Scenario: While connecting to Local DB through Developer / Mobile Client, users would face similar issues…
Resolution:
The siebel remote system preferences are set as follows
DCK: PwdLockoutFlg TRUE
DCK: PwdLockoutInDays 1
DCK: PwdLoginTries 2
So the siebel remote Enable Mobile Web Client Lockout setting is selected (DCK: PwdLockoutFlg=TRUE ) , the Mobile Web Client counts unsuccessful user login attempts. When the count reaches the value of the Failed Login Attempts setting(DCK: PwdLoginTries=2), the Mobile Web Client prevents that user from logging in for the number of days specified in the Lockout Period setting(DCK: PwdLockoutInDays=1).
You have 2 options:
1) wait one day until the Lockout is not active
2) a- set siebel remote systeme preference DCK: PwdLockoutFlg to FALSE. This can be done by unchecking the box “Enable Mobile Web Client Lockout” in the Siebel Remote System Preferences views.
b- reextract the user
August 6, 2008
Posted by
Narayan Patro |
Remote |
Application_Lock-Out_Mode |
1 Comment
Scenario: You have 2 enterprises under a single Gateway. Each Enterprise in turn has its own Siebel Server.
Lets assume the server names as Server1 and Server2.
Lets assume that both the servers are configured to run on the same host XYZ with SynchMgr Ports 40401 and 40402 respectively.
In order for your client or Tools application to dock successfully with the server (either for Local Db initialization or Data Synch) you would be required to fill in the correct parameter in the “LOCAL” section of the respective cfg file.
The parameter is DOCKCONNSTRING.
The correct parameter value would be “HOST_NAME::STATIC_PORT_NUMBER” where
HOST_NAME is the host on which the server is configured.
STATIC_PORT_NUMBER is the port on which the respective Synchronization manager component is running.
Note: Check the double colon in between Host_Name and STATIC_PORT_NUMBER.
e.g., if we want to dock with server2 in the above case, the parameter value for DOCKCONNSTRING would be XYZ::40402.
Method to determine the values:
Log on to srvrmgr using the command line. ( SIEBSRVR_ROOT\Bin:\> srvrmgr /g <GATEWAY_NAME> /e <ENTERPRISE_NAME> /u <USER_NAME> /p <PASSWORD> /s <SIEBEL_SERVER> )
To determine the Host value for the SynchMgr component type in the following command:
list param host for server SERVER_NAME
You will get a response something similar as shown below:
srvrmgr:sessrvr> list param host for server sessrvr
PA_ALIAS PA_VALUE PA_DATATYPE PA_SCOPE PA_SUBSYSTEM PA_SETLEVEL PA_DIS
P_SETLEVEL PA PA PA PA PA_NAME
——– ———– ———– ——– ———— ———— ——
———- — — — — ———
Host siebelsrv-1 String Server Server level Server
level set N N Y N Host Name
Note the host name as the second string in the response.
To determine the STATIC_PORT_NUMBER for component SynchMgr, use the following command:
list advanced param PortNumber for comp SynchMgr
srvrmgr:sessrvr> list advanced param PortNumber for comp SynchMgr
PA_ALIAS PA_VALUE PA_DATATYPE PA_SCOPE PA_SUBSYSTEM PA_SETLEVEL PA_DISP
_SETLEVEL PA PA PA PA PA_NAME
———- ——– ———– ——— ———— ———– ——-
———— — — — — ——————
PortNumber 40402 Integer Subsystem Networking Comp level Compone
nt level set N N Y N Static Port Number
July 17, 2008
Posted by
Narayan Patro |
Remote |
|
1 Comment