There are two ways to create and maintain multiple environments on the iSeries using Attunity AIS. The purpose of these environments can be used to separate either business entities and the source files they use, or to separate environments like DEV, Q/A and PROD. In either case these are logical definitions that can easily be maintained via simple CL commands and the Attunity Studio product installed on a Windows machine for administration. There are two ways of handling these scenarios. One way is by using internal definitions in Attunity to separate the environments, we'll call this a logical separation, and the other way is to install the product in two separate libraries on the same machine, we'll call this a physical separation. Depending on the type of configuration you want to use involves the manipulation of the environment, job descriptions you define and Attunity variables set upon start up and execution of the daemon and servers.

1.) Logical separation:

A logical separation involves creating a second daemon configuration using customer workspaces, customer bindings and customer data sources, adapters and so on. Once these definition have been defined two Attunity daemons could be started on separate port sharing the same executable code under one Attunity library and also sharing the same IFS directory structure to store the Attunity repository data files and log files. This method requires less involvement in the native iSeries environment and more initial overhead defining the Attunity definitions. Startup would be done using our IRPCD command starting two daemons up on two different ports specifying the daemon configuration name in the startup command (e.g. CALL IRPCD -L 10.10.10.10:2551 START IRPCD and CALL IRPCD -L 10.10.10.10:2552 START IRPCD2)
The main exception to this type of separation is that all of the jobs that run under the subsystem must run as the same ID. In this way there is no separation via the native iSeres security and only via the port specified by the daemon startup.

2.) Physical separation:

A physical separation means the two separate installations of the Attunity product a performed in two separate libraries using two separate sets of IFS directories. The internal configurations do not need to be modified as much and each environment can be owned and executed by separate iSeries user ID's. The main difference in using this method is maintaining a set of CL scripts, job descriptions and possibly subsystem definitions for the two environments. Also, when both daemons are running you want to have the NAVROOT environment variable removed from the system entirely allowing the setting at start up to be cached with the daemon. This requires the submit job parameter CPYENVVAR=YES to be set when the daemon start up is submitted.

A zip file has been attached containing basic CL source for the second scenario. The daemon start up CL scripts can be used for the first scenario independently.