Previous    Contents    Index    DocHome    Next

iPlanet Application Server Enterprise Connector for CICS Administrator's Guide

 

Chapter 2 Installation
 

This chapter describes how to install, start, and uninstall the iPlanet Application Server Enterprise Connector for CICS.

This chapter contains information about the following topics:

• Software Prerequisites




• Hardware Requirements




• Installing on Windows NT




• Uninstalling from Windows NT




• Installing on Solaris




• Uninstalling from Solaris




• Upgrading or Re-installing Issues




• Post Installation Issues

 

 

Software Prerequisites

---

The following software prerequisites are necessary to install the iPlanet Application Server Enterprise Connector for CICS:

• the iPlanet Application Server 6.0 SP1 must be installed




• the iPlanet Application Server Unified Integration 6.0 SP1 must be installed




• CICS software on the mainframe must be installed




• One of the following web browsers should be installed:
• Netscape Communicator 4.5




• Microsoft Internet Explorer 4.0 (NT only)

 

 

• A web server, such as iPlanet Web Server (iWS) and iPlanet Application Server 6.0 SP1, must reside on the same system on which you are installing the connector.



---

Caution

The CICS connector operates with the iPlanet Application Server, therefore it must be installed in the same directory in which the iPlanet Application Server is installed.

---



 
 

Supported Versions of CICS

The iPlanet Application Server Enterprise Connector for CICS supports IBM CICS running on OS/390. The required releases are MVS 5.2.2 and CICS ESA 4.1 and above with current APARS.

iPlanet Application Server Enterprise Connector for CICS includes installation and configuration for both TCP/IP and SNA (APPC) protocols.
 
 

Hardware Requirements

---

The following hardware requirements are necessary for installing the connectors.
 

Computers and Operating Systems
 

• One of the following operating systems:
• Microsoft Windows NT version 4.0 with Service Pack 5




• Sun SPARC running Solaris 2.6 or Solaris 8

 

 

• Memory Per CPU: 256 MB minimum; 512 MB recommended




• Available disk space: 200 MB for NT, 400 MB for Solaris

 

 

Preparing to Install 

---

Before installing the iPlanet Application Server Enterprise Connector for CICS complete the following steps:

• Verify the CICS Server connectivity.




• Stop the iPlanet Application Server if it is running.Without stopping the application server, the installation program may not be able to overwrite files currently in use.




• Read the iPlanet Application Server Enterprise Connector for CICS Release Notes for any last minute updates.

 

 

Installing on Windows NT

---

The following describes the procedures for installing and uninstalling the CICS Enterprise Connector on Windows NT.

You must be logged in to Windows NT as the administrator to install the CICS Enterprise Connector.
 

To Install on Windows NT
 

1. Read the README.txt file on the CD-ROM.




2. Copy NT/inscics.zip from the CD-ROM into a temporary local directory.




3. Unzip inscics.zip, then run setup.exe.




4. Read the Welcome message and click on the Next button. See Figure 2-1.




5. Follow the instructions on the screen to progress through the introduction.

 

 

Figure 2-1    Welcome Message

6. Thoroughly read and understand the licensing information before installing, and accept the license agreement. See Figure 2-2.

 

 

Figure 2-2    Software License Agreement

7. Choose your installation directory, then click Next. See Figure 2-3.

 

 

Figure 2-3    Location of Installation

---

Note	You must install the iPlanet Application Server Enterprise Connector for CICS in the same directory as where you installed iPlanet Application Server and UIF.

---

8. Click Next to continue.

Select the Enterprise Connector for CICS 6.0 check box. See Figure 2-4.


 

 

Figure 2-4    Components to Install

9. Choose the protocol you prefer, either TCP/IP or SNA protocol, by marking the appropriate button, and then click Next. See Figure 2-5.



---

Note	See Chapter 3 "Installing the Mainframe Component" for a description of alternatives to connect the CICS Enterprise Connector to the mainframe.

---



 
 

Figure 2-5    Select TCP/IP or SNA Protocol

Continue with Step 10 if you selected TCP/IP protocol or continue with Step 11 if you selected the SNA protocol.

 

 

10. Type in your CICS Backend System definition for TCP/IP and click Next. 

The Configuration Summary shown in Figure 2-8 is displayed.


 

 

Figure 2-6    TCP/IP Protocol

11. Enter the CICS Backend System information for APPC and click Next. 

The Configuration Summary shown in Figure 2-8 is displayed.


 

 

Figure 2-7    SNA Protocol

12. Review the configuration summary and click install if the information is correct.

 

 

Figure 2-8    Configuration Summary

13. Click Install if the information is correct.




14. (Optional) Figure 2-9 displays the possible warning window(s) that can appear if the installer detects that the CICS Enterprise Connector is already installed. Choose Yes to overwrite the existing adapter type and all sample data source definitions shipped with the CICS Enterprise Connector. User defined data sources are not overwritten. Select No if you are simply adding another iPlanet Application Server instance to an existing cluster.

Confirm your decision.


 

 

Figure 2-9    Setup File Copy

---

Caution

You must restart your computer after you complete the installation.

---

15. After installing the CICS Enterprise Connector on Windows NT, proceed with the Mainframe component installation as described in Chapter 3. 

If you selected a direct APPC connection from NT, SNA/APPC on NT must be configured as explained in the following section.


 

 

SNA/APPC Configuration for Windows NT

---

A sample configuration file for IBM Personal Communications (PCOMM) product for Windows NT is listed, and supplied in: 

<instdir>\APPS\adapters\CICS\backend\appconfig.ACG

Load this file into your PCOMM SNA Node Configuration as a basis for changes and adaptations to your SNA/APPC setup. 

 
Code Example 2-1    PCOMM LU6.2 Configuration Definitions on a PC 

---

*TSTue Mar 7 10:57:58 2000

NODE=(

ANYNET_SUPPORT=NONE

CP_ALIAS=SHMUELNT

DEFAULT_PREFERENCE=NATIVE

DISCOVERY_SUPPORT=NO

FQ_CP_NAME=P390.SHMUELNT

NODE_ID=05D00000

NODE_TYPE=END_NODE

REGISTER_WITH_CDS=1

REGISTER_WITH_NN=1

)

PORT=(

PORT_NAME=LANX_04

ACTIVATION_DELAY_TIMER=30

DELAY_APPLICATION_RETRIES=1

DLC_DATA=00000000000004

DLC_NAME=LAN

IMPLICIT_CP_CP_SESS_SUPPORT=1

IMPLICIT_DEACT_TIMER=0

IMPLICIT_DSPU_SERVICES=NONE

IMPLICIT_HPR_SUPPORT=1

IMPLICIT_LIMITED_RESOURCE=NO

IMPLICIT_LINK_LVL_ERROR=0

LINK_STATION_ROLE=NEGOTIABLE

MAX_ACTIVATION_ATTEMPTS=10

MAX_IFRM_RCVD=8

MAX_RCV_BTU_SIZE=32767

PORT_TYPE=SATF

RETRY_LINK_ON_DISCONNECT=1

RETRY_LINK_ON_FAILED_START=1

RETRY_LINK_ON_FAILURE=1

PORT_LAN_SPECIFIC_DATA=(

ACK_DELAY=100

ACK_TIMEOUT=3000

ADAPTER_NUMBER=9999

BUSY_STATE_TIMEOUT=60

IDLE_STATE_TIMEOUT=30

LOCAL_SAP=04

MAX_RETRY=10

OUTSTANDING_TRANSMITS=16

POLL_TIMEOUT=3000

POOL_SIZE=16

REJECT_RESPONSE_TIMEOUT=30

TEST_RETRY_INTERVAL=8

TEST_RETRY_LIMIT=5

XID_RETRY_INTERVAL=8

XID_RETRY_LIMIT=5

)

)

LINK_STATION=(

LS_NAME=LINK0000

ACTIVATE_AT_STARTUP=1

ACTIVATION_DELAY_TIMER=-1

ADJACENT_NODE_TYPE=LEARN

AUTO_ACTIVATE_SUPPORT=0

CP_CP_SESS_SUPPORT=1

DEFAULT_NN_SERVER=0

DELAY_APPLICATION_RETRIES=0

DEST_ADDRESS=42000000006604

DISABLE_REMOTE_ACT=0

DSPU_SERVICES=NONE

ETHERNET_FORMAT=1

HPR_LINK_LVL_ERROR=0

HPR_SUPPORT=0

INHERIT_PORT_RETRY_PARMS=1

LIMITED_RESOURCE=NO

LINK_DEACT_TIMER=0

LINK_STATION_ROLE=USE_ADAPTER_DEFAULTS

MAX_ACTIVATION_ATTEMPTS=-1

MAX_IFRM_RCVD=0

MAX_SEND_BTU_SIZE=32767

NODE_ID=05D00000

PORT_NAME=LANX_04

RETRY_LINK_ON_DISCONNECT=0

RETRY_LINK_ON_FAILED_START=0

RETRY_LINK_ON_FAILURE=0

SOLICIT_SSCP_SESSION=0

TG_NUMBER=0

USE_DEFAULT_TG_CHARS=1

)

DLUR_DEFAULTS=(

DEFAULT_PU_NAME=SHMUELNT

DLUS_RETRY_LIMIT=65535

DLUS_RETRY_TIMEOUT=5

)

MODE=(

MODE_NAME=BLANK

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#CONNECT

DEFAULT_RU_SIZE=1

MAX_NEGOTIABLE_SESSION_LIMIT=256

MAX_RU_SIZE_UPPER_BOUND=1024

MIN_CONWINNERS_SOURCE=128

PLU_MODE_SESSION_LIMIT=256

RECEIVE_PACING_WINDOW=3

)

MODE=(

MODE_NAME=#BATCH

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#BATCH

DEFAULT_RU_SIZE=0

MAX_NEGOTIABLE_SESSION_LIMIT=256

MAX_RU_SIZE_UPPER_BOUND=2048

MIN_CONWINNERS_SOURCE=128

PLU_MODE_SESSION_LIMIT=256

RECEIVE_PACING_WINDOW=20

)

MODE=(

MODE_NAME=#BATCHSC

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#BATCHSC

DEFAULT_RU_SIZE=1

MAX_NEGOTIABLE_SESSION_LIMIT=256

MAX_RU_SIZE_UPPER_BOUND=2048

MIN_CONWINNERS_SOURCE=128

PLU_MODE_SESSION_LIMIT=256

RECEIVE_PACING_WINDOW=3

)

MODE=(

MODE_NAME=#INTER

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#INTER

DEFAULT_RU_SIZE=1

MAX_NEGOTIABLE_SESSION_LIMIT=256

MAX_RU_SIZE_UPPER_BOUND=4096

MIN_CONWINNERS_SOURCE=128

PLU_MODE_SESSION_LIMIT=256

RECEIVE_PACING_WINDOW=20

)

MODE=(

MODE_NAME=#INTERSC

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#INTERSC

DEFAULT_RU_SIZE=1

MAX_NEGOTIABLE_SESSION_LIMIT=256

MAX_RU_SIZE_UPPER_BOUND=2048

MIN_CONWINNERS_SOURCE=128

PLU_MODE_SESSION_LIMIT=256

RECEIVE_PACING_WINDOW=7

)

MODE=(

MODE_NAME=APPCMODE

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#CONNECT

DEFAULT_RU_SIZE=1

MAX_NEGOTIABLE_SESSION_LIMIT=128

MAX_RU_SIZE_UPPER_BOUND=4096

MIN_CONWINNERS_SOURCE=16

PLU_MODE_SESSION_LIMIT=32

RECEIVE_PACING_WINDOW=1

)

MODE=(

MODE_NAME=QPCSUPP

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#CONNECT

DEFAULT_RU_SIZE=1

MAX_NEGOTIABLE_SESSION_LIMIT=52

MAX_RU_SIZE_UPPER_BOUND=1024

MIN_CONWINNERS_SOURCE=26

PLU_MODE_SESSION_LIMIT=52

RECEIVE_PACING_WINDOW=2

)

MODE=(

MODE_NAME=QSERVER

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=#CONNECT

DEFAULT_RU_SIZE=1

MAX_NEGOTIABLE_SESSION_LIMIT=64

MAX_RU_SIZE_UPPER_BOUND=1024

MIN_CONWINNERS_SOURCE=0

PLU_MODE_SESSION_LIMIT=64

RECEIVE_PACING_WINDOW=7

)

MODE=(

MODE_NAME=SNASVCMG

AUTO_ACT=0

COMPRESSION=PROHIBITED

COS_NAME=SNASVCMG

DEFAULT_RU_SIZE=0

MAX_NEGOTIABLE_SESSION_LIMIT=2

MAX_RU_SIZE_UPPER_BOUND=512

MIN_CONWINNERS_SOURCE=1

PLU_MODE_SESSION_LIMIT=2

RECEIVE_PACING_WINDOW=1

)

PARTNER_LU=(

FQ_PLU_NAME=P390.A06CICS2

ADJACENT_CP_NAME=P390.P390SSCP

CONV_SECURITY_VERIFICATION=1

MAX_MC_LL_SEND_SIZE=32767

PARALLEL_SESSION_SUPPORT=1

PARTNER_LU_ALIAS=A06CICS2

PREFERENCE=USE_DEFAULT_PREFERENCE

)

CPIC_SIDE_INFO=(

SYM_DEST_NAME=SRVX

CONVERSATION_SECURITY_TYPE=NONE

MODE_NAME=APPCMODE

PARTNER_LU_NAME=P390.A06CICS2

TP_NAME=SRVX

TP_NAME_TYPE=APPLICATION_TP

)

ADJACENT_NODE=(

FQ_CP_NAME=P390.P390SSCP

LU_ENTRY=(

FQ_LU_NAME=P390.A06CICS2

)

)

SHARED_FOLDERS=(

CACHE_SIZE=256

)

VERIFY=(

CFG_MODIFICATION_LEVEL=13

CFG_VERSION_LEVEL=1

)

Initializing the SNA/APPC Protocol Stack in Windows NT
 

1. Select Start > Programs > IBM Personal Communications > Administrative and PD Aids > SNA Node Operations.




2. Select Operations > Start Node.

The Personal Communications Node Operations window appears.


 

 

3. Select Operations > CNOS Initialize.

 

 

Uninstalling from Windows NT

---

This procedure is used to uninstall the iPlanet Application Server Enterprise Connector for CICS from Windows NT.
 

To Uninstall from Windows NT
 

1. Select Start > Programs - iPlanet Application Server 6.0 > Uninstaller. 

The iPlanet Uninstall window appears. See Figure 2-10.


 

 

Figure 2-10    iPlanet Uninstall

2. Deselect all components except the Enterprise Connector for CICS 6.0.




3. Click Sub Components.

The uninstaller checks for dependencies between subcomponents and the main component. If you try to deselect a component and its subcomponent are toggled on, a warning message appears.


 

 

Deselecting the CICS Enterprise Connector 

Deselect items in the following order:

1. Deselect Netscape Server Produect Core components.




2. Deselect Administration Services and Netscape Directory Suite.




3. Deselect iPlanet Application Server 6.0.

 

 

To Deselect the iPlanet Application Server
 

1. Deselect Application Server 6.0 core binaries.




2. Deselect Web Connector Plug-in component.




3. Deselect Administrator's component.




4. Deselect Deployment Manager component.




5. Deselect core Server component.




---

Caution

If you do not follow the above mentioned order of deselections, alert messages are displayed and you may not be able to deselect the desired option.

---


Click the Continue button to return to the main uninstall menu.
 
 

6. Click Uninstall.

The Uninstall message is displayed. See Figure 2-11.


 

 

Figure 2-11    Uninstall

7. Click OK to complete the uninstallation procedure.

The Enterprise Connector for CICS 6.0 has been uninstalled. Some files may remain. Check for these files at the location listed and manually remove them.


 

 

Installing on Solaris

---

The following is the installation process for the iPlanet Application Server Enterprise Connector for CICS on a Solaris operating system.

To ensure that you have everything necessary to complete the installation, review this section before starting the installation.
 

Pre-installation
 

1. Insert the CICS Enterprise Connector Install CD-ROM into the CD-ROM drive.




2. Mount the CD-ROM, for example, /cdrom/cdrom0.




3. Read the README.txt file on the CD-ROM.

 

 

To Install on Solaris
 

1. Copy the Solaris/inscics.tar file from the CD-ROM into a temporary local directory.




2. Untar the inscics.tar file.

For example: tar -xvf inscics.tar


 

 

3. Run the ./setup command from the inscics directory

Follow the instructions of the installation program. During installation, press the following key sequences for:

CTRL+B to back up to the previous screen.

CTRL+C to cancel the installation program. This results in an incomplete installation. To install again, rerun the installation program from the beginning.


 

 

4. Figure 2-12 is displayed. Either press enter or type Yes to continue.

 

 

Figure 2-12    Welcome

5. Enter Yes and the License message appears. See Figure 2-13.

 

 

Figure 2-13    License

6. Thoroughly read and understand the licensing information before installing and then enter Yes.

The Selection message appears. See Figure 2-14.


 

 

Figure 2-14    Selection

7. Press Enter.



---

Note	The iPlanet Application Server must already be installed on your system. You must perform this step to proceed with the connector installation.

---




The Location message appears. See Figure 2-15.


 

 

Figure 2-15    Location

8. To accept the default shown in the brackets, press Enter.

Otherwise, enter in the iPlanet Application Server installation directory, and then press Enter.

The Components message appears. See Figure 2-16.


 

 

Figure 2-16    Components

9. Press Enter.

The Subcomponents message appears. See Figure 2-17.


 

 

Figure 2-17    Subcomponents

10. Press Enter.

The Domain Name message appears. See Figure 2-18.


 

 

Figure 2-18    Domain Name

11. Click Enter to accept the default or enter another name <host.domain.com>.

The System User message appears. See Figure 2-19.


 

 

Figure 2-19    System User

12. Enter in a System User, or accept the default shown in brackets, and press Enter.

The System Group message appears. See Figure 2-20.


 

 

Figure 2-20    System Group

13. Enter in a System Group, or accept the default shown in brackets, and press Enter.

The Relay Host message appears. See Figure 2-21.


 

 

Figure 2-21    Relay Host

---

Note	The following steps are concerned with information from the mainframe.

---

14. Type in the Mainframe TCP/IP Host name and press Enter.

The Relay Port message appears. See Figure 2-22.


 

 

Figure 2-22    Relay Port

15. Type in the Relay Port, and press Enter.

The LU (logical unit) message appears. See Figure 2-23.


 

 

Figure 2-23    Logical Unit

16. Enter the LU name and press Enter.

The LU name is the VTAM application LU name for CICS.

The User ID and Password screen appears. See Figure 2-24.


 

 

Figure 2-24    User ID and Password

17. Type in the User ID and Password, and press Enter.

This must be a valid User ID and Password pair as defined in the CICS system.

The Final installation screen appears. See Figure 2-25.


 

 

Figure 2-25    Final

18. Press Enter to continue.

A Work in Progress screen appears as the connector and related files are installed. When finished, you are instructed to restart all iPlanet Application Server engines before running any sample application.


 

 

19. Restart iPlanet Application Server engines.

To restart the iPlanet Application Server engines execute the following script:

<instdir>/ias/bin/KIVAes.sh stop

<instdir>/ias/bin/KIVAes.sh start


 

 

20. Continue with Chapter 3 "Installing the Mainframe Component".

 

 

Uninstalling from Solaris

---

This procedure is used to uninstall iPlanet Application Server Enterprise Connector for CICS from Solaris.
 

To Uninstall from Solaris
 

1. Go to the installation directory /user/iplanet/ias6 and enter the following command:

./uninstall

A list of uninstall component options appears. See Figure 2-26.


 

 

Figure 2-26    Uninstall Component Options

2. Select the specific product components you want to uninstall and click Enter.

The Uninstall Subcomponents message appears. See Figure 2-27.


 

 

Figure 2-27    Uninstall Subcomponents

3. Press Enter.

The Uninstalling message appears. See Figure 2-28.


 

 

Figure 2-28    Uninstalling

The Enterprise Connector for CICS 6.0 SP1 has been uninstalled. Some files may remain. Check for these files and manually remove them.

 

 

Upgrading or Re-installing Issues

---

If upgrading an earlier version or reinstalling the current version of the CICS Enterprise Connector, the installation procedure overwrites the currently installed files. Uninstalling the current version is not required.

The Uninstaller removes common files in multi-connector installation.When uninstalling one of several connectors, such as R/3, PeopleSoft, or CICS, the common directories /ias/APPS/console and /ias/APPS/ecu may be deleted. You must copy these directories back to APPS directory from /ias/APPS/UIF backup for the CICS connector to function correctly. Installation of multiple enterprise connectors for multiple EISs (R/3, Tuxedo, and PeopleSoft) on the same iPlanet Application Server is allowed.

---

Note	To avoid problems with overwriting files in use, stop the iPlanet Application Server before installing any new software. Always backup the current files prior to installation including the UIF Repository content.

---

 

To Uninstall a Connector on Windows NT

If you want to uninstall a connector from a Windows NT machine that has more than one connector installed, perform the following tasks. 

1. Uninstall the connector. Refer to Chapter 2 in the Administrator's Guide.

During the uninstallation procedure the connector files shown in the right pane, see Figure 2-29, are removed from the iPlanet/iAS6/ias directory and moved to the UIFbackup/console directory. The connector files need to be copied back to their original location. 


 

 

Figure 2-29    Uninstalling Connector

2. Copy the console specific directories, the top level directory and the connector specific directories to the ias/Apps/console for the following folders: 
• constants 




• exceptions 




• ftp 




• gui 




• model 

 

 

3. All the other directories, with all their included files, and the LocalDebug.class should be copied back. 




4. Copy the following connector files to the console directory: 
• Appltab 




• ldobuffer.dll. 

 

 

To Uninstall from Solaris

If you want to uninstall an Enterprise Connector from a Solaris machine that has more than one connector installed, perform the following tasks. 

1. Uninstall the connector. Refer to Chapter 2 in the Administrator's Guide.

During the uninstallation procedure the connector files are removed from the iPlanet/iAS6/ias directory and moved to the UIFbackup/console directory. The connector files need to be copied back to their original location. 


 

 

2. Copy the console specific directories, the top level directory and the connector specific directories to the ias/APPS/console for the following folders: 
• constants 




• exceptions 




• ftp 




• gui 




• model 

 

 

3. All the other directories, with all their included files, and the LocalDebug.class should be copied back. 

 

 

Post Installation Issues

---

The following issues are described:

• Activating the Samples through NT or Solaris




• Copying Files in Webless Installation

 

 

Activating the Samples through NT or Solaris

After installing the CICS Enterprise Connector you can verify that your installation succeeded and run the CICS samples provided.

For more information on how to activate and run CICS samples, see Chapter 4 of the iPlanet Application Server Enterprise Connector for CICS Developer's Guide.
 

Copying Files in Webless Installation 

In a webless installation, the web server and iPlanet Application Server reside on separate machine. In this configuration mode, the iPlanet Application Server Enterprise Connector for CICS installation procedure does not automatically copy the index.html file pertaining to connector samples to web server document root directory. 

To run the samples shipped with the iPlanet Application Server Enterprise Connector for CICS, an index.html file must be copied manually from the iPlanet Application Server instance to web server instance. 
 

To Copy Files to Run the Program Samples
 

1. Create the cicsSamples directory under the web server document root directory. 

For example, <iWS installdir>/docs/cicsSamples. 


 

 

2. Copy the index.html file from <iASrootdir>/ias/APPS/adapters/htmldocs/cics/cicsSamples directory to <iWS installdir>/docs/cicsSamples directory on web server machine.