First Look: iWay Container Edition 9.2

[Joseph Vogel]

iWay will now distribute a docker image which when instantiated will act as an ISM server very similar to a standalone server deployment.  We are going to demonstrate iWay Service Manager running in a docker container with support for persistence. In this tutorial we will be using Docker Desktop running on a Microsoft Windows 2011 operating system

 

First we need to load iWay Container Edition into Docker desktop. To do this on Windows open a command prompt and navigate to a directory which contains the docker file tar file. To load the docker image enter the following:
 

docker load -i iwayContainerEdition92.tar

Bringing up Docker Desktop we should see the newly added docker image, iwaycontainer. 

 

To create a docker container using this docker image click on the "run" icon (right arrow) on the right. A dialog will appear as shown below:

 

The most minimal configuration for this container would be to map the iSM Console port as well as the iSM IBSE SOAP port.
For support of persistence which means that when the container is brought down it remembers its previous state you will need to map to volumes. 
One for ISM's configurations and the other for its logging services 

 

HTTP/HTTPS Port Assignments

Port Mappings	Exposed Port	Required	Description
Port Mappings	Exposed Port	Required	Description
ISM Runtime Console	9999	Yes	Used to expose the ISM Runtime Console
IBSE SOAP Port	9000	Yes	Used for both iWay Business Service (SOAP) and iWay Integration Tools, IIT
Envoy	8000	No	Used to be monitored via SPOG/Sentinel technology

Container Persistence Layer

Volume Mapping	Internal Location	Description
Configurations	/opt/ibi/iway9/conf	Used to persist ISM configurations and data
Logging	/opt/ibi/iway9/logs	Used to persist collected logging information

 

Clicking the Run button as shown above should start ISM in a container as shown below:

 

Bringing up a Web browser and logging into the iSM runtime console using the standard iway/iway userid/password combination
should result in the following:

 

 

A running version of iWay Service Manager running a docker container. 
 

Customizing the Deployment

The limitations of docker desktop does not allow us to customize the docker run command to the extent that we need.
In a production environment you most likely would want to control the hostname of the container as well as the domain of this console.
To bring up iWay Service Manager running in a container like this you will need to open a command prompt and enter the following:

docker run -v "/c/dev7/test/mylogs:/opt/ibi/iway9/logs" -v "/c/dev7/test/myconfig:/opt/ibi/iway9/conf" -p 9999:9999 -p 9000:9000  -e IWAYWHITELIST=TIBCO-R91391RY --hostname=TIBCO-R91391RY --name myiway iwaycontainer

where:

Mounts

Source	Target	Description
/opt/ibi/iway9/logs	/c/dev7/test/mylogs	Custom log directory to support persistence
/opt/ibi/iway9/conf	/c/dev7/test/myconfig	Custom configuration directory to support persistence

 

Ports

Source	Target	Description
9999	9999	Mapped Console port
9000	9999	ISM Soap Port

 

Environmental Variables

Variable	Value	Description
IWAYWHITELIST	<YOUR HOSTNAME>	Comma delimited domain names of the server host (used to prevent CSRF attacks)

 

Once running this ISM container will be accessible via both: http://localhost:9999 and  http://TIBCO-R91391RY:9999

This should get you a sneak peak into what's coming in iWay 9.2.

Look for a more detailed discussions on this topic and other containerization techniques involving iWay in the near future. Comments and feedback are always appreciated.
Thanks..

 

 

 

 

 

 

 

Edited April 17 by Joseph Vogel