Chapter 1   Installing the Enterprise Connector


The iPlanet Application Server Enterprise Connector for CICS enables you to build interactive web-based applications that accesses data stored in a CICS database. These web-based applications may be for electronic commerce, or for any management, financial, distribution, and manufacturing of a supply chain within an enterprise system. Specifically, iPlanet Application Server Enterprise Connector for CICS enables you to manipulate data within a CICS transaction from a servlet or EJB controlled by the iPlanet Application Server.

This chapter describes concepts the administrator should be familiar with when setting up iPlanet Application Server Enterprise Connector for CICS or using the API in servlets or EJBs, and contains the following:

• Overview

• Installing the Enterprise Connector for CICS

• Mining the CICS Application

Overview

---

The Enterprise connectors fit into a three tier application model setup that supports the iPlanet Application ServeriPlanet Application Server 6.0 application web server setup.

Figure 1-1    Application Model

The three tier application model is composed of the following:

• Presentation Tier

• Application Server Tier

• Data Access Tier

Presentation Tier

The presentation tier is where information is accessed by the user, usually a web browser. The user accesses iPlanet Application Server from his browser using HTML via HTTP and HTTPS (1).

Application Server Tier

The application server tier (2) houses the intelligence for the web server, applications, and communications to databases such as Oracle, DB2. Enterprise Java Beans (EJB) and servlets are supported by the iPlanet Application Server. In addition, iAB and iEB Tools provide ways to create EJB's and servlets, which are accessed by the UIF (Unified Integration Framework), as seen in the Data Access Tier.

Data Access Tier

The data access tier consists of the UIF which provides business logic needed to enable uniform access to different backend systems (3). The function of the UIF is to act as an interpreter to ease the transfer of information. The UIF interfaces with EJBs and servlets on one side, and product-specific Enterprise connectors on the other side. This tier also works closely with the Mining Tool, which is provided by the iPlanet Application Server Enterprise connectors and is used to convert metadata to XML, and populate the UIF Repository.

The UIF is composed of two parts:

• Application Programming Interface (API) framework

• UIF Repository

API Framework

The API framework is a collection of APIs that enables the client to talk to the backend systems. Information exchange occurs at this stage. iPlanet Application Server Enterprise Connector for CICS communicates with the backend system via an in-process, multi-threaded method.

UIF Repository

The UIF Repository stores data in XML format. The UIF is actually a consistent way to access backend data. It consists of a set of ten API calls that act as a means to communicate with the backsystem.

An EJB calls for various commands/information from the backend system. This call is routed through the UIF, which serves as a translator between the backend system and the EJB. A dialog is established, an exchange of information occurs, and the dialog is concluded. See Figure 1-1 Application Model.

The Mining Tool uses a common cross-platform format, XML, to populate the repository by taking backend information such as COBOL COPYBOOKS, and converting it to XML. The XML is then stored in the UIF Repository in a specific structure that can be recalled when necessary.

Figure 1-2    Mining Tool

Enterprise Connector for CICS Architecture

• Unified Integration Framework (UIF), a common Application Programming Interface (API) used to access data. For example, programmers use the UIF API to invoke different backends with one set of calls.

• A repository that contains data that drives iPlanet Application Server Enterprise Connector for CICS. The repository is associated with the UIF to hold parameters and other information about the CICS system; for example, the kind of connection, the data that can be accessed, and the access methods.

• An adapter that implements the CICS-specific data access services. The adapter provides the translation and packaging of data between the UIF and the CICS system.

The following describesthe components in a typical iPlanet Application Server Enterprise Connector for CICS system:

Servlet or EJB	The Servlet or EJB is an application that operates the iPlanet Application Server Enterprise Connector for CICS.
UIF API	The common UIF API that enables you to operate different Enterprise connectors with the same API.
Enterprise connector	The component in iPlanet Application Server that enables you to access the CICS packet.
Repository	An LDAP directory where all the CICS definitions are stored for the use of iPlanet Application Server.
CICS Management Console	The Graphic User Interface (GUI) that enables you to perform various administrative tasks.
CICS Metadata Mining Tool	This component enables you to introspect from within the Management Console to the CICS backend.
Repository Browser	This component enables you to view the Repository and its components. See the iPlanet Application Server Enterprise Connector for CICS Developer's Guide for further details.
CICS System (Message Agent)	A CICS native component that enables you to access CICS.

Technical Overview

In this section, we will discuss the following topics:

Prerequisites	This section describes existing conditions or required installed programs to run the iPlanet Application Server Enterprise Connector for CICS.
Development	This section describes method definition and servlet application.
Deployment	This section describes how to arrange the application.
Run	This section describes what occurs during the run time.

Prerequisites

To properly run the iPlanet Application Server Enterprise Connector for CICS adapter, the following requirements must be met:

• You must install iPlanet Application Server Enterprise Connector for CICS and UIF (see Installing the Enterprise Connector for CICS, Chapter 1).

Development

This is where developing the CICS servlet application is accomplished.

1. From the Management Console, from the Data Mining option, mine one or more of the COBOL programs defined in the backend.

2. Use the CICS mining tool found in the Management Console.

3. Write a servlet application using recently mined methods. Write an application or call the function object yourself using direct UIF API (see iPlanet Application Server Enterprise Connector for CICS Developer's Guide, Chapter 3 Using the UIF API Directory).

Deployment

This section describes how to arrange the application.

To properly deploy the application, you need to:

1. Register the application. (To register a servlet in iPlanet Application Server 6.0 you need to create two XML files. Name the XML thoughtfully, as the name of the XML file is used as a lookup to run the servlet. For example, if you name the XML "test.XML", then you also need to create a file named "ias-test.XML". Access the servlet from an HTML page as follows: /NASApp/<xmlfilename>/<servletname>).

2. Obtain and decompress XML files to a directory.

3. Load XML files to a directory.

4. Restart the application server.

Run Time

During the run time flow, the following occurs in the following:

1. The servlet is executed by HTML via a URL or a JSP.

2. The servlet Java code starts a CICS function object in the iPlanet Application ServeriPlanet Application Server through the UIF API.

3. The CICS adapter retains all the input definitions from the repository.

4. The CICS adapter executes a request against the CICS backend, sending the received input through the HTML. When a reply is received from the CICS backend, the CICS adapter returns the reply to the UIF, which then returns all the output values to the servlet Java code. This can then be sent back via HTML or JSP to the user.

Installing the Enterprise Connector for CICS

---

The iPlanet Application Server Enterprise Connector for CICS iPlanet Application Serveradministrator is responsible for the following:

• Installation of the iPlanet Application Server iPlanet Application Server

• Installation of the iPlanet Application Server Enterprise Connector for CICS adapter

• Mining the CICS Message Definition

The iPlanet Application Server must be installed first. For more information, please see the iPlanet Application Server, Version 6.0, Installation Guide.

Installing on Windows NT

This section describes installing and uninstalling iPlanet Application Server 6.0 Enterprise Connector for CICS on Windows NT.

iPlanet Application Server Enterprise Connector for CICS supports IBM CICS running on OS/390. MVS 5.22 and CICS 3.2 and above with current APARS.

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

Installation Prerequisites

The iPlanet Application Server 6.0 Enterprise Connector for CICS installation requires that the following be resident on your system: an appropriate web server, such as iPlanet Web Server (iWS), iPlanet Application Server iPlanet Application Server6.0, and the Unified Integration Framework (UIF) module.

Before beginning the installation:

1. Check that an appropriate web server, iWS 4.1 or later, has been installed.

   If your system does not have an installed web server, install one before beginning the iPlanet Application Server 6.0 installation. The disk size requirements for the web server are in addition to the requirements listed in Table 1-1.

2. Check that iPlanet Application Server 6.0 is installed on your system.

   iPlanet Application Server and UIF 6.0 must be installed on your system before you start the iPlanet Application Server Enterprise Connector for CICS 6.0 installation. See the iPlanet Application Server Installation Guide for instructions on installing iPlanet Application Server 6.0.

3. Check that UIF 6.0 is installed on your system.

   UIF 6.0 must be installed on your system before you start the iPlanet Application Server for CICS 6.0 installation. See the iPlanet Application Server Installation Guide for instructions on installing iPlanet Application Server 6.0.
   

   Table 1-1 Minimum System Requirements
   
   

   Operation System	Windows NT 4, Service Pack 5
   Hard Drive	100 MB free for minimum installation; 150 MB is recommended.
   iPlanet Application Server	150 MB
   RAM	64 MB; 128 MB is recommended

Installation Procedure

First, unzip the iPlanet Application Server for CICS files.

1. Double-click on the setup.exe file.

2. Read the Welcome message and then click Next.
   
   

3. Read the License Agreement; click Yes if you agree,

   Thoroughly read and understand this information before installing.
   
   

4. Choose your installation directory, then click Next.

   If you are only installing iPlanet Application Server for CICS, you must install iPlanet Application Server for CICS in the same directory as you installed iPlanet Application Server.
   
   

5. Select the iAS CICS Adapter 6.0 check box and then press the Next button.
   
   .

6. Choose the protocol you prefer in the Select TCP/IP or SNA protocol window as shown below, and then click Next.
   
   

---

Note	The following procedure starting in Step 7 is used to connect to the backend using TCP/IP.

---

7. Type in your CICS Backend system definition.
   
   

   Type in the requested information in the text boxes and then click Next to continue with Step 9 that completes the installation.

---

Note	The following procedure starting in Step 8 is used to connect to the backend using SNA.

---

8. Select the SNA radio button to display the SNA protocol dialog box.
   
   

9. 
   
   Review the configuration summary. If it is correct, press the Install button.

---

Note	If you have previously installed iPlanet Application Server 6.0 on your computer the following message will be displayed. Click No To All to complete the installation.

---

10. Setup File Copy.
    
    

---

Caution

You must restart your computer after you complete the installation.

---

11. After installation on NT, proceed with Mainframe component installation.

    In case of direct APPC connection from NT, SNA/APPC on NT must be configured as explained in the following section.

SNA/APPC Configuration

A sample configuration file for IBM Personal Communications (PCOMM) product for NT is enlisted, and supplied in: <instdir>\nas\ias610samp.acg

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

Code Example 1-1 PCOM 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

)

Uninstalling on Windows NT

This procedure is used to uninstall iPlanet Application Server Enterprise connector for CICS.

Uninstalling the Enterprise Connector for CICS

1. Choose Uninstaller from the NT start menu's programs - Netscape Application Server 6.0 entry.

2. Deselect all components for iAS except iAS for CICS, then click OK.

   While deselecting the components for iAS, the uninstaller checks for dependencies between components.

Deselecting the Enterprise Connector for CICS
Deselect items in the following order:

1. Deselect Netscape Server Family Core components.

2. Deselect Administration Services and Netscape Directory Suite.

3. Deselect iAS 6.0.

Deselecting iPlanet Application Server
Click Change and deselect options in the following order:

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 will be displayed and you may not be able to deselect the desired option.

   ---

   
   

Installing on Solaris

The following presents the installation steps for iPlanet Application Server Enterprise Connector for CICS on Solaris.

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

Installation Prerequisites

The following are required before you can install iPlanet Application Server Enterprise Connector for CICS.

• iPlanet Enterprise Server 4.1 or above installed

• iPlanet Application Server 6.0

• Unified Integration Framework

• Related software

Pre-Installation

The first step in the pre-installation is to download and unzip the file inscics.zip to a temporary directory.

Ensure that the same setup is used for installing iPlanet Application Server.

Conventions

Each step in the installation process contains:

• a display of the screen as it will appear during installation

• information that the user must input

  Explanation of user input is provided only when the screen display is not self explanatory, as shown below.

Installation Procedure

Information to be input by person installing Solaris

1. In the temporary directory type >Type#./setup

   The following message appears:

   iPlanet Server Products Installation/Uninstallation

   Welcome to the iPlanet Server Products installation program

   This program will install iPlanet Server Products and the

   iPlanet Console on your computer.

   It is recommended that you have "root" privilege to install the

   software.

   Tips for using the installation program:

   Press "Enter" to choose the default and go to the next screen

   Type "Control-B" to go back to the previous screen

   Type "Control-C" to cancel the installation program

   You can enter multiple items using commas to separate them.

   For example: 1, 2, 3.

   Would you like to continue with installation? [Yes]:

2. Type Yes to continue.

   The following message appears:

   BY INSTALLING THIS SOFTWARE YOU ARE CONSENTING TO BE BOUND BY AND ARE BECOMING A PARTY TO THE AGREEMENT FOUND IN THE LICENSE.TXT FILE. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, PLEASE DO NOT INSTALL OR USE THIS SOFTWARE.

   Do you agree to the license terms? [No]:

3. Type Yes to continue, if you agree with the terms.

   The following message appears:

   Select the items you would like to install:

   iPlanet Servers

   Installs iPlanet Servers with the integrated Netscape Console onto your computer.

   Netscape Console

   Installs Netscape Console as a stand-alone Java Application on your computer.

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

   Select the component you want to install [1]:

4. Press <Enter> to install the iPlanet Server.

   The following message appears:

   This program will extract the server files and install them into a directory you specify. That directory is called the server root in the product documentation and contains the server programs, the Administration Server, and the server configuration files.

   To accept the default shown in the brackets, press <Enter>.

   Install location [/iPlanet/iAS6]:

5. Type the iPlanet Application Server installation directory, and then press <Enter>.

   The following message appears:

   iPlanet Server Products components:

   Components with a number in () contain additional subcomponents

   which you can select using subsequent screens.

   1. iAS CICS Adapter 6.0 (1)

   Specify the components you wish to install [ALL]: 1

6. Press <Enter> to install all the components.

The following message appears:

iAS CICS Adapter 6.0 components:

Components with a number in () contain additional subcomponents

which you can select using subsequent screens.

1. iAS CICS Adapter Core Components

Specify the components you wish to install [1]: 1

7. Press <Enter> to install all the components.

   The following message appears:

   Enter the fully qualified domain name of the computer

   on which you're installing server software. Using the form

   <hostname>.<domainname>

   Example: eros.airius.com.

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

   Computer name [grass.tel-aviv.israel.sun.com]:

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

   The following message appears:

   Choose a Unix user and group to represent the iPlanet server

   in the user directory. The iPlanet server will run as this user.

   It is recommended that this user should have no privileges

   in the computer network system. The Administration Server

   will give this group some permissions in the server root

   to perform server-specific operations.

   If you have not yet created a user and group for the iPlanet

   server, create this user and group using your native UNIX

   system utilities.

   To accept the default shown in brackets, press the Return key.

   System User [nobody]:

   System Group [nobody]:

9. To accept the default shown in brackets, press the <Enter> key.

   The following message appears:

   The following information is needed in order to connect iAS to the CICS backend system. You will be prompted to give the relay host, relay port, LU name, user ID and password.

   Relay Host:

10. Type in the Relay Host.

    The following message appears:

    Please enter the port number for this relay host.

    Host Name:

11. Type in the Relay Port.

    The following message appears:

    Please enter the LU name.

    LU name:

12. Type in the LU name.

    The following message appears:

    Please enter the user ID and password.

    User ID:

    Password:

13. Type in the User ID and Password.

    The following message appears:

    Finished with gathering of information.

    Next, the iAS for CICS files will be extracted. After that,

    the configuration and registration based on your responses will begin.

    Please hit ENTER to continue:

14. Press <Enter> to continue.

After the successful installation on Solaris you may check the samples by going to the URL: http://<webserver instance name>/cicsSamples.

Uninstalling on Solaris

1. Go to your installation directory, for example:

   iplanet/ias6

2. Type ./uninstall.
   A list of uninstall options appears.

3. Select the specific product components you wish to uninstall.

Mining the CICS Application

---

The iPlanet Application Server Enterprise Connector for CICS does a specialized form of data mining: it looks at data and extracts functions and parameters from backend systems to enable you to utilize (call) these functions.

Entering the Console from Windows NT

1. Select Start>Programs>iPlanet Application Server 6.0>iAS for CICS Management console
   
   .

Entering the Console from Solaris

1. Run: cicsconsole.sh

   from <iPlanet/ias/APPS/bin

2. Select the CICS Management Console icon, and click the Open button in the upper right to display the CICS Management Console.
   
   

Figure 1-3    CICS Management Console window

Data Mining

Data mining is the search for relationships and global patterns that exist in large databases. These relationships represent valuable knowledge about the database and objects in the database. The elements of the Data-mining tool are shown in the following illustration.

Figure 1-4    Elements of the Data Mining

You submit search criteria to the Management Console which queries CCIS for any functions matching the criteria. You then selects the function or functions to be mined. Data is extracted from CICS, converted to XML, and then loaded into the repository.

The three data-mining operations/options are:

Load into Repository	The Load into Repository option is used to load selected function, or functions, into the repository. The XML file is erased.
Save XML	This option is used to store a selected function, or functions, as XML which can be loaded later into a repository.
Archive XML	This is used to store function, or functions, as XML in zip format; these can be loaded later into a repository. The zip file name is the default. The zip file is located as a default at <root>/apps/archives.

Displaying Data Mining Selections

1. Click the Data Mining icon to display the Choose Data Source list.
   
   

Figure 1-5    Choose Data Source window

2. Select the Data source and click the OK button to display the Input dialog box.
   
   

Figure 1-6    Input window

3. Type in the search criteria and click the OK button to display the Choose PeopleSoft Function dialog box.

   You can use wildcards, e.g. CUSTOMER*
   
   

Figure 1-7    The Choose CICS Function window

4. Select the function(s) you want to activate.

   When you load the selection into a repository, it does not automatically save the XML file. You must select the Save XML check box to save the function. The operation is finished when the progress indicator disappears

   
   

   ---

   Note	You can select one, two, or all the check boxes.

   ---

   
   

Loading Functions Into Repository

The Load into Repository selection is used to load a function, or functions, into the repository.

1. Select the function in the list box

2. Select the Load into Repository check box.

3. Click the Open Button to load the file.
   
   

Figure 1-8    The Load window

4. Select the Archive.
   
   

Figure 1-9    The Choose Archive window

Click the Load button to load the selected archive. Click the Cancel button to return to the previous window with no changes made. Click the Archive Details button to display the XML file (see the Developer's Guide for more details).

Saving XML Functions

This option is used to store a selected function, or functions, as XML which can be loaded later into a repository.

1. Select the Save XML check box.

2. Select the Load into Repository check box. An XML file is created and stored in a directory with name of function.

   
   

   ---

   Note	The default options are stored in a directory with the name of the function that can not be changed.

   ---