A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5

Chapter 5. Connection management 135

Figure 5-12 The Connect macro tree

If this connection pool will be used by only one host Integration Object, you will

normally finish the Integration Object by recording the Data macro and then

saving the Integration Object, which will also cause the creation of the data sets

for the connection pool. If this connection pool will be used by different

Integration Objects, you might alternatively save only the connection pool

definitions (including user list, Connect and Disconnect macros) by clicking File

-> Save -> Connection Pools. When creating Integration Objects using this

connection pool, you then have to record only the Data macro.

5.3 Configuration files

Seven different files are generated for a connection pool from the definitions in

Host Access and placed into the HostPub\Studio\SessionDefs subdirectory

(unless you have changed the file structure during installation). It is possible to

directly edit those files with an editor supporting UTF-8 encoding (for example,

MS WordPad) in order to add functions supported by the macros but not

implemented in the full-screen interface of the Studio.

136 IBM WebSphere Host Publisher Version 3.5

Figure 5-13 File as400_itso.poolspec

The poolspec file in Figure 5-13 sets some general values for connections in the

pool and includes the names of the files that contain the connection parameters

(connspec), the logon description (logonspec), and the user list (userpool). In

this example, the names are all set to as400_itso, except for the userpool which

is as400_users.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE poolconfig SYSTEM "poolconfig.dtd">

<poolconfig>

------------------------------------

<hodpoolspec name="as400_itso">

<maxidletime value="60"/>

<maxbusytime value="60"/>

<connecttimeout value="120"/>

<maxconnections value="5"/>

<minconnections value="2"/>

<overflowallowed value="false"/>

<poolingenabled value="true"/>

<localuserpool refname="as400_users"/>

<hodconnspec refname="as400_itso"/>

<hodlogonspec refname="as400_itsologspec"/>

</hodpoolspec>

</poolconfig>

Chapter 5. Connection management 137

Figure 5-14 File as400_users.userpool

The userpool file (Figure 5-14) contains the list of user IDs (only the first and last

user ID is shown for this example). The file contains the passwords for the user

IDs in normal text. Be careful to restrict access to this file if security is a concern

for applications allowed for these user IDs. When transferring the files to the Host

Publisher Server, the passwords can optionally be encrypted for transmission

through the network and storage on the server.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE userconfig SYSTEM "userconfig.dtd">

<userconfig>

-----------------------------------------------------

<schema>

<defineproperty encrypt="0" name="$key_description"/>

<defineproperty encrypt="0" name="_password"/>

<defineproperty encrypt="0" name="_userid"/>

</schema>

<localuserpool name="as400_users">

<entry key="HPUB1">

<property name="$key_description" value="User 1"/>

<property name="_userid" value="HPUB1"/>

<property name="_password" value="abcd44"/>

</entry>

<entry key="HPUB2">

<property name="$key_description" value="User 2"/>

<property name="_userid" value="HPUB2"/>

<property name="_password" value="abcd44"/>

</entry>

<entry key="HPUB3">

<property name="$key_description" value="User 3"/>

<property name="_userid" value="HPUB3"/>

<property name="_password" value="abcd44"/>

</entry>

<entry key="HPUB4">

<property name="$key_description" value="User 4"/>

<property name="_userid" value="HPUB4"/>

<property name="_password" value="abcd44"/>

</entry>

</localuserpool>

</userconfig>

138 IBM WebSphere Host Publisher Version 3.5

Figure 5-15 File as400_itso.connspec

The connspec file in Figure 5-15 contains the parameters used to establish the

connections.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE connconfig SYSTEM "connconfig.dtd">

<connconfig>

--------------------------------------------

<hodconnspec name="as400_itso">

<singlelogon value="true"/>

<sessionprops>

SSL=false

fontSize=10

autoReconnect=false

OIAVisible=true

port=23

autoConnect=false

TNEnhanced=false

fontSizeBounded=true

autoFontSize=false

codePage=037

host=9.24.105.26

screenSize=2

sessionType=2

SSLServerAuthentication=false

SESSION_QUIETMODE=true

LUName=

codePageKey=KEY_US

</sessionprops>

<connecttimeout value="120"/>

<disconnecttimeout value="120"/>

</hodconnspec>

</connconfig>

Chapter 5. Connection management 139

Figure 5-16 File as400_itso.logonspec

The logonspec file in Figure 5-16 includes the names of the files that contain the

Connect (logon) and Disconnect (logoff) macros and the name of the file that

describes the screen from which the Data macro can start.

Figure 5-17 File as400_itsologon.macro (Part 1)

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE logonconfig SYSTEM "logonconfig.dtd">

<logonconfig>

-----------------------------------------------------

<hodlogonspec name="as400_itsologspec">

<logonmacro filename="as400_itsologon.macro"/>

<logoffmacro filename="as400_itsologoff.macro"/>

<checkinscreendesc filename="as400_itsocheckin.screen"/>

</hodlogonspec>

</logonconfig>

HAScript name="" description="" timeout="60000" pausetime="200"

promptall="false" author="" creationdate="" supressclearevents="false" >

<screen name="Screen1.1" entryscreen="true" exitscreen="false"

transient="false">

<description uselogic="1 and 2" >

<oia status="NOTINHIBITED" optional="false" invertmatch="false" />

<block row="1" col="1" erow="-1" ecol="-1" casesense="true" optional="false"

invertmatch="false" >

<string value=" " />

<string value=" IIIIIIII TTTTTTTT SSSSSSSS OOOOOOOO " />

<string value=" II TT SS OO OO " />

<string value=" II TT SSSSSSSS OO OO " />

<string value=" II TT SS OO OO " />

<string value=" IIIIIIII TT SSSSSSSS OOOOOOOO " />

<string value=" " />

<string value=" iSeries and AS/400 Center Raleigh/RTP " />

<string value=" " />

</block>