Siebel Connector

philips505 over 7 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 7 years ago

We have developed a standalone java Siebel client using the jars provided by Siebel 15.8.0.0 aka 8.1.1.15. This client connects and runs successfully from the server on which our Appian deployment is hosted.

We then referenced the Siebel jars packaged with Appian 16.2 and attempted the same. The client fails with the following error:

<com.siebel.common.common.CSSException>
<Error><ErrorCode>8716698</ErrorCode> <ErrMsg>Invalid format of the packet received from the server.(SBL-JCA-00410)</ErrMsg></Error>
</com.siebel.common.common.CSSException>
at com.siebel.om.conmgr.Connection.readPacket(Connection.java:628)
at com.siebel.om.conmgr.Connection.init(Connection.java:296)
at com.siebel.om.conmgr.Connection.<init>(Connection.java:140)
at com.siebel.om.conmgr.ConnectionManager.open(ConnectionManager.java:134)
at com.siebel.om.om.CSSModel.login(CSSModel.java:1673)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java:217)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java:179)
at com.allangray.siebel.file.extract.SiebelConnector.connectToSiebel(SiebelConnector.scala:18)
at com.allangray.siebel.file.extract.Runner.main(Runner.java:24)
Exception in thread "main" <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>
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java:224)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java:179)

This error is consistent with the error we receive when attempting to connect to Siebel from within Appian.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Steven Hearne
Appian Employee
over 7 years ago

Would you mind enabling Debug loggin for connector functions in Appian?

Navigate to <APPIAN_HOME>\\ear\\suite.ear\\resources\\appian_log4j.properties

Find the following line:
#log4j.logger.com.appian.integration=DEBUG

Change this line to:
log4j.logger.com.appian.integration=DEBUG

Save the file. The changes will hot deploy.

After that, attempt to connect to Siebel from within Appian. Then upload the server.log file.

This might provide us with more information.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 philips505 over 7 years ago

See attached. Let me know if you require any other information. Thanks!
server.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Steven Hearne
Appian Employee
over 7 years ago

Do you have a firewall between Siebel and Appian?

I'm looking at this link:
www.error-codes.info/.../sbl-jca-00313-socket-had-incorrect-word.html

Because I saw this error:
Socket had incorrect word size
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel