ZDS

Kintana Techniques

The 'Environment' section is where the Kintana package keeps information on your source and destination servers. For every server you have from which you want to get or send files to you must define a Kintana 'Environment' record. Server changes are a daily occurrance in most installations, and the environment list must track these changes!

Whenever servers to be serviced by Kintana are added to an environment OR when server names change the environment table MUST be updated.

An environment record must exist for a server in order for it to be added to a workflow.

Changes must be made if server names are changed, or the workflow will fail since Kintana will not be able to telnet-ftp to the non-existent server.

If servers are eliminated then delete the record from the environment list rather than just disabling it. Keep the list as clean as possible with only active servers in the list.

Before deleting an environment run this script: List all environment (Source and Target Server) names in use by workflows and check that there are no workflows that reference it!

Physical Server names are entered in the 'Client' field.

Environment names and descriptions can be whatever you choose. However using a consistent naming convention is strongly recommended.

The recommended formats are:

Environment name : 'ENVIRONMENT SERVERNAME'

Description : 'ENVIRONMENT FUNCTION DETAILS'.

where 'ENVIRONMENT' is, for example, 'DEV', 'QA', 'PROD', 'DRS'

and 'FUNCTION' is, for example, 'Application', 'Database'

The reason for pre-fixing the Name and Description fields with the ENVIRONMENT is that it makes it very much simpler to review the list and keep it in sync with the real physical world!

To create a new environment (Source or Destination Server) record, copy an existing one in the same environment (DEV, QA, PROD, DRS) and complete these tabs:

Host : Always complete the Client entry. Enter the Database entry for database servers.

Applications : Enter the applications that reside on this server and the path to the directory they are in

Oracle Apps : Not used.

User Data : Kintana's place to enter generic parameters. They are not all used.

Kintana provides a basic sanity check that verifies that Kintana has (some level of) access to the specified target via telnet or ftp. It does not NOT check that there is a staging directory or other user defined information.

Even though this is a limited check, it is very important to run it!

It at least establishes that basic connectivity exists!

Open the Environment (Server) record and click on the [Check} button at the bottom. Kintana will try to establish Telnet and FTP connections to the server. If it cannot connect, check that the server name is spelt right e.g. H, alphabetic O, numeric 1

These scripts generate hard copy that is useful in keeping the environment (Source and Target Servers) list synchronized with the servers in use by the workflows, and in keeping the list trimmed down to the servers actually in current use.

List the environment table

List all environment (Source and Target Server) names in use by workflows

List all environment (Source and Target Server) names NOT in use by workflows