Bookshelf v8.0: What's New in This Release

Transports and Interfaces: Siebel Enterprise Application Integration >

What's New in This Release

What's New in Transports and Interfaces: Siebel Enterprise Application Integration, Version 8.0, Rev. C

Table 1 lists changes described in this version of the documentation to support release 8.0 of Oracle's Siebel software.

Table 1. New Product Features in Transports and Interfaces: Siebel Enterprise Application Integration, Version 8.0, Rev. C
Topic	Description
Inbound Methods for a Transport Business Service	Modified topic. Added a caution not to set the OM - Preload SRF Data parameter to True for single-threaded Siebel Application Object Manager components, such as Siebel Enterprise Application Integration (EAI) receivers.
Features Not Supported for Use with the Siebel JMS Transport	Modified topic. The use of Secure Sockets Layer (SSL) with the Siebel JMS Transport is not supported because the Java Message Service (JMS) standard is not bound to transport layers. For information on enabling and using SSL with the Siebel JMS Transport, contact the vendor of your JMS system.
Roadmap for Configuring JMS Messaging Between Siebel Business Applications and Oracle SOA Suite Using Oracle Advanced Queuing	Modified topic. Revised it to use Oracle Enterprise Manager for resource provider configuration and to correct the list of required Java Archive (JAR) files.
Mapping a JCA Thread to a Siebel Server Task and Log File	New topic. You can find the Siebel Server task and log file from the Java EE Connector Architecture (JCA) logging information.

What's New in Transports and Interfaces: Siebel Enterprise Application Integration, Version 8.0, Rev. B

Table 2 lists changes described in this version of the documentation to support release 8.0 of the software.

Table 2. New Product Features in Transports and Interfaces: Siebel Enterprise Application Integration, Version 8.0, Rev. B
Topic	Description
Increasing the Maximum Message Length on IBM WebSphere MQ	New topic. If you are handling large messages, you can change the MaxMsgLength queue manager and queue attributes.
Receiving Inbound Messages with MSMQ Receiver	Modified topic: Removed the Receiving Messages from MSMQ topic. Added MSMQ Receiver named subsystem steps to the examples. Removed the EAI MSMQ Transport steps from the workflow examples because the MSMQ Receiver, which uses the EAI MSMQ Transport, is defined in the receiver subsystem steps.
Prerequisites for Implementing a Java Business Service Restrictions for Implementing JBS	Modified topic. You cannot use 64-bit Java Virtual Machines (JVMs) with Java business services in Oracle's Siebel Business Applications, which are 32-bit.
About Synchronous and Asynchronous Invocation	Modified topic. Added a note that in-process re-entrance is not supported for the JMS Receiver.
About the JMS Receiver	Modified topic. Added details on JMS Receiver parameters.
Roadmap for Configuring JMS Messaging Between Siebel Business Applications and Oracle SOA Suite Using Oracle Advanced Queuing	New topic. This topic describes a process for communicating between Siebel Business Applications and Oracle SOA Suite using Java Message Service (JMS) as the transport mechanism.
Troubleshooting for the JMS Transport	Modified topic: Expanded the descriptions of the CheckJNDIObjects and CheckJMSServer debugging methods. Added a note that while the classpath is limited to 1024 characters, it might be truncated when displayed in the user interface and command-line interface.
Selecting the Appropriate Business Service for HTTP	Modified topic. Do not use the Web Engine HTTP TXN business service for inbound HTTP transport sessions.
Using the EAI HTTP Transport for Inbound Integration	Modified topic: Clarified how session cookies are handled in session mode. Clarified where special characters must be encoded for use in URLs and where encoding is not required.
Providing Client Certificate Information for SSL Mutual Authentication	New topic. A Siebel eScript example is shown, which provides client-authentication parameters.
EAI File Transport Named Subsystem	New topic. Added information on the FileTranspSubsys named subsystem and an example of its use.
Transcode Service Business Service	New chapter. The Transcode Service business service converts data from one character-set encoding to another. It can also validate conversions before they are performed.

What's New in Transports and Interfaces: Siebel Enterprise Application Integration, Version 8.0, Rev. A

Table 3 lists changes described in this version of the documentation to support release 8.0 of the software.

Table 3. New Product Features in Transports and Interfaces: Siebel Enterprise Application Integration, Version 8.0, Rev. A
Topic	Description
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.

Additional Changes

Workflows are created in Siebel Tools in version 8.0 and higher. Each procedure in this guide that describes how to create a workflow has been revised to reflect this change.

Changes that were made to Transports and Interfaces: Siebel Enterprise Application Integration for Siebel Business Applications version 8.1 and higher have also been made in this guide where they apply to version 8.0.

Transports and Interfaces: Siebel Enterprise Application Integration		Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.