Install

Rational Developer for System z

Contact us...

1. Install Rational Developer for System z
2. Install TXSeries
1. Installation considerations
2. Installing TXSeries
3. Creation of CICS users and groups
4. Setting up IBM TXSeries Administration Console for administrative tasks on Windows
5. Environment variables created during installation
6. Create CICS Region
7. Install Microsoft Loopback adapter

Install Rational Developer for System z

1. In the RDzJava_Setup folder, run launchpad.exe ()
2. Select a language (i.e English) and click "Install Rational Developer for System Z" ()
3. Select Custom Installation ()
   For an installation of Developer for System z, choose your user role to launch the installation with the recommended set of Developer for System z
   features and bundled offerings for your role. Alternatively, you may choose to launch a custom installation with all Developer for System z features and
   bundled offerings by clicking the corresponding link on the launchpad.
1. System z Traditional Developer Role
   Developers wishing to develop or maintain on CICS or IMS applications, DB2 Stored Procedures, Batch applications, or green-screen interfaces. The developers can also gain access to IBM problem determination tools, CICS explorer interfaces, and Source Code Management systems. 
   
2. Service Developer Role
   
   Developers wanting to develop or maintain traditional workload and to expose System z applications and programs out as Web Services or Service Flows. This also includes the capabilities found in the System z Traditional Developer. 
3. J2EE/WAS Developer Role
   System z developers creating applications and Web interfaces using Java Enterprise Edition that connect to CICS, IMS, DB2, or Batch applications. This also includes the capabilities found in the Service Developer. 
4. Select the packages you want to install and click Next ()
5. Accept the terms in the license agreements and click Next.
6. Create a new package group, set the Installation Directory and click Next ()
7. Leave the Extend an existing Eclipse box un-check and click Next.
8. Make sure the English checkbox (translation) is selected and click Next.
9. Select the features to install and click Next ()
10. For the Help System, select Access help from the Web.  For WAS configuration, check Create a profile and check Enable administrative security on the profile.  Use admin/admin as the User ID and Password.  Click Next ()
11. Review the summary information.  Click Back to make changes or click Install.
12. Installation completed successfully ()

Install TXSeries

Installation considerations

The following topics provide you an introduction on the prerequisites, disk space requirements, directory structure, and so on, which are required for installing TXSeries for Multiplatforms.

1. CICS prerequisites and supported locales
2. CICS directory structure for regions, servers, and clients (/var)
3. Creation of CICS users and groups
4. Environment variables created during installation
5. TXSeries integration with IBM Tivoli Provisioning Manager
6. Possible effects of changing the system clock
7. Metacharacter restrictions
8. Installation verification program

Installing TXSeries

1. Select Install optional software and click TXSeries for Multiplatforms v7.1 ()
2. Click Browse... to locate TXSeries installation files and then click OK ()
3. TXSeries is being prepared for installation ()
4. In the TXSeries window, select English and click OK.
5. Review installation guide and click Next ()
6. Accept the terms in the license agreement and click Next.
7. Specify the installation directory and click Next.  
   Note: To avoid potential problems, install in the specified default directory (i.e C:\opt\cics)
8. Review Pre-Installation Summary and click Next or make changes (click Previous).
9. TXSeries is being installed.  This may take some time ()
10. When Install is complete, you can check/uncheck to view/not view Readme and/or logfile. Click Next.
11. Click Done to quit the installer

Creation of CICS users and groups

During installation of CICS®, the following required user and groups are automatically created:

1. An operating system group named cics.
2. An operating system group named cicsterm.
3. An operating system group named cicssm (on AIX® only).
4. An operating system user named cics.
5. An operating system user named cicssm (on AIX only).

Many CICS procedures are accessible only when you are logged in as root. Other CICS procedures require that you are logged in as a user with root privileges. CICS also requires that the root and cics users be members of the cics and cicsterm groups.

Setting up IBM TXSeries Administration Console for administrative tasks on Windows

On Windows, the TXSeries® light-weight infrastructure service runs as a local system account by default. If you attempt to perform tasks such as creating or destroying CICS® regions or other servers (for example, SFS servers) as a local system account, the create or destroy operation will fail.

To perform these tasks, you must first run the TXSeries light-weight infrastructure service as an administrator by completing the following steps:

1. In your deskstop, right-click the My Computer icon and select Manage ()
2. In the Computer Management window, select Services and Applications\Services, go to Standard tab, right-click TXSeried LWI... service and select Properties ()
3. In the TXSeries LWI... window, select the Log On tab, select This account, enter an administrator user name (i.e charles, or any other user who belongs to the Administrator group), enter Password, Confirm password, and click OK ()

Restart the TXSeries light-weight infrastructure service by right-clicking it and selecting Restart.

Environment variables created during installation

During installation, the CICS® Product Setup program creates or updates these environment variables:

Create CICS Region

Before creating a CICS Region, you should set up the "IBM TXSeries Administration Console for administrative tasks on Windows" and install the "Microsoft Loopback Adapter"

1. Start Administrative Console
   You can start the ad console in two ways:
2. Enter http://localhost/txseries/admin in your web browser or
   
3. Click Start\All Programs\...\IBM TXSeries Administration tool ()
4. In the Login window, enter User Name and Password.  click Login ()
5. In the TXSeries Administration Console, expand Regions, click All Regions, and click Create ()
6. Enter Name and click Submit (
   
   )
7. 
   

Install Microsoft Loopback adapter

The Microsoft Loopback adapter is a testing tool for a virtual network environment where network access is not available. Also, you must use the Loopback adapter if there are conflicts with a network adapter or with a network adapter driver. You can bind network clients, protocols, and other network configuration items to the Loopback adapter, and you can install the network adapter driver or network adapter later while retaining the network configuration information. You can also install the Loopback adapter during the unattended installation process.

To manually install the Microsoft Loopback adapter in Windows XP, follow these steps:

1. Click Start, and then click Control Panel.
2. If you are in Classic view, click Switch to Category View under Control Panel in the left pane.
3. Double-click Printers and Other Hardware, and then click Next.
4. Under See Also in the left pane, click Add Hardware,and then click Next.
5. Click Yes, I have already connected the hardware, and then click Next.
6. At the bottom of the list, click Add a new hardware device, and then click Next.
7. Click Install the hardware that I manually select from a list, and then click Next.
8. Click Network adapters, and then click Next.
9. In the Manufacturer box, click Microsoft.
10. In the Network Adapter box, click Microsoft Loopback Adapter, and then click Next.
11. Click Finish.

After the adapter is installed successfully, you can manually configure its options, as with any other adapter. If the TCP/IP properties are configured to use DHCP, the adapter will eventually use an autonet address (169.254.x.x/16) because the adapter is not actually connected to any physical media.

Note By default, TCP/IP properties are configured to use DHCP.