Setting up the Connect:Direct file transfer sample
You must perform the following steps before importing and
deploying the sample:
The IBM Sterling Connect:Direct sample was developed to run on a local system.
Therefore you must have a working local IBM Sterling Connect:Direct server
installed on your system. Make sure that this server is running and working.
The sample uses the predefined configurable service to access your local IBM
Sterling Connect:Direct server. Your local IBM Sterling Connect:Direct server
must use the default ports in order to work with that default configurable
service. Alternatively you can create and use your own configurable service
for the Connect:Direct nodes.
Ensure that your default integration node has been created.
In order to enable your default integration node to connect to the
local IBM Sterling Connect:Direct server, you must set a security
identity with a user name and password to connect to this server. To do this,
perform the following steps:
Start the IBM Integration Console.
Enter the following command: mqsisetdbparms IB9NODE -n cd::default -u username -p password
replacing username and password
with the credentials for your local IBM Sterling Connect:Direct
server. You might also replace IB9NODE
with your default integration node name.
Restart your integration node so that the changes take effect.
Stop your integration node by entering the following command: mqsistop IB9NODE where IB9NODE can be replaced with the name of
your default integration node.
Start your broker again by entering the following command: mqsistart IB9NODE where IB9NODE
can be replaced with the name of your default integration node.
Close the command console by entering exit.
Additional steps when running the sample on Linux.
The IBM Sterling Connect:Direct sample requires that a default download directory has been specified
within your IBM Sterling Connect:Direct installation
Modify the file userfile.cfg to set the pstmt.download_dir property to a suitable default location on your system.