Using Horizontal Clusters on WebSphere
The JD Edwards EnterpriseOne Transaction Server installation is configured with filestore for the messaging engines by default. If you use Horizontal cluster it is mandatory that you use the JDBC store.
To use horizontal clusters on WebSphere:
Go to Service Integration > Buses.
On Buses, select ORABus.
On Buses, select the Bus Members.
On Buses, Bus members, click on the link for the cluster.
On Bus members, click Additional Properties > Messaging engines.
Select the messaging engines created by default with the RTE installation.
Click the Remove messaging engine button to delete them.
On Buses, OraBus, Bus members, testcluster, Messaging engines for testcluster, click the Add messaging engine button.
On Select message store type, select the radio button for Data store.
Click the Next button.
On Specify data store properties, complete these fields:
Data source JNDI name
Enter a name for the JNDI. For example, JDBC1.
Schema name
Enter a name for the schema. For example, IBMWSSIB.
Authentication alias
Enter an authentication alias. For example, <machine>CallManager01/JDBC1.
Click the Finish button.
Save changes to master configuration.
Repeat the same for creating Message Engines for other members of the cluster.
On deleting the default message engines created during the installation of the RTE application, all the Queues are also deleted. As a result, you must re-add these queues manually or you can run the rte.py script passing the required parameters.
Run this wsadmin command before starting the clustered servers/RTE instance.
Go to the <WAS_DMGR_PROFILE_LOC>\bin on command prompt.
Run the following command on the prompt:
wsadmin -lang jython -f <JDE_AGENT_HOME>\bin\rte.py createSIBDestination <Bus-name> <Nodename> <Server_name> <Cluster_Name> <profilepath> <queue_names>
For example:
Z:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>wsadmin -lang jython -f Z:\JDE_HOME_WAS7\bin\rte.py createSIBDestination ORABus dnvmtqa30Node01 MyServer1 MyCluster1 Z:\IBM\WebSphere\AppServer\profiles\Dmgr01 SubQueue00,SubQueue01,SubQueue02,SubQueue03,SubQueue04,SubQueue05,SubQueue06,SubQueue07,SubQueue08,SubQueue09,SubQueue10,SubQueue11,SubQueue12,SubQueue13,SubQueue14,SubQueue15,EventQueue00,EventQueue01,EventQueue02,EventQueue03,TriggerQueue,SourceRouteQueue,ESBQueue00
Pass input as NULL where not applicable. For a cluster, input for Nodename and Server_name can be passed as NULL.