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 broker has been created.
- In order to enable your default broker 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 WebSphere Message Broker command console.
- Enter the following command:
mqsisetdbparms MB8BROKER -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 MB8BROKER
with your default broker name.
- Restart your broker so that the changes take effect.
- Stop your broker by entering the following command:
mqsistop MB8BROKER
where MB8BROKER can be replaced with the name of
your default broker.
- Start your broker again by entering the following command:
mqsistart MB8BROKER
where MB8BROKER
can be replaced with the name of your default broker.
- 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.
Back to sample home