Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Object Interfaces Reference > Customizing Siebel Object Interfaces > Accessing a Siebel Object Interface > Accessing the Siebel Java Data BeanA Java client that uses the Siebel Java Data Bean to connect to the Siebel Server requires JAR files. These files allow the Java language to access the objects and methods of the Siebel Object Interface. These files are specific to the version of the Siebel application. Do not use these JAR files with other versions. For more information, see About the Siebel Java Data Bean Object Interface. To access the Siebel Java Data Bean
Example of Accessing the Siebel Java Data BeanThe following example code accesses the Siebel Java Data Bean. You can use a Java IDE to compile and run this code: import com.siebel.data.*; public class DataBeanDemo public static void main(String[] args) public DataBeanDemo() // log in to the Siebel Server // get the business object // get the business component // log off catch (SiebelException e) Using Single Sign-on (SSO) with Siebel Java Data BeanIf you use single sign-on (SSO) with Siebel Java Data Bean, then you must include the following items in the login:
m_dataBean.login("Siebel://gatewayserver:2321/enterpriseServer/SCCObjMgr_enu", SADMIN, HELLO,"enu");
Customizing the Parameters a Third-Party Application Uses to Connect Through the Siebel Java Data BeanYou can customize the parameters that a third-party application uses when it connects to a Siebel application through the Siebel Java Data Bean. To customize the parameters a third-party application uses to connect through the Siebel Java Data Bean
Properties of the Siebel Properties FileTable 6 describes the properties of the siebel.properties file.
Example of the Siebel Properties FileThe following code is an example of the siebel.properties file: siebel.connection.string = siebel.tcpip.rsa.none://test.siebel.com/siebel/sseobjmgr_enu/test siebel.user.password = password siebel.conmgr.txtimeout = 3600 siebel.conmgr.sesstimeout = 300000 Determining the Total Number of Open ConnectionsThe connection pool maintains a set of connections to a specific server process. The default value for the siebel.conmgr.poolsize property is 2. The maximum value is 500. The siebel.conmgr.poolsize property and the Min MT Server parameter on the object manager determine the total number of open connections. Each MT server process is a Windows process that includes a connection pool. The total number of open connections is the value in the siebel.conmgr.poolsize property multiplied by the value in the Min MT Server parameter. For example, if the siebel.conmgr.poolsize is 2, and if the Min MT Server parameter is 3, then the total number of open connections is six. Customizing Character Encoding for the Siebel Java Data BeanThe character encoding of the Siebel Server and the character encoding of the Siebel client must be the same. This allows the Siebel client and the Siebel Server to communicate correctly. If the Siebel client and the Siebel Server default character encoding cannot be the same, then you can modify the Siebel client character encoding. To customize character encoding for the Siebel Java Data Bean
Table 7 lists character encoding mappings you can use for the Java Data Bean. The Siebel Value column contains the codes you can specify in the CodePageValue variable. Encrypting Communication Between the Java Data Bean and the Siebel ServerTo encrypt communication between the Siebel Java Data Bean and the Siebel Server, you can use the Rivest, Shamir and Adleman (RSA) encryption libraries. For information about platforms you can use with encryption, see Siebel System Requirements and Supported Platforms on Oracle Technology Network. To encrypt communication between the Siebel Java Data Bean and the Siebel Server
Encrypting Communication on a Platform That the RSA Libraries do Not SupportTo use encryption on a platform that the RSA libraries do not support, Oracle uses the Java Cryptography Extension (JCE) v1.2.1 specification. JCE provides a way to encrypt, create the encryption key, create the key agreement, and handle Message Authentication Code. With JCE, you can use some other qualified cryptography library as a service provider. For information about developer resources for Java technology, see the following Web site: http://www.oracle.com/technetwork/java/java-sun-com-138872.html To encrypt communication on a platform that the RSA libraries do not support
Login Errors You Might Encounter When You Use the Siebel Java Data BeanThe Siebel Java Data Bean might return a login error that is similar to the following: Siebel Exception thrown invoking login Method. Code--1. Message-Logon request 75 was abandoned after 2ms connection. Any of the following items can cause this error:
Using the Siebel Java Data Bean with Multiple ThreadsMultiple threads of a single process must not access a common instance of the Siebel Java Data Bean. If a process with multiple threads must use the Siebel Java Data Bean, then each thread must create a separate instance of the Siebel Java Data Bean. Do not reuse an instance of any other object that the Siebel Java Data Bean makes available across multiple threads of the same process. This requirement includes the following objects: CAUTION: You must configure Siebel CRM to create one instance of the Siebel Java Data Bean for each thread that must use it. If a thread gets Siebel Java Data Bean Objects, then do not configure Siebel CRM to share these objects with any other thread. |
![]() ![]() |
Siebel Object Interfaces Reference | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |