test

Sun B2B Suite AS2 Protocol Manager User's Guide

Constructing the Environments

In implementing AS2 PM Projects in the sample scenario, you must set up at least one Environment for each eXchange installation. The sample scenario is set up to operate on one machine but mimic two TPs. As a result, for this sample, you need to construct the Environments as explained under the following sections:

Using Environment Explorer

You perform these operations using Enterprise Designer’s Environment Explorer and its canvas windows. The sample Environments contain the following types of components:

For example, the Oracle external system must be configured to reference your Oracle setup. Other external systems (for example, the File and Batch eWays) have configurations that may differ depending on your system setup, and so forth. Also, you might be using nonstandard ports or user name/password combinations that vary from system to system.

The remainder of this section describes the common procedures to construct the sample scenario’s Environments.

Note –

Before you begin, make sure you have followed the preliminary instructions provided under Beginning Operations.

Setting up the Environments

This section explains how to create the sample’s Environments for Atlanta and Berlin. Use the procedures to set up Atlanta first, then Berlin.

ProcedureTo Create the Basic Components

  1. On 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 envA (envB for Berlin).

  4. Right-click envA (envB for Berlin) and, on the menu, click New Logical Host and name the Logical Host lhA (lhB for Berlin).

  5. Right-click IntegrationSvr1 and select Properties from the context menu.

    The Properties dialog box for IntegrationSvr1 appears (see Figure 6–4). For more information on how to use this dialog box, see the eGate Integrator User's Guide.

    Figure 6–4 Integration Server Properties Dialog Box: Environment

    Integration Server Properties Dialog Box: Environment

  6. For lhA > IntegrationSvr1 on Environment Explorer, set the Configuration > SeeBeyond Integration Server properties as follows:

    • Integration Server URL: Points to the Integration Server, for example:

      • http://localhost:18000 (for envA)

      • http://localhost:28000 (for envB)

    • Username: Administrator

    • Debug port: 1044

    • Password: STC (masked)

    • Application Workspace: Blank, for this sample

    • Number of Local Transactions: 0

  7. For the rest of the IntegrationSvr1 properties settings, accept the defaults.

  8. Create a Sun SeeBeyond JMS IQ Manager under IntegrationSvr1 and name it SBJMSIQMgr1.

ProcedureTo Create and Configure the Oracle External System

  1. On Enterprise Designer, on the Environment Explorer tree, right-click envA (envB for Berlin) and, on the context menu, click New Oracle External System.

  2. Name the new component esOracle and click OK.

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

    Note –

    The eXchange database uses Oracle. For more information on Oracle requirements for eXchange and AS2 PM, see the AS2 Protocol Manager Release Notes.

  3. Right-click esOracle and select Properties from the context menu.

    The Properties dialog box for the external system appears (see Figure 6–5). For more information on how to use this dialog box, see the Oracle eWay Adapter User's Guide.

    Figure 6–5 Oracle External System Properties Dialog Box: Environment

    Oracle External System Properties Dialog Box: Environment

  4. 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

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

ProcedureTo Create and Configure the LDAP External System

  1. Create a new LDAP eWay (New > LDAP External System) under envA (envB for Berlin) and name it esLDAP.

  2. 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, for Atlanta and Berlin (the two URLs must be different), according to the provided syntax, for example:

      ldap://ex4:1389/o=bhex2_1,dc=stc,dc=com

    • Authentication: simple

    • Principal: As necessary for your system

    • Credentials: Password, as necessary for your system

    Note –

    A separate LDAP external system instance is required for each B2B Host.

  3. For all other LDAP eWay (esLDAP) properties, accept the defaults.

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

ProcedureTo Create and Configure the B2B Configurator Service External System

  1. Create a B2B Service Configurator (New > B2B Configurator Service) external system under envA (envB for Berlin) and name it esB2BService.

  2. 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: jdbc:oracle:thin:@hostname:port:exchange

    • UserName: Valid user ID for the current Oracle system

    • Password: Valid password for the current Oracle system (masked)

  3. Set the environment-configuration > JMS Settings properties for esB2BService as follows:

    • JMS Server URL: Points to the IQ Manager port, envA Logical Host on 18000 (envB on 28000), the IQ Manager port for envA: 18007 (28007 for envB), this port number listed in the Domain Manager for the current Logical Host, an example of the URL syntax: 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

  4. For the rest of the B2B Configurator Service properties settings, accept the defaults.

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

ProcedureTo Create and Configure the Keystore External System

  1. Create a Keystore (New > Keystore) external system under envA (envB for Berlin) and name it esKeystore.

  2. Set the Environment Configuration > Connection Settings properties for esKeystore as follows:

    • LDAP: As necessary for your system, for Atlanta and Berlin (the two URLs must be different), according to the provided syntax, for example:

      ldap://ex4:1389/o=bhex2_1,dc=stc,dc=com

    • Password: Valid password for the current Keystore (masked)

    • Keystore Type: PKCS12 (change from default)

    • LDAP User Name: The user name you use for the current LDAP system

    • LDAP User Password: The password you use for the current LDAP system

    • Keystore Provider: BC (change from default)

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

ProcedureTo Create and Configure the File eWays

  1. Create a new File eWay (New > File External System) in inbound mode under envA and name it esFileA.

  2. Set the Configuration > Inbound File eWay > Parameter Settings property for esFileA as follows:

    Directory:


     C:/temp/eXchange/Sample/AS2/Data/Atlanta
    Note –

    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 AS2 named Errors.

  3. Set the Configuration > Outbound File eWay > Parameter Settings property (for DLQ and processing errors) for esFileA as follows:

    Directory:


     C:/temp/eXchange/Sample/AS2/Errors/Atlanta

  4. For all other File eWay (esFileA and esFileB) properties, accept the defaults.

  5. Create a new File eWay (New > File External System) in inbound mode under envB and name it esFileB.

  6. Set the Configuration > Inbound File eWay > Parameter Settings property for esFileB as follows:

    Directory:


     C:/temp/eXchange/Sample/AS2/Data/Berlin

  7. Set the Configuration > Outbound File eWay > Parameter Settings property (for DLQ and processing errors) for esFileB as follows:

    Directory:


     C:/temp/eXchange/Sample/AS2/Errors/Berlin

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

ProcedureTo Create and Configure the Additional External Systems

  1. 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.

  2. 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.

  3. In Properties dialog boxes for your new external systems, accept the defaults.

    Note –

    When you are finished with each Properties dialog box, click OK.

  4. Create an HTTP eWay (client mode) external system under envA (envB for Berlin) and name it esHTTP.

  5. Open the Properties dialog boxes for esHTTP and accept the defaults.

  6. Create an HTTP eWay (server mode) external system under envA (envB for Berlin) and name it esHTTPserver.

  7. Open the Properties dialog boxes for esHTTPserver and accept the defaults.

    Note –

    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.

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

When You Are Finished for Atlanta

Result: You have set up the Environment for Atlanta, envA. See Figure 6–6.

Figure 6–6 Sample Scenario’s Atlanta Environment

Sample Scenario’s Atlanta Environment

When You Are Finished for Berlin

Result: You have set up the Environment for Berlin, envB, which appears directly under envA on the Environment Explorer tree. The Berlin Environment appears similar to the Atlanta Environment shown in Figure 6–6.

Final Result

You have now finished setting up the Environments for Atlanta and Berlin, including the external system components to be used by both.

ProcedureTo Prepare for the Next Steps

  1. Collapse the envA and envB Environment Explorer trees, click Save All, and close all canvases.