Working with the Structure and General Settings of a Template File

This section discusses:

  • Naming the template file.

  • Setting the structure of the template file.

Naming the Template File

Using the text editor for your operating system, create a new file and save it using the following convention:

<file_name>.<file_extension>

The file extension can be .txt, .properties, or any extension that is readable in ASCII format.

Note:

You need to specify the template name using the PTEM_PROP environment variable prior to running the PTEM_CONFIG Application Engine program.

Setting the Structure of the Template File

The content of the properties should be structured in the following order:

  1. General settings.

  2. Template settings.

  3. Individual configuration plug-in settings.

To enable a plug-in, you include a reference to that plug-in, such as:

plugin.IB.1=PTEM_CONFIG:PTIBRenameNode

where

  • IB - refers to the category of the plug-in.

  • 1- represents the sequence number in which plug-ins are configured.

  • PTEM_CONFIG:PTIBRenameNode - represents the plug-in name, which consists of application package name (PTEM_CONFIG) and class name (PTIBRenameNode).

Then, you include the properties for that plug-in immediately following the plug-in reference. The following example illustrates a sample template file:

configure=true
verify=true
decrypt_password=true

template.domain=@webhist.SESSIONCOOKIEDOM
template.host=@webhist.WEBSERVERNAME
template.httpport=@webhist.PORTALHTTPPORT
template.jslport=@webhist.jolt_port
template.localnode=%LocalNode
template.piasite=@webhist.ps.discovery.siteName
template.sslport=@webhist.PORTALHTTPSPORT
template.tools_release=%ToolsRelease
template.userid=%UserId

#Group:Integration Broker
#Description:Integration Broker Configurations

##### Rename the default local node#####

plugin.IB.1=PTEM_CONFIG:PTIBRenameNode

#Default local node
env.default_local_node=@localnode@

#Purge application server messages
env.app_msg_purge_all_dms=true

Note:

All other configuration plug-ins you want to enable can be included in the file as needed.