1.OVERVIEW:
To identify the impact of this upgrade on the existing Siebel7.8 interfaces, detailed impact analysis is performed. This document covers the interface impacts identified and discuss the proposed solutions.
2.SCOPE:
Analyzed the existing Interfaces in Siebel 7.8 Application to identify
1.Architectural and supported platforms impact on Interfaces
2.Upgrade impact on Siebel interface objects(IOs, Workflows, Scripts..etc)
3.External Application Impact
3.REFERENCE DOCUMENTS AND ARTIFACTS:
•http://w76162.usac.mmm.com/CRMA/index.html
•System Requirement Specifications guide of 7.8, 8.1
•Siebel 7.8 application and Tools Repository
4.ARCHITECTURAL IMPACTS:
All real time interfaces in Siebel 7.8 application are using IBM MQSeries Application Messaging Interface1.2.4 (AMI) transport
Oracle stopped supporting AMI transport starting Siebel7.8 onwards. Some customers got it working on 7.8 as the transport business service was still available at the repository but they did so at their own risk.
There was no formal support for AMI at 7.8 and the transport has not been maintained or enhanced since 7.7
Hence, we will not be able to continue with AMI transport in Siebel 8.1 application.
Supporting Documentation:
https://support.oracle.com/CSP/ui/flash.html#tab=Dashboard(page=Dashboard&id=g2ta6nki()),(page=SRView&id=g2tbb3om(sr_stmt=Does%20the%20EAI%20MQSeries%20AMI%20Transport%20work%20in%208.1.1%20and%20if%20yes,%20will%20it%20gets%20su...&&sr_number=3-1167762381&sr_row_id=3-JB977X))
https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=477793.1
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=498587.1
4.1 Available Solutions:
The below are the 3 supported Interfaces as alternatives for latest version of Siebel application.
1. EAI JMS Transport
2. EAI MQ Series Server Transport
3. Other Transports
EAI JMS Transport
MQ can be configured to act as a JMS server and siebel can access a remote MQ+JMS server. However, all applications exchanging messages with siebel need to use JMS methods to put or read messages to the MQ queue. The reason is a "pure" MQ message lacks headers and other information a JMS message has. As a result, a message put by a 3rd party application into an MQ queue NOT using JMS methods would NOT be readable by Siebel.
The reverse is also true. A JMS message put at an MQ queue by Siebel using JMS methods would not be readable by applications not using JMS methods to read it.
It means you have to re-design the 3rd party applications to use JMS too.
EAI MQ Series Server Transport
If EAI MQ Series Server Transport is used siebel server that interacts with MQ , a whole MQ server needs to be installed at the same machine.
Unlike AMI, you can not access a remote MQ queue with this transport.
The MQ server has to be at the same box as the siebel server.
This may have an impact on MQ licenses as you may have to license multiple MQ servers.
Other Transports
EAI allows other transports such as EAI HTTP Transport, EAI File Transport, and even custom transports (custom business services you code yourself) but they are not standard QUEUE transports. They do not provide the same guarantees and features as a queue transport.
4.3 Impact to Siebel:
• Software Installation
Software’s to be installed on Windows Servers where Workflow Process Manager Siebel Server component operates.
1. IBM Websphere MQ Client Version 6.0.2.2
2. Java Virtual Machine
Download ms0n.zip, ms0B.zip, me01.zip from IBM support site. Extract the files to JMS\GUITool
•Setting up the JVM Receiver Component Parameter & Subsystem
Need to setup JMS Receiver Component Parameters in Enterprise Servers – Component Definitions
Setting up the JVM Subsystem Types
Need to specify the required parameters like JVM Subsystem name
ReceiveQueue name
Impact to MW & Other applications:
1. Middleware Queue Type needs to be modified in accordance with JMS Transport
2. Chances of discrepancy of JMS Headers with the Middleware and External Applications
3. If JMS transport communication port is not open, enable the ports
4. Middleware team has to investigate for further Impact while migrating from AMI Transport to JMS Transport
Configuration Impacts:
1. Need to make use of EAI JMS Transport instead of EAI MQSeries AMI Transport
2. Slight modification with the default branches in the workflows
3. Some of the Upgrade workflow issues needs to addressed
4. Integration Object Issues
5. Unit test all the interfaces and fix the issues
Out of Scope
• End to end testing of Interfaces in 7.8
• Testing of Interfaces that does not have sufficient details and XML files
• Development of any Interfaces integrated with Siebel 7.8 after upgrade to Siebel 8.1
• Setup and validation of interfaces (if required) for successful execution of test cases
No comments:
Post a Comment