This section explains how to create the sample’s Environments for Atlanta and Berlin. Use the procedures to set up Atlanta first, then Berlin.
On Enterprise Designer, near the lower left of the window, click the Environment Explorer tab.
On the Environment Explorer tree, right-click the Repository and, on the context menu, click New Environment.
Name the newly created Environment envA (envB for Berlin).
Right-click envA (envB for Berlin) and, on the menu, click New Logical Host and name the Logical Host lhA (lhB for Berlin).
Right-click IntegrationSvr1 and select Properties from the context menu.
The Properties dialog box for IntegrationSvr1 appears. See the figure below.
For lhA ⇒ IntegrationSvr1 on Environment Explorer, set the Configuration ⇒ SeeBeyond Integration Server properties as follows:
For the rest of the IntegrationSvr1 properties settings, accept the defaults.
Create a Sun SeeBeyond JMS IQ Manager under IntegrationSvr1 and name it SBJMSIQMgr1.
Right-click SBJMSIQMgr1 and select Properties from the context menu.
The Properties dialog box for SBJMSIQMgr1 appears.
For lhA ⇒ SBJMSIQMgr1 on Environment Explorer, set the Configuration ⇒ SeeBeyond JMS IQ Manager Configuration property as follows:
Password: STC
On Enterprise Designer, on the Environment Explorer tree, right-click envA (envB for Berlin) and, on the context menu, click New Oracle External System.
Name the new component esOracleand click OK.
These actions create, for the current Environment, an external system instance for the Oracle eWay in outbound mode.
The eXchange database uses Oracle. For more information on Oracle requirements for eXchange and ASC X12 PM, see the Readme file that accompanies ASC X12 PM.
Right-click esOracleand select Properties from the context menu.
The Properties dialog box for the external system appears. See the figure below.
Configure the Configuration ⇒ Outbound Oracle eWay ⇒ JDBC Connector settings properties for esOracle as follows:
Description: Oracle Connection Pool Datasource
ServerName: Host name of the Oracle server machine
PortNumber: 1521 (change this value only if your Oracle system administrator changed the default)
DatabaseName: SID for your current Oracle system
User: Valid user ID for the current Oracle system
Password: Valid password for the current Oracle system (masked)
Driver Properties: Blank, for this sample
Delimiter: #
TNS Entry: Blank, for this sample
MinPoolSize: 0
MaxPoolSize: 10
MaxIdleTime: 0
Configure the Configuration ⇒ Outbound Oracle non-Transactional eWay ⇒ JDBC Connector settings properties for esOracle as follows:
Description: Oracle non-Transactional Connection Pool Datasource
ServerName: Host name of the Oracle server machine
PortNumber: 1521 (change this value only if your Oracle system administrator changed the default)
DatabaseName: SID for your current Oracle system
User: Valid user ID for the current Oracle system
Password: Valid password for the current Oracle system (masked)
Driver Properties: Blank, for this sample
Delimiter: #
TNS Entry: Blank, for this sample
MinPoolSize: 0
MaxPoolSize: 10
MaxIdleTime: 0
When all properties have been configured correctly for your site, click OK.
Create a new LDAP external system(New ⇒ LDAP External System) under envA (envB for Berlin) and name it esLDAP.
Set the Environment Configuration ⇒ Connection properties for esLDAP as follows:
Initial Context Factory: com.sun.jndi.ldap.LdapCtxFactory
Provider URL: As necessary for your system, according to the provided syntax For example, ldap://mycompany.co.in:1389/dc=co,dc=in
Authentication: simple
Principal: As necessary for your system. For example, Manager
Credentials: Password, as necessary for your system. For example, exchange
A separate LDAP external system instance is required for each B2B Host.
For all other esLDAP properties, accept the defaults.
Create a B2B Service Configurator (New ⇒ B2B Configurator Service) external system under envA and name it esB2BService.
Set the environment-configuration ⇒ Database Settings properties for esB2BService as follows:
Type: Oracle
URL: Points to the eXchange database; an example of the URL syntax is: jdbc:oracle:thin:@hostname:port:exchange
UserName: Valid user ID for the current Oracle system. For example, ex_admin
Password: Valid password for the current Oracle system (masked). For example, ex_admin
Set the environment-configuration ⇒ JMS Settings properties for esB2BService as follows:
JMS Server URL: Points to the IQ Manager port. The envA Logical Host is on 18000 (envB on 28000), the IQ Manager port for envA is 18007 (28007 for envB). This port number is listed in the Domain Manager for the current Logical Host; an example of the URL syntax is: stcms://hostname:port
Security Principal: Administrator
Security Credentials: STC (masked)
Connection Factory: connectionfactories/topicconnectionfactory
Resend Topic: topics/EX_TODELIVERY
Timeout Topic: topics/EX_ERROR
Business Protocol Topic for Batching: topics/EX_BATCHER
Delivery Protocol Topic for Batching: topics/EX_DELIVERYBATCHER
For the rest of the esB2BService properties settings, accept the defaults.
Create a new File eWay (New ⇒ File External System) in inbound mode under envA and name it esFileA.
Set the Configuration ⇒ Inbound File eWay ⇒ Parameter Settings property for esFileA as follows:
Directory:
C:/temp/eXchange/Sample/X12/Data/Atlanta |
Make sure this folder and the folder for envB are correctly configured under the appropriate parameter in ePM. It is recommended that you create an additional folder under X12 named Errors.
Set the Configuration ⇒ Outbound File eWay ⇒ Parameter Settings property (for DLQ and processing errors) for esFileA as follows:
Directory:
C:/temp/eXchange/Sample/X12/Errors/Atlanta |
For all other File eWay (esFileA and esFileB) properties, accept the defaults.
Create a new File eWay (New ⇒ File External System) in inbound mode under envB and name it esFileB.
Set the Configuration ⇒ Inbound File eWay ⇒ Parameter Settings property for esFileB as follows:
Directory:
C:/temp/eXchange/Sample/X12/Data/Berlin |
Set the Configuration ⇒ Outbound File eWay ⇒ Parameter Settings property (for DLQ and processing errors) for esFileB as follows:
Directory:
C:/temp/eXchange/Sample/X12/Errors/Berlin |
In Enterprise Designer, on the Environment Explorer tree, right-click envA (envB for Berlin) and, on the context menu, click New Batch Local File System.
Name the new external system esBLF, and click OK.
These operations create, for the Environment, an external system for the Batch eWay in local file mode.
In the new external systems’ Properties dialog boxes and accept the defaults.
When you are finished with each Properties dialog box, click OK.
Create an HTTP eWay (client mode) external system under envA (envB for Berlin) and name it esHTTP.
Open the Properties dialog boxes for esHTTP and accept the defaults.
Create an HTTP eWay (server mode) external system under envA (envB for Berlin) and name it esHTTPserver.
Open the Properties dialog boxes for esHTTPserver and accept the defaults.
When you build a B2B Host Deployment Profile, eXchange automatically creates another external system on the chosen Environment. This external system is called an eXchange service. For more information on this service, see the eXchange Integrator User’s Guide. Also, see Constructing the B2B Host Project.
Result: You have set up the Environment for Atlanta, envA. See Figure 6–2.
Collapse the envA Environment Explorer tree, click Save All, and close all canvases.
Result: You have set up the Environment for Berlin, envB, which appears directly under envA on the Environment Explorer tree. See Figure 6–2.
Collapse the envB Environment Explorer tree, click Save All, and close all canvases.
Final Result: You have now finished setting up the Environments for Atlanta and Berlin, including the external system components to be used by both.