Pageviews

Follow Ritesh Maddala Blogs - Join the Fan Club Today and Keep Learning

Wednesday, October 16, 2013

ObAccessClient.lst does not contain a client id - ACCESS_GATE FATAL 0x00001824

Hi,

Problem Description :

When A new Webgate agent is registered with OAM, sometimes due to some mis-configuration it the OHS servers throws some common exception. Today I got a very uncommon exception in OHS - Webgate - OAM configuration. Below is the stack trace came in :
------------------------------------------------------------------------------------------------------------
Message from syslogd@ at Wed Oct 16 10:19:05 2013 ...
mmvhsgbobis001a Oblix: 2013/10/16@10:19:05.07603      
3716    3765    ACCESS_GATE     FATAL   0x00001520    
/ade/aime_ngamac_497961/ngamac/src/palantir/webgate2/src/apache2entry_web_gate.cpp:589
"Exception thrown during WebGate initialization"

Message from syslogd@ at Wed Oct 16 10:19:05 2013 ...
mmvhsgbobis001a Oblix: 2013/10/16@10:19:05.07618      
3716    3765    ACCESS_GATE     FATAL   0x00001824    
/ade/aime_ngamac_497961/ngamac/src/palantir/webgate2/src/apache2entry_web_gate.cpp:590
 "ObAccessClient.lst does not contain a client id."      raw_code^213

------------------------------------------------------------------------------------------------------------

Message from syslogd@ at Wed Oct 16 10:46:35 2013 ...
mmvhsgbobis001a Oblix: 2013/10/16@10:46:35.09020    
 4728    4733    ACCESS_GATE     FATAL   0x00001520  
 /ade/aime_ngamac_497961/ngamac/src/palantir/webgate2/src/apache2entry_web_gate.cpp:589
  "Exception thrown during WebGate initialization"

Message from syslogd@ at Wed Oct 16 10:46:35 2013 ...
mmvhsgbobis001a Oblix: 2013/10/16@10:46:35.09035    
 4728    4733    ACCESS_GATE     FATAL   0x0000182A  
 /ade/aime_ngamac_497961/ngamac/src/palantir/webgate2/src/apache2entry_web_gate.cpp:590
"An internal ObError exception was caught."     raw_code^224

------------------------------------------------------------------------------------------------------------

Solution for Above Error:
------------------------------
Check "ObAccessClient.xml file in 
MW_HOME/ohs/instances/instance1/config/OHS/ohs1/webgate/config

If anything is looking inappropriate, just once more copy the artifacts from OAM_RREG_HOME/output/Agent_Name/ObAccessClient.xml  to this location.
(In My case I have registered the Agents using RREG - OAM remote Registration Tool).

If that doesn't work, you have to delete the present Agent from OAM and  re-register the Agent to create the new Artifacts (cwallet.sso and ObaccessClient.xml). Copy the new Artifacts to MW_HOME/ohs/instances/instance1/config/OHS/ohs1/webgate/config





Tuesday, October 8, 2013

ClassCastException error during OIM- Siebel Provisioning/Reconciliation

ClassCastException error during OIM-

Siebel Provisioning/Reconciliation

OIM connector for Siebel was apparently installed successfully. But, provisioning to the Siebel resource did not go through. A careful inspection of logs reveals the notorious “ClassCastException”.
Environment: OIM 11g 11.1.1.5.0 (PS1), Siebel 8.1.1, Oracle DB 11.2.0.1, Siebel User Management Release 11.1.1, Oracle Enterprise Linux 5.6 (64 bit), WLS 10.3.5
Stacktrace
java.lang.ClassCastException: java.lang.NoClassDefFoundError cannot be cast to org.identityconnectors.framework.common.objects.ConnectorObject
Other variants:
java.lang.NoClassDefFoundError
Investigation
This problem occurs if the required third party JARs (as noted in the connector documentation) were not successfully bundled within the connector during connector installation.
The documentation instructs one to copy siebel.jar and siebelji_enu.jar from SIEBEL_INSTALLATION_DIRECTORY/siebsrvr/CLASSES directory location and place in OIM_HOME/ConnectorDefaultDirectory/targetsystems-lib/siebel-RELEASE_NUMBER. But the downloaded third party jars size showed ridiculous 133KB (where healthy Siebel.jar ->1,295KB, SiebelJI_enu.jar -> 42KB).
Verification
1. $OIM_HOME/server/bin/DownloadJars.sh
[Enter Xellerate admin username :]xelsysadm
[Enter the admin password :]
[Enter serverURL :[ t3://localhost:7001 ]]t3://localhost:14000
[Enter context Factory :[ weblogic.jndi.WLInitialContextFactory ]]
Enter the jar type
  1.JavaTasks
  2.ScheduleTask
  3.ThirdParty
  4.ICFBundle
4 <——————————— Choose 4 for SiebelConnectorBundle here
Enter the full path of the download directory :

/tmp
Enter the name of jar file to be downloaded from DB :
org.identityconnectors.siebel-1.0.1.jar <—————– The name of the SiebelApps bundle
Do u want to download more jars [y/n] :n
Download jar executed successfully
2. Create a new Directory and name it Siebel_Jar. Unzip the downloaded org.identityconnectors.siebel-1.0.1.jar file into Siebel_Jar and check for the four required third-party JAR files which will not be present.
Your Directory Should look like :

Siebel_Jar
             |--------|
                        |----org
                        |----THIRDPARTYREADME.txt
                        |----META-INF
                        |----org.identityconnectors.siebel-1.0.1.jar

Solution
1. In the directory where the downloaded org.identityconnectors.siebel-1.0.1.jar was unzipped (ie. so you’re in the structure of the archive itself) create a sub-directory within this called: lib
2. Copy the Two External Jars i.e. (Siebel.jar and SiebelJI_enu.jar) required Siebel third-party JAR files into this new lib directory.
3. Move org.identityconnectors.siebel-1.0.1.jar file from this directory to another directory. Re-jar the files which now contain the third-party files in the new lib directory (the following command assumes you’re in the same directory(Siebel_Jar) where the original jar was unzipped in to and you’ve moved the original JAR file from this directory so it doesn’t end up in the new archive):
Now Your Directory should look like:
Siebel_Jar
             |--------|
                        |----org
                        |----THIRDPARTYREADME.txt
                        |----META-INF
                        |----lib
 Now Run the command below.
jar cvfm org.identityconnectors.siebel-1.0.1.jar META-INF/MANIFEST.MF *
(note the use of the existing MANIFEST.MF file as OIM will check for this)
4. Upload this new updated JAR file back into the database:
$OIM_HOME/server/bin/UploadJars.sh
[Enter Xellerate admin username :]
[Enter Xellerate admin username :]xelsysadm
[Enter the admin password :]
[Enter serverURL :[ t3://localhost:7001 ]]t3://localhost:14000
[Enter context Factory :[ weblogic.jndi.WLInitialContextFactory ]]
Enter the jar type
   1.JavaTasks
   2.ScheduleTask
   3.ThirdParty
   4.ICFBundle
4 <———————— again choose option 4 here for the SiebelConnectorBundle
Enter the path/location of jar file :
/tmp/jars/ org.identityconnectors.siebel-1.0.1.jar <—————– The name of the SiebelApps bundle
Do u want to load more jars [y/n] :n
Upload jar executed successfully
5. Restart OIM and retest provisioning and monitor logs.





******************************************************************************
******************************************************************************

Follow Ritesh Maddala Blogs - Join the Fan Club Today and Keep Learning

Follow Me

Java Application Examples

Java Application / Software Development

Follow by Email