Search This Blog

sbl-svc-00252


Applies to:

Siebel System Software - Version 7.8.2 [19213] to 8.1.1.4 [21225] [Release V7 to V8]
Information in this document applies to any platform.

Goal

Does Application Deployment Manager (ADM) online deployment work with SSO and LDAP?
The ADM online deployment fails with the errors below:

[Deployment Session Header]
ADM Deployment Session: 1-7A6M2O
Start Time: 11/16/2008 19:21:50
Target Web Address: http://abc.de.fg.com/eai_enu
Target User Name: 501516363

Status: Deployment Failed
End Time: 11/16/2008 19:21:53
EAI Logs:
Error invoking service 'UDA Service', method 'SendReceive' at step 'Send and Receive'.(SBL-BPR-00162)
HTTP Internet Exception during 'Login': 'A redirect request will change a non-secure to a secure connection ', code: '12039'(SBL-EAI-04116)
An error occurred connecting to the Target System. Please verify the connection information.(SBL-SVC-00252)
The environment is SSO and LDAP enabled.

Fix

ADM is the framework; underneath, ADM uses Enterprise Application Integration (EAI) for data deployment through the business object layer.
The online deployment of Siebel ADM uses EAI technology:  ADM uses an EAI HTTP inbound call to connect to the target environment. The first step in setting up ADM to do online deployment is to make sure the EAI HTTP inbound call to target environment is successful, independent from the ADM UI.
The ADM inbound EAI HTTP request logs into the EAIObjMgr_enu object manager using the username and password in the URL; thus, SSO and LDAP need to be configured for the EAIObjMgr_enu component.

Since there are currently issues with EAI using SSO, ADM does not yet work with SSO. When there is a new SSO solution for EAI,  then ADM will work with SSO.

ADM with Management Server is NOT supported in an SSO-enabled mode.

Workaround without Management Server and Management Agent:

This workaround should NOT be implemented in an environment with Management Server and Management Agent since the process would expose the trust token in multiple places.
Create a dedicated Siebel user to perform all EAIObjMgr works, bypassing the SSO and LDAP.  This works successfully in deploying from source to target.

Test Submitting an Inbound EAI HTTP Request:
URL to submit an inbound EAI HTTP request to the target environment:
http://kachend123.siebel.com:80/eai_enu/start.swe?SWEExtSource=SiebelEcho&SWEExtCmd=Execute&UserName=SADMIN&Password=SADMIN&SWEExtData=ABC

Description of URL: kachend123.siebel.com:80/eai_enu/start.swe? This is the target machine name where the EAI component is running; 80 is the port used to configure the SWSE in target environment.

SWEExtSource=SiebelEcho&SWEExtCmd=Execute This is to execute SiebelEcho defined in your siebsrvr\bin\enu\eai.cfg file in the [HTTP Services] section. SiebelEcho is defined as a method in the EAI profile subsystem.

&UserName=SADMIN&Password=SADMIN This is the username and password you want to use to log into the target system.

&SWEExtData=ABC This is the data you want to send. In this example, the text "ABC" is sent.
Steps to Submit:
  1. Open an IE browser.
  2. Copy and paste the above command in the URL, and hit enter.
  3. If successful, you will be prompted to save in a file named start.swe.
  4. Save the file.
  5. Open the file start.swe with notepad:  the text ABC is shown.

You should be able to do this with an out-of-the-box configuration.

Perform/Check in the Target Environment:
  1. Enable the "Enterprise Application Integration" server component group.
  2. Synchronize the batch component after you enable the server component group.
  3. Restart the Siebel Server service.
  4. Confirm that "EnableExtServiceOnly = TRUE" in the eai_enu section of the eapps.cfg.

Extracted Example From eapps.cfg:
[/eai_enu]
ConnectString = siebel.TCPIP.None.None://kachend123:2321/SEA78/EAIObjMgr_enu
EnableExtServiceOnly = TRUE
WebPublicRootDir = D:\S78\SWEApp\public\enu
WebUpdatePassword = z6u4MuGrmSPESz8R09ZsxwH5IDnI





Applies to:

Siebel System Software - Version: 7.7.2.2 [18356] and later   [Release: V7 and later ]
Siebel System Software - Version: 7.8.2.2 [19219] to 8.1.1.4 [21225]   [Release: V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.2 [18356]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2000 Server SP 4

This document was previously published as Siebel SR 38-2319330387.

Symptoms

We are working with ADM, trying to migrate data from Dev to test environments using the Application Deployment Manager GUI. We are using the vanilla View object created by Siebel when installed. We have created the project and the session to migrate the views.

However, ADM fails while trying to access our test environment. We get the following error:

An error occurred connecting to the Target System. Please verify the connection information.

I have checked the test environment for:

•    EAI Object manager is enabled and running.
•    UDA Deployment exists in the Enterprise profile and eai.cfg.
•    Login works is successful.
•    I can manually export a file and import the file successfully.


The following is output from the ADM session log:

[Deployment Session Header]
ADM Deployment Session: 1-5K76
ADM Deployment Project: Test Aspens Views
Start Time: 07/26/2005 16:57:50
Target Web Address: http://test.serverlocation.com/eai_enu
Target User Name: sadmin

Status: Deployment Failed
End Time: 07/26/2005 16:57:50

EAI Logs:
Unterminated token starting at position '116' in EAI template 'http://test.serverlocation.com/eai_enu/start.swe?SWEExtCmd=ExecuteLogin&SWEExtSource=UDADeploy&UserName=sadmin&Password=$tebel08'(SBL-EAI-04030)
Error invoking service 'UDA Service', method 'SendReceive' at step 'Send and Receive'.(SBL-BPR-00162)
An error occurred connecting to the Target System. Please verify the connection information.

An error occurred connecting to the Target System. Please verify the connection information.(SBL-SVC-00252)

Cause

Additional errors in EAIObjMgr log file:

EAIObjMgr_enu_6176.log 7.7.2.2 [18356] ENU


SisnTcpIp SisnSockDetail 4 0 2005-07-26 16:53:10 7360: [LOCALTRANS-server] accept() timeout during get conn request

SisnTcpIp SisnSockDetail 4 0 2005-07-26 16:53:15 7360: [LOCALTRANS-server] accept() timeout during get conn request

SisnTcpIp SisnSockDetail 4 0 2005-07-26 16:53:20 7360: [LOCALTRANS-server] accept() timeout during get conn request

MaintTestObjEvt MaintTestObjEvtTrace 4 0 2005-07-26 16:53:23 6180: _smiFacTestObj::Execute(43c1d4) for Background, Waitime = 23


The problem was due to the password associated with the SADMIN user.

The password contained a '$' symbol which was causing the error.

Solution

A different user without the '$' symbol worked fine.
Do not use the '$' or '#' symbols in passwords.

No comments:

Post a Comment