Saturday, May 29, 2010

TXSeries Installation


IBM TXSeries 7.1

Contact us...


Install TXSeries

Installation considerations

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.

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 Microsoft Loopback adapter".  You also have to disable Symantec client firewall if you are using it. 

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.

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
  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. 

Disable Symantec Client Firewall

If you are using Symantec Client Firewall, disable it temporarily.

Create a CICS Region

  1. Start TXSeries Administration Console
    You can start the ad console in two ways:
    1. Enter http://localhost/txseries/admin in your web browser or
    2. Click Start\All Programs\...\IBM TXSeries Administration tool ()
  2. In the Login window, enter User Name and Password with Administrator privileges.  click Login ()
  3. In the TXSeries Administration Console, expand Regions, click All Regions, and click Create ()
  4. Enter new CICS region name (i.e TestR), leave Group ID blank, select Use SFS (File Management) and click Submit ()
  5. The CICS region and default SFS server is created ()
  6. The CICS region and default SFS server is started ()

After creating a CICS region, edit the region environment file (c:\var\cics_regions\CICSRegion\environment) and add line: PATH=d:\systemZ\bin;%PATH%.  This command tells the CICSRegion where to pick up the correct COBOL runtime environment.

Configure a CICS local terminal

Edit the CICS local terminal initialization file

cicslcli.ini (C:\opt\cics\bin ) is the CICS local terminal initialization file.

cicslcli.ini file excerpt
cicslcli.ini file excerpt
;Server = CICS01 ; Arbitrary, unique name for the server
Server = TestR ; Arbitrary, unique name for the server
Description = Named Pipe Support for local client ;
Protocol = LOCALCLI ; Matches with a Driver section below
NetName = 00.00.00.00 ; Dummy
NamedPipeName = CICSCC ; Must match servers named pipe
  1. Change Server from CICS01 to TestR.
  2. Remember CICSCC (NamedPipeName).  You will be using this name to configure the Listerner
  3. Close and save cicslcli.ini file

Configure a Listener

  1. Open the TXSeries Web administration console
  2. Expand Regions, expand the CICS region that you defined, i.e TestR, click Listener, and click Add ()
  3. Set the Listerner Definition window as shown and click Submit ()
    1. Listener Name = TestL
    2. Activate resource at cold start? = Yes
    3. Resource description = Listener Definition
    4. Protocol Type = Named Pipe
    5. Number of TCPIP listener processes to use = 1
    6. local Named Pipe name = CICSCC
    7. Click Submit
  4. The Listener Definition is completed successfully ()
  5. You have to re-start the CICS region to apply the changes.

Testing the setup

Make sure that you re-start the CICS region before testing the setup you did above.

  1. From the Windows® Start menu, select All Programs > IBM > TXSeries for Multiplatforms V7.1 > Start Local Terminal. The CICSTERM - CICS server selection window opens ()
  2. Select the correct CICS server for your CICS region and click OK ()
  3. When the CICS terminal starts, type: CEMT and press Ctrl, which is the 3270 terminal Return key 
  4. If the transaction runs properly, the CICS terminal screen will show something like the following ()

2 comments:

  1. How is TXSeries integrated with WBSF? Any thoughts on that?.

    ReplyDelete
  2. You integrate TXSeries with WBSF through Websphere Integration Developer.

    WBSF should be primarily use for enabling dynamic assembly.

    ReplyDelete