• Table of contents
• Deployment
  • Upload properties files
    • ws-mimic
    • ecosway-adaptor
    • ws-status
    • ecwyadaptor
  • Deploy WAR/JAR file
    • Deploy ecwyconnector
    • Deploy ecosway-adaptor
    • Deploy ws-mimic
    • Deploy ws-status

Deployment¶

Prerequisite:

• Completed Installation section
• Completed Configuration section

This section describes how to deploy components/modules to the servers.

Deployment Architecture:

The deployment's tasks are summarized in the below table:

Component	Type	Target
ecwyconnector	WAR	Dot Com Mall / QueueSystem
ecosway-adaptor	JAR	US Mall
ws-mimic	WAR	US Mall / QueueSystem
ws-status	WAR	US Mall

In general, this deployment task involves 2 parts:

1. Upload properties files
2. Deploy WAR/JAR file

Upload properties files¶

This section is dedicated for the first time deployment only. For subsequent deployment, you should update the existing properties files when needed.

All of the properties files can be found in SVN repository:

http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config

All of the properties files should store in the directory:

/data/ecwyconnector

ws-mimic¶

List of the properties files to be uploaded:

• Note: replace {environment} with either production (for production environment) or development (for development environment)
  • application.properties - http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ws-mimic/properties/application.properties
  • jndi-factory.properties - http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ws-mimic/properties/jndi-factory.properties

Steps:

1. see the Deployment section for the deployment target
2. upload the following files to /data/ecwyconnector/ws-mimic/ directory via ftp or sftp:
   • application.properties
   • jndi-factory.properties
3. make sure everyone has the read-access to the above files
4. done

ecosway-adaptor¶

List of the properties files to be uploaded:

• Note: replace {environment} with either production (for production environment) or development (for development environment)
  • application.properties - http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ecosway-adaptor/properties/application.properties
  • database.properties - http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ecosway-adaptor/properties/database.properties
  • registration/template.properties - http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ecosway-adaptor/properties/registration/template.properties

Steps:

1. see the Deployment section for the deployment target
2. upload the following file(s) to /data/ecwyconnector/ecosway-adaptor/ directory via ftp or sftp:
   • application.properties
   • database.properties
3. upload the following file(s) to /data/ecwyconnector/ecosway-adaptor/registration/ directory via ftp or sftp:
   • template.properties
4. make sure everyone has the read-access to the above files
5. done

ws-status¶

List of the properties files to be uploaded:

• Note: replace {environment} with either production (for production environment) or development (for development environment)
  • database.properties - http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ws-status/properties/database.properties

Steps:

1. see the Deployment section for the deployment target
2. upload the following file(s) to /data/ecwyconnector/ws-status/ directory via ftp or sftp:
   • database.properties
3. make sure everyone has the read-access to the above files
4. done

ecwyadaptor¶

List of the properties files to be uploaded:

• Note: replace {environment} with either production (for production environment) or development (for development environment)

Steps:

1. see the Deployment section for the deployment target
2. upload the following file(s) to /data/ecwyconnector/ecwyadaptor/ directory via ftp or sftp:
   • database.properties - http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ecwyadaptor/properties/database.properties
3. make sure everyone has the read-access to the above files
4. done

Deploy WAR/JAR file¶

• Refer to Deployment section to see the list of available components and deployment target.
• Refer to the Components section for the latest component version.

Deploy ecwyconnector¶

Steps:

1. choose one of the methods:
   1. build from source files:
      1. build the deployment file (see Build components from sources)
      2. rename the deployment file to ecwyconnector.war
   2. download the binary from internal repository (see Nexus):
      • component name: ecwyconnector
      • component version: see Latest Version
2. upload the file to target server
   • if target server is Jboss AS 4.2.2
     • upload to /usr/local/jboss-4.2.2.GA/server/{profile name}/deploy
3. restart jboss
4. done

Deploy ecosway-adaptor¶

See Deploy ecosway-adaptor

Deploy ws-mimic¶

Steps:

1. choose one of the methods:
   1. build from source files
      1. build the deployment file (see Build components from sources)
      2. rename the deployment file to ws-mimic.war
   2. download the binary from internal repository (see Nexus):
      • component name: ws-mimic
      • component version: see Latest Version
2. upload the file to target server
   

   .../jboss5.1.0.GA/server/{profile name}/deploy
   

3. restart jboss
4. done

Deploy ws-status¶

See Deploy ws-status