Skip to main content

Posts

Configuring Cluster in IBM Sterling B2B Integrator

In this article, I will show you how to configure a horizontal cluster in IBM Sterling B2B Integrator  with two nodes.   Cluster setup provides 24x7 high availability. Even if one of the node goes down, the other node can serve the requests. Cluster is needed to share the work load which is possible through load balancing in Web server. The nodes in the cluster share the same database and they ensure that all the nodes are consistent and show the same output to customer. There are two ways to install Sterling B2B Integrator :  a. Using GUI. b. Using Response files.  In this article, I have used response files for installing Sterling Integrator v5.2.6.1 with ifix level 5 . Starting from version 5.2.6, Sterling Integrator uses IBM Installation Manager (IIM) for installation.  In Node1, install sterling integrator in the same way as you do for a standalone system.  1. Set lang as en_US. export LANG=en_US 2. echo $LANG en_US 3. Install the base version 5.2.6.1. Get the insta
Recent posts

Document Keyword Replace Service in IBM Sterling B2B Integrator

In IBM Sterling B2B Integrator, there are situations where you want to replace a specific character in a document with another character. Document Keyword Replace service provides you the facility to  find and replace text in a document. You need to configure a Service and Business Process for this functionality in IBM Sterling B2B Integrator.   Please do the following to create and configure the service : 1. Login to IBM Sterling Integrator 5.2.6.1.  Go to Deployment - Configuration. Create a New Service of type : Document Keyword Replace Service. 2. Enter Keyword start and end definition as $ as shown below. Click Next. 3. Check the Checkbox to enable the service for Business Processes as shown below : 4. Click Finish. The Service is now created. 5. Go to Business Processes - Manager. Create a Process Definition "DKR_regular". This is the process definition xml.   Example:1 <process name="DKR_regular">  <sequence>   <operation nam