Table 3. New Product Features in Transports and Interfaces: Siebel Enterprise Application Integration, Version 8.0, Rev. A
|
|
Using Named Subsystems for Transport Parameters |
Modified topic. Added a note that you must specify named subsystem parameters by their aliases. |
Exposing MQMD Headers as Properties |
Modified topic. Updated the lists of supported inbound and outbound headers. Corrected the description of the MsgFlags MQMD message header in Table 9. |
About Defining Integration Objects |
Removed the procedure from this topic. The creation of integration objects is documented in Integration Platform Technologies: Siebel Enterprise Application Integration. |
Prerequisites for Implementing a Java Business Service |
Modified topic. Added complete Java Runtime Environment (JRE) library paths for various operating systems. |
Troubleshooting the Java Business Service |
Modified topic. Added the names of Windows and UNIX utilities that you can use to troubleshoot CLASSPATH errors. |
Configuring the JMS Transport |
Modified topic. Added a note that you can have only one Java Virtual Machine (JVM) loaded in a process, and therefore only one JVM subsystem. If you try to load more than one JVM subsystem, an error will occur. If you want multiple JVM subsystems, then you must configure additional components. |
Configuring Against TIBCO |
Returned this topic to the documentation, because TIBCO is supported in Siebel Business Applications version 8.0 and higher. |
Using POST and GET |
Modified topic. Added descriptions of the POST and GET methods. |
EAI HTTP Transport Method Arguments |
Removed the HTTPIsSecureConn parameter. This parameter is not necessary, because the Web server automatically uses the Secure Sockets layer (SSL) protocol when the URL begins with https:// . |
EAI HTTP Transport for Inbound Messages |
Modified topic. Added a note that you can make the business service available by deploying it to the run-time database from Siebel Tools, as well as by compiling the SRF file. Clarified the note about the HTTP response for inbound requests. If the process properties are set as In/Out (the default), the values will appear as HTTP headers on the HTTP response from the Siebel Server. |
Specifying Parameters as Business Service User Properties |
Modified topic. You can deploy the business service to the run-time database from Siebel Tools. |
Connection Parameters for the SiebelDataBean |
Modified topic. Added the maximum values for siebel.conmgr.txtimeout and siebel.conmgr.sesstimeout. Changed their values in the sample siebel.properties file to more realistic numbers. |
About JCA Logging |
New topic. Enhancements have been made to J2EE Connector Architecture (JCA) logging in Siebel Business Applications version 8.0 and higher. |