Services/API deployment in IIB 10

Step 1:

Telnet Service IP and Port on production to verify connection between the servers.

Step 2:

Open JKS file on IBM Keyman tool and add certificate of ICAP Service on it.

Step 3:

For Broker Level:

mqsichangeproperties <Node-Name> -b httplistener -o HTTPSConnector -n keystoreFile — v “<Location of JKS file>”

For EG Level:

mqsichangeproperties <Node-Name> -e ass -o HTTPSConnector -n keystoreFile -v “<Location of JKS file>”

Step 4:

Restart Broker or EG.

Step 5:

Add entry of IP and DNS name of service on host file.

Step 6:

Import project zip on IIB toolkit workspace.

Step 7:

Change all MQ manager name, queues names, service IPs and trace file location on flow according to production.

Step 8:

Create backup of previous project.

Step 9:

Create bar file of whole project.

Step 10:

Deploy bar file in execution group EG.

For Cache Service Deployment

Step 1:

Check all entries on config.properties file according to production.

Step 2:

Place config.properties and UserRight.properties file on this location “/FBANKIIB/AppConfig/ESB-Config”

Step 3:

Stop Integration node

Step 4:

Executing this command to enable cache on broker

mqsichangebroker <Node Name> -b default

Step 5:

Start Integration node

Step 6:

Deploy UpdateGlobalCache service on execution group.

Step 7:

Execute below URL to check cache uploaded or not

http://{Production -IP}:{Production-Port}/UpdateGlobalCache

Step 8:

If getting successful response then its ok. Other wise check config.properties file

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adil Abdullah

Adil Abdullah

Currently working as Full stack Java developer for Swedish company Easit AB. Working on Java and IBM stack.