Use these instructions to enable a WebSphere® Sensor Events high
availability system to connect to the SIBus.
Before you begin
These steps expect that you have already created a logical
topology for your high availability system in the
WebSphere Sensor Events Administrative Console.
Procedure
- Open the WebSphere Sensor Events Administrative Console.
The home page displays.
- Navigate back to the Configuration Groups,
and modify the agents for the High Availability Controller.
- Clear the marks for the following agents from the check
boxes:
- DTSMQBridgeInboundFlowAgent
- DTSMQBridgeInboundPipeAgent
- DTSMQBridgeOutboundPipeAgent
- MQBridgeOutboundFlowAgent
- Select the following agents:
- EdgeSIBusBridgeInboundFlowAgent
- SIBusBridgeOutboundFlowAgent
- SIBusBridgeInboundPipeAgent
- SIBusBridgeOutboundPipeAgent
- Modify the url property values for the
SIBusBridgeInboundPipeAgent and the SIBusBridgeOutboundPipeAgent.
- In the High Availability Controller panel,
click SIBusBridgeInboundPipeAgent, and modify
the url property value from iiop://%PREMISES_IP%:2908
to iiop://%PREMISES_IP%:9810.
- Make the same change to the SIBusBridgeOutboundPipeAgent.
- In the WebSphere Sensor Events Administrative Console, click Event
Templates.
- For each event template listed below,
click View Template Properties and modify its
channel from dc.out.channel : JMS to dc.out.bus.channel
: JMS.
- */*/command/portalcontrol/activation
- */*/command/portalcontrol/set/dataextensions
- */*/command/system/reload
- */*/command/system/restart
- */*/report/diagnostic/applpong
- */*/report/tag/feedback
- Log in to the WebSphere Application Server administrative console, and
navigate to .
- Select the cluster, such as PremisesCluster, for the Scope.
- Click ibmsensoreventQCF,
and add the WebSphere Sensor Events central
server host name or IP address to the Provider endpoints list.
- Return to the Queue connection factories page
and select the central server node for the Scope.
- Click ibmsensoreventQCF,
and add the WebSphere Sensor Events central
server host name or IP address to the Provider endpoints list.
- Stop and restart WebSphere Application Server.
- Update the config.ini file
to export the system package, com.ibm.CORBA.iiop.
- Go into the profile used for your JMV. This
profile can be found inside of the org.eclipse.osgi_3.3.1.R33x_v20070828.jar file.
- For Java™ 1.5,
open the J2SE-1.5.profile file and copy the org.osgi.framework.system.packages
section to your config.ini file.
- Add com.ibm.CORBA.iiop to the list of packages for the
org.osgi.framework.system.packages.
- Navigate to IHS_HOME\htdocs\en_US\bundles\bundlelists and
edit the dc_core4dts.txt file.
Comment
out the following lines by adding // to the start
of each line:
START com.ibm.mq.osgi.client_6.0.2.5.jar
START com.ibm.mq.osgi.prereq_6.0.2.5.jar
Remove the
comment marks (//) from the start of these lines:
START com.ibm.ws.sibc.jndi_6.0.2.jar
START com.ibm.pvc.jms_1.1.0.20081017.jar
START com.ibm.ws.sibc.jms_6.0.2.jar
Note: If you are running
a non-IBM JVM you also need to remove the comment marks from this
line in the dc_core4dts.txt file: START
com.ibm.ws.sibc.orb_6.0.2.jar
- Verify that Data Transformation service
has connected to the SIBus by going to the IBM_RFID_HOME\logs\E4_0.log file
and looking for a line that says the following:
[INFO] FMBB2628 bridge Pipe E4-SIBus has established its outbound connection.