Setting Up Companies’ Environments

This section explains how to set up the Atlanta and Berlin Companies’ sample Environments, envAtlanta and envBerlin.

The sample assumes you use default configurations for all servers, where possible, and that you make any changes in Enterprise Designer, where needed, for example:

• Oracle: You must create a new outbound Oracle external system instance for each Environment and configure it, even if you imported the sample Environments. Sample parameters are for reference only. Any Oracle database used by eXchange must be accessible to eGate, and you must know its Oracle SID, user name, and password.

• Ports: To run anything other than Integration Server on ports 18000 through 18009, you must make adjustments to configuration values for port numbers, depending on the type of application server you are using.

• HTTPS: For information on how to configure your HTTP server or client to use SSL, see the HTTP(S) eWay Intelligent Adapter User’s Guide, for eWay settings and Integration Server configuration.

  ---

  Note –

  After you have created all of the external system instances you need for the current B2B host Project, another external system instance, an eXchange service, is created in this Project automatically when you activate the Project. See Setting Up Companies’ B2B Host Projects for details.

  ---

Creating Atlanta Company’s Environment

This section explains how to create the sample’s Environment for the Atlanta Company.

To create the basic components

1. In Enterprise Designer, near the lower left of the window, click the Environment Explorer tab.

2. On the Environment Explorer tree, right-click the Repository and, on the context menu, click New Environment.

3. Name the newly created Environment envAtlanta.

4. Right-click envAtlanta and, on the menu, click New Logical Host and name the Logical Host lhAtlanta.

   ---

   Note –

   If you want to create any additional Logical Host, right-click it and open its Properties dialog box. Click Logical Host Configuration and change the value Logical Host Base Port to a larger multiple of 1000 (28000 if ports 28000-28009 are unused; otherwise 28100 or 29000). When you are finished, close the Properties dialog box.

   ---

5. Create an Integration Sever under lhAtlanta and name it isAtlanta.

6. Create a Seebeyond JMS IQ Manager under lhAtlanta and name it jmsAtlanta.

To create and configure the nondatabase external system instances

1. In Enterprise Designer, on the Environment Explorer tree, right-click envAtlanta and, on the context menu, click New BatchFTP External System.

2. Name the new external system instance extBatchFtpAtlanta, and click OK.

   These operations create, for the Environment, an external system instance for the Batch eWay in FTP mode.

3. On the new external system’s Properties dialog box, allow the default ports for SOCKS, FTP, and SSH Tunneling.

4. Create a Batch eWay (local file mode) external system under envAtlanta and name it extBatchLocalFileAtlanta.

5. Create a File eWay (inbound mode) external system under envAtlanta and name it extFileInAtlanta.

6. Create a File eWay (outbound mode) external system under envAtlanta and name it extFileOutAtlanta.

7. Create an HTTP eWay (client mode) external system under envAtlanta and name it extHttpAtlanta.

8. On the new HTTP eWay’s Properties dialog box, enter the in the following values:

   • URL Syntax: http://www.seebeyond.com

   • Content Type: Leave blank.

9. Create an HTTP Server eWay external system under envAtlanta and name it extHttpServerAtlanta.

10. Create a new keystore under envAtlanta and name it envAtlanta_ks_store. See Configuring Companies’ Cryptographic Features for details on how to add keys and certificates to the keystore.

To create and configure the Oracle external system instance

1. In Enterprise Designer, on the Environment Explorer tree, right-click envAtlanta and, on the context menu, click New Oracle External System.

   ---

   Note –

   The eXchange database instance runs on Oracle. For more information Oracle requirements for eXchange and ebXML Protocol Manager, see System Requirements.

   ---

2. Name the new component extOracleOutAtlanta, designate it Outbound Oracle eWay, and click OK.

   These operations create, for the Environment, an external system instance for the Oracle eWay in outbound mode.

3. Right-click extOracleOutAtlanta and configure properties appropriately, as follows:

   • DatabaseName: SID for your current Oracle system.

   • DataSourceName: local.

   • Delimiter: Symbol #.

   • Description: Oracle thin driver Connection Pool Datasource.

   • Driver Properties: Blank, for this sample.

   • Password: Valid password for the current Oracle system.

   • PortNumber: 1521 (change this value only if your Oracle system administrator changed the default).

   • ServerName: myMachine: Host name of the Oracle server machine.

   • TNS Entry: Blank, for this sample.

   • User: Valid user ID for the current Oracle system.

4. When all properties have been configured correctly for your site, click OK.

When You Are Finished

• Your result appears as shown in When You Are Finished.

• Collapse the envAtlanta Environment Explorer tree, click Save All, and close all canvases.

Creating Berlin Company’s Environment

This section explains how to create the sample’s Environment for the Berlin Company.

To create the basic components

1. Follow the steps provided under the Creating Atlanta Company’s Environment.

2. Name the appropriate components as follows:

   • envBerlin

   • lhBerlin

   • isBerlin

   • jmsBerlin

To create and configure the nondatabase external system instances

1. Follow the steps provided under the Creating Atlanta Company’s Environment, under envBerlin.

2. Name the appropriate external system instances as follows:

   • extBatchFtpBerlin (use default properties)

   • extBatchLocalFileBerlin

   • extFileInBerlin

   • extFileOutBerlin

   • extHttpBerlin (use the same properties values as extHttpAtlanta)

   • extHttpServerBerlin.

   • envBerlin_ks_store.

To create and configure the Oracle external system instance

1. Follow the steps provided under the Creating Atlanta Company’s Environment, using envBerlin.

2. Name the new component extOracleOutBerlin, designate it Outbound Oracle eWay.

3. Configure extOracleOutBerlin as shown in the list provided in step Creating Atlanta Company’s Environment under the Creating Atlanta Company’s EnvironmentCreating Atlanta Company’s Environment.

When You Are Finished

• Your result appears as shown in When You Are Finished.

• Collapse the envBerlin Environment Explorer tree, click Save All, and close all canvases.