Preconfiguration for the Atlanta and Berlin Environments

This section explains the preconfiguration operations you must perform for the Atlanta and Berlin Environments.

Creating and Starting the Domains

This section explains how to create and start the Logical Host Domains for the Atlanta and Berlin Environments.

See the eGate Integrator User’s Guide for more information about eGate logical hosts, domains, and the Domain Manager feature.

To Create and Start the Sample Domains

1. Create the domains.

   • To create the Atlanta domain, run the following script in the \logicalhost directory:

     C:\ … logicalhost\createdomain --dname dmnA

   • To create the Berlin domain, run the following script in the \logicalhost directory:

     C:\ … logicalhost\createdomain --dname dmnB --startingport 28000

     This script creates the domain name dmnB and designates the default ports 2800x.

2. If the repository is not already running, start it by running the following script:

   C:\ ... repository\startserver.bat

3. Start the domains.

   • To start the Atlanta domain , type the following command:

     C:\ … logicalhost\start_dmnA.bat

     ---

     Note –

     Starting the first domain can require approximately 7 minutes.

     ---

   • To start the Berlin domain , type the following command:

     C:\ … logicalhost\start_dmnB.bat

4. Use the Domain Manager interface to make sure the new domains are started and running.

Adding a New User to ePM and Message Tracking

You must add two new ePM users, one for Atlanta and one for Berlin, using the eGate Integration Server Security Gateway.

To Add a New User To the ePM and Message Tracking Groups

1. With the Repository running, start a new browser session.

2. Access the appropriate URL.

   • Atlanta:http://localhost:18000

   • Berlin:http://localhost:28000

3. Log in to Integration Server Security Gateway using with the username Administrator and the password STC.

4. In the Integration Server Administration window, click the User Management tab.

   Figure 6–2 Screen capture of Integration Server Administration, User Management tab

   
   

5. Select Add New User and supply the user name and password for the new user.

   • Atlanta:

     • Assign the user name userA

     • Assign the password userA

   • Berlin:

     • Assign the user name userB

     • Assign the password userB

6. For Group List, type PartnerManager, MessageTracking

   This step provides the following user privileges:

   • The PartnerManager role allows the specified user to log in to and use ePM.

   • The MessageTracking role allows the specified user to use the Message Tracking Web client.

7. When you are finished, click Submit.

8. Log out of Integration Server Administration and close the window.

Adding the Application Server Instances

You must add two new instances of the Application Server using the eGate Enterprise Manager, one for Atlanta and one for Berlin. Therefore, perform this procedure twice, once for Atlanta and once for Berlin.

To Add Two New Application Server Instances

1. With the Repository running, install Enterprise Manager by running the following script:

   C:\ … \emanager\install.bat

2. In the installation wizard, follow the prompts and accept the license agreement and default port (15000).

3. After the installation is complete, start Enterprise Manager server by running the following script:

   C:\ … \emanager\startserver.bat

4. Start a new browser session and access the appropriate URL:

   http://localhost:15000

5. Log in to Enterprise Manager with the user name Administrator and the password STC.

6. Select J2EE.

7. Click the Manage Servers tab, and add a new application server.

   • Server Type:Sun SeeBeyond Integration Server

   • Host Name:localhost

   • User Name:Administrator

   • Password:STC

   Figure 6–3 Enterprise Manager Window

   
   

8. Click Connect to Server.

9. Save your changes and exit the window.

Initializing and Running Enterprise Designer

This section describes operations to perform once you have initialized and run the Enterprise Designer.

Using Enterprise Designer, increase the eDesigner_heap_size property to 1024. For more information, see the eXchange Integrator User’s Guide.

To Initialize and Run Enterprise Designer

1. With the Repository running, start Enterprise Designer by running the following script:

   C:\ … \edesigner\bin\runed.bat

2. Choose Update Center from the Tools menu.

3. In the Update Center wizard, follow the steps to check for updates, and to add all available updates and new modules.

4. When you are done, restart Enterprise Designer (referred to as IDE in the user interface).

   ---

   Note –

   For more information, see the eGate Integrator User’s Guide.

   ---

5. Log in to Enterprise Designer with the user name Administrator and the password STC.

Next Steps

Patch each Logical Host domain with .jar files to ensure message validation using the EDIFECS service.

To Patch the Domains With Files For Validation

1. To ensure correct third-party validation of messages, you must locate the following files in Enterprise Designer’s Project Explorer under Sun SeeBeyond ⇒ eXchange ⇒ Protocol Managers ⇒ HIPAA Manager ⇒ Validations ⇒ EDIFECS ⇒ Files:

   • xengine.jar

   • xe_extensions.jar

2. Export these files to the following locations in your installation:

   • For Atlanta:

     C:\ … \logicalhost\is\domains\dmnA\lib\

   • For Berlin:

     C:\ … \logicalhost\is\domains\dmnB\lib\

   ---

   Note –

   For more information, see Third-party Validation.

   ---