78 Geac System21 commerce.connect: Implementation on the iSeries Server
Figure 4-2 shows an example of an imported configuration.
Figure 4-2 Importing the WebSphere configuration to an iSeries called homer
The import includes:
The node
The data source and JDBC driver
The applications required for vendor.connect
The config.xml file contains the following variables, which are substituted on the import
command and replaced with real names:
$NodeName$: This is the WebSphere node name, which is case sensitive. This is
relevant when you start the console with AdminClient and when you specify an Inter-ORB
Protocol (IIOP) address for a Java Naming and Directory Interface (JNDI) lookup (for
example, within the batch files which start client programs). It is also relevant to tools such
as the XML export/import utility.
Usually the name is entirely in lowercase, However, on some systems, it is entirely in
uppercase, and in theory, could be a mixture of both. If you find that the console fails to
start with such messages as “Could not get attributes” (similar to when the
service/subsystem is not started) but the service is started, then problem may be the case
of the name.
You can verify the required name by using the following SQL to look at a WebSphere table:
select NAME
from EJSADMIN/NODE_TABLE
This shows the node name exactly as WebSphere wants it to appear. Do not be tempted
to change the contents of this table. It is liable to make things worse rather than better.
Notes:
Leave a space before each - sign. Leave a space after each keyword, for example,
-adminNodeName , -import , and -substitute .
There is only one pair of quotes around the entire substitution string.
QSH Command Entry
$
> cd /QIBM/ProdData/WebASAdv/bin
$
===> XMLConfig -adminNodeName homer -import /VendorConnect/vc.xml -substitute "
nodname=homer;host=homer.jba.co.uk;port=85;IP=123.456.001.157"
_
F3=Exit F6=Print F9=Retrieve F12=Disconnect
F13=Clear F17=Top F18=Bottom F21=CL command entry
