Siebel Connector

philips505 over 8 years ago

I am attempting to connect to a clients Siebel server using the built in a!sblInvoke expression. I am however receiving the following error:

[success:false,result:,error:[code:[category:0,namespace:1,detail:0],title:Error calling sblInvoke,message:The external server for this system [key=siebeldev] generated an exception when calling a function [sblInvoke]. Details from external system: <Exception>
<Major No.>16</Major No.><Minor No.>8716488</Minor No.><Message>Could not open a session in 4 attempts. {1}(SBL-JCA-00200)</Message><DetailedMessage>Unknown<DetailedMessage>
</Exception>,detail:Could not open a session in 4 attempts. {1}(SBL-JCA-00200)]]

I have checked the Siebel logs and there is no record of the call or exception. It seems that the call is not even making it to Siebel.

We are using Appian 16.2 and calling Siebel 15.8.0.0.

Has anyone experienced a similar issue?

Discussion posts and replies are publicly visible

0 philips505 over 8 years ago

The siebel jar that appian uses is for 8.2.*. Is there a standard way of updating this to the latest?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Steven Hearne
Appian Employee
over 8 years ago

Would you mind uploading the logs, please?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 philips505 over 8 years ago

See attached an extract of server.log. Thank you in advance!
server.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 philips505 over 8 years ago

We are on Siebel 15.8.0.0 aka 8.1.1.15 aka IP2015; installed on Windows Server 2012. We connect from other applications in our stack to Siebel via same integration method – although our Siebel jar files are from our installation.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Steven Hearne
Appian Employee
over 8 years ago

Just for clarification, in this statement:

"The siebel jar that appian uses is for 8.2.*. Is there a standard way of updating this to the latest?"

Do you mean that you want to move to a jar used for 8.1*?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 philips505 over 8 years ago

Yes, apologies, I mean to "downgrade" the jar to 8.1.*.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Steven Hearne
Appian Employee
over 8 years ago

From our understanding, the siebel jar that Appian uses should work with the 8.x series.

I was looking at your error message, and I noticed that it was similar to the error message on this site:
kb.informatica.com/.../124780.aspx

This site says the cause is:
This error occurs due to the incorrect parameter Application object manager (emedicalobjmgr.enu) in the connection object.

Looking at the Appian documentation, it seems that the appManager parameter might be related:
forum.appian.com/.../Connector_Functions.html

Have you checked this?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 philips505 over 8 years ago

Yes, we have made sure all parameters are correct. Have you ever had a need to include siebel.properties in the classpath to enable connectivity?
siebel.properties
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 philips505 over 8 years ago

Have you ever had issues with differing JVM timezone settings and connecting to Siebel, i.e. Appian is on GMT and Siebel is on a local timezone setting?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Steven Hearne
Appian Employee
over 8 years ago

For question #1: I'm not sure; you'd have to test this out.

For question #2: Not to my knowledge, but again, this is something that you'd have to test.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel