Chapter 3   Managing Data Sources and User Privileges


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

The tasks are to write functions to access data that defines methods.

This chapter contains the following information:

• Overview of the Management Console

• Mapping User Privileges

• Managing the Listener

Overview of the Management Console

---

The management console has two groups of functions:

• Tasks that are used to process and browse data and functions: data mining, browse archived XMLs, and add new data sources.

• User management that establishes relationships between the web and backend users.

The user mapping management tasks performed with the management console are explained in this chapter. See Chapter 2 in the iPlanet Application Server Enterprise Connector for PeopleSoft Developer's Guide for a description of the other tasks of the management console.

Mapping User Privileges

---

From the CICS Management Console window, click the CICS User Management tab. The User Mapping Management tree file appears on the left, and the Data Source Name backend information appears on the right.

Figure 3-1    User Mapping Management

The Data Source Name window displays the following selected data:

Web User Information	The web user information such as the user's ID, the transaction name, and the entity name, is listed here.
Entity Information	The entity information such as the backend user name, and entity name is listed here.

Web User Information

The Web User Information is used to map a web user identity to a backend user identity. The administrator assigns an entity name for the web users. This web ID is used by the server to enable users to move freely across multiple systems. You can add, change users, and delete users and entities from this window. The administrator assigns entity information before the web user information, as one is based upon the parameters defined in the entity information. Because certain web user's parameters are based upon entity information parameters, the administrator must first establish entity information. The Web User Information area lists the following:

Web ID	This is an ID assigned to users on the system.
Transaction Name	This is the name of the function that will be performed. This name is named after the backend system, and order in which it appears.
Entity Name	This is the name of the assigned backend user. The naming process is dependent upon the database type used.

Editing a Web User

You can add a new web user, change a web user, and delete a web user by pressing the corresponding button.

Adding a Web User

1. To add a new web user, click on the New User button. The Web User Information window appears:
   
   

Figure 3-2    The Web User Information window

2. Type in the web ID

3. Select an entity name from the available names

4. Click OK when finished to return to the main window.

Changing a Web User

1. To change a user, click on the Change User button

2. Edit the desired field

3. Click OK when finished to return to this window.

Deleting a Web User

1. To delete a web user

2. Select the desired web user

3. Click the Delete button when finished to return to the main window.

Entity Information

The Entity Information area is used to list the following data about the backend entities assigned to the web users:

Backend User Name	The name of the backend user. This name also indicates which system the user is currently using.
Backend Password	The password of the backend user. This is assigned by the user.
Entity Name	The name of the backend entity. This is assigned by the system administrator. Certain responsibilities and restrictions can be associated with this parameter.

Editing an Entity

You can add a new entity, change an entity, and delete an entity by clicking on the corresponding button.

Adding an Entity

1. To add a new backend entity, click on the New Entity button. The Entity Information window appears:
   
   

Figure 3-3    The Entity Information window

2. Type in the appropriate data

3. Click the OK button

   The new entity information will appear in the Entity Information area of the window.

Changing an Entity

1. To change a entity informationclick on the Change entity button

2. Edit the desired field(s).

3. Click the OK button

   The edited entity will appear in the Entity Information area of the window.

Deleting an Entity

1. To delete a backend entity select the desired entity

2. Click the Delete button

   
   

   ---

   Note	When you delete backend users, also delete web users. Web users pointing to deleted backend users will not function.

   ---

   
   

Saving Edited Entities
Click on the Save buttonwhen you have completed all actions in the Entity Information window. All your additions and changes will be saved to the system.

Managing the Listener

---

From the CICS Management Console, you can manage listener jobs. A listener job is similar to the Relay. A listener listens to incoming TCP/IP conversations and relays them to a CICS region. The Listener Statistics option enables you to start, view, and manage listeners on the MVS. You can define new Listeners and submit them, cancel, and restart Listener jobs. This option also displays listener statistics information, such as name, ID, job status, and spool file.

Upon selecting the Listener Statistics option and logging on to the mainframe, the following window appears:

When naming Listener Jobs, use the ID name used to log on to the mainframe, and one character after it in any order (a number or letter). For example, Tim1 or Samplea.

To purge or restart a job, select the row in the Listener Statistics field. Click the right mouse button, or press the delete key on the keyboard.

To update the screen, click the Refresh button at the bottom of the CICS Management Console window.

Listener Statistics

This option enables you to select from a list of mainframe listener jobs, create a new job file, submit a job, save changes, or update job data. You can define new instances of listeners. For example, you might have an iPlanet Application Server server that needs to relay conversations to different mainframes on separate SNA networks, such as a mainframe used for testing and another used for production. In this case, you could define different job files and select the appropriate job depending on whether the server is in "test" or "production" mode.

The job files will be displayed on the local file system. When submitted, they will be transmitted to the mainframe via FTP, and submitted there.

Upon selecting this option and logging on to the mainframe computer, the following screen appears:

When naming Listener Jobs, use the ID name used to log on to the mainframe, and one character after it in any order (a number or letter). For example, Tal1 or Tal4.

To purge or restart a job, select the row in the Listener Statistics field. Click the right mouse button, or press the delete key on the keyboard.

To update the screen, click Refresh.

Available Files

This option allows you to select from a list of mainframe listener jobs, create a new job file, submit a job, save changes, or update job data. You can define new instances of listeners. For example, you might have a NAS server that needs to relay conversations to different mainframes on separate SNA networks, such as a mainframe used for testing and another used for production. In this case, you could define different job files and select the appropriate job depending of whether the server is in test or production mode.

The job files will be displayed on the local file system. When submitted, they will be transmitted to the mainframe via FTP, and submitted there.

Upon selecting this option and logging on to the mainframe computer, the following screen appears:

Select a job by clicking on it. Press one of the corresponding buttons on the bottom of the screen to submit a job, save changes, or update data.

Creating a New Job File

From the Listener Management icon, select and double click the Template.jcl file. A window will appear with your ID. Input the file name, and press the OK button to create the file.

---

Note	Important nomenclature rule: The new files are generated on the JCLTemplate file. You may edit this file to modify the template. The job name must be constructed from the user ID used to log on to the mainframe and one character. This structure enables the Management Console to access the file.

---