At this point, apply all Deployment Profiles to the appropriate Environment’s Logical Host. Return to previous procedures in this chapter to troubleshoot any possible problems appropriately until all Deployment Profiles apply with no errors.
The directory for the Logical Host that runs the Atlanta Company is called lhAtlanta (associated with envAtlanta), and the directory for the Logical Host that runs the Berlin Company is called lhBerlin (associated with envBerlin).
Access a command prompt and change directories to the run executable file’s location (for example, beginning with lhAtlanta) of the Logical Host:
Start the run script using the appropriate parameters, for example:
bootstrap- r http://<myMachine:12345>/<myRepository>- i <myID> -p <myPassword>- e envAtlanta- l lhAtlanta -f
For the -r (Repository) parameter), supply the correct URL with the Repository name.
For the -i and -p (user ID and password) parameters, supply the appropriate values.
For -e (Environment name) parameter, use envAtlanta
For -l (Logical Host name) parameters, use lhAtlanta
You need not supply the -f (force) flag if all configuration changes have already been applied, or if this is the first time that the run script has been executed.
After a brief time, the Logical Host starts running, and all activated Projects that reference envAtlanta are automatically applied to it.
cd lhBerlin\bootstrap\bin bootstrap- r http://<myMachine:12345>/<myRepository>- i <myID> -p <myPassword>- e envBerlin- l lhBerlin -f
This procedure is optional. You only need to use it if changes are made to parameters in an Environment while a Logical Host is running, for example, adding or modifying keystores for an eXchange service.
Use these steps to apply the changes without having to shut down and rerun the Logical Host. This procedure is the equivalent of shutting down the Logical Host and running it again using the -f flag.
In Enterprise Designer’s Environment Explorer, open the Environment where the changes have occurred.
Right-click the Logical Host that is running and, on the context menu, click Apply.
Repeat the previous step, as needed, for other Logical Hosts in the same Environment.
In the Logical Host, a brief shutdown and restart occur, and the changes are applied to the running Logical Host.
The originating B2B host sends an outbound status request and receives an inbound status response. The originating ePM sends an outbound “ping” and receives an inbound “pong.”
Both companies can trade data back and forth with one another, so you can reverse the inbound and outbound settings, depending on which company you want to be the sender and which the receiver. The sample’s scenario (as supplied) is set up according to the procedure in this section.
See Sample Data for a list of the sample scenario’s data files and the directory locations created when the sample scenario’s files are first extracted.
You may have given different names to the \temp\eXchange\ directories shown in the path locations listed under Sample Data. If so, substitute those names for the \temp\eXchange\ directories given in this procedure.
Before you start, change the .txt file extensions for your outbound data to .~in.
Copy the outbound data files to the following directory:
Make sure the file names of your outbound data (any of the files you want to send) have .txt file extensions. Any file with a .txt file extension changes to .~in as the file is picked up for delivery by eXchange.
This operation also copies the information in the payload data files and sends it along with the outbound files, so you see no change to the payload data file names. The Berlin Company returns the inbound data files to the following directory: