The sample projects shipped with ebXML Protocol Manager use hard-coded hostnames (“domain1” for the Atlanta host and “domain2” for the Berlin host), but the documentation presumes a single local host (“localhost”) throughout.
To use the ebXML sample, do one (and only one) of the following:
To use two different machines to simulate the Atlanta and Berlin hosts, globally change the string “domain1” to the actual hostname of the machine you are using to simulate the Atlanta host, and globally change the string “domain2” to the actual hostname of the machine you are using to simulate the Berlin host.
To use a single machine to simulate both the Atlanta and Berlin hosts, add aliases for “domain1” and “domain2” to the machine's etc/hosts file (on Windows, this file is %SYSTEMROOT%\system32\drivers\etc\hosts), as highlighted in the following fictitious example:
127.0.0.1 localhost # (optional comment)255.255.255.255 mymachine.myenterprise.com 111.333.555.777 machine1 # (optional comment) 222.444.666.888 machine2.theirenterprise2.com[...]255.255.255.255 domain1 # aliasing domain1 to mymachine <-- 255.255.255.255 domain2 # aliasing domain2 to mymachine <-- [...]