Actions
Deployment » History » Revision 24
« Previous |
Revision 24/25
(diff)
| Next »
chin-yeh, 07/20/2011 02:14 PM
- Table of contents
- Deployment
Deployment¶
Prerequisite:- Completed Installation section
- Completed Configuration section
This section describes how to deploy components/modules to the servers.
Deployment Architecture:
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 |
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/qconnector
ws-mimic¶
List of the properties files to be uploaded:- Note: replace {environment} with either production (for production environment) or development (for development environment)
- see the Deployment section for the deployment target
- upload the following files to /data/qconnector/ws-mimic/ directory via ftp or sftp:
- application.properties
- jndi-factory.properties
- make sure everyone has the read-access to the above files
- 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
- see the Deployment section for the deployment target
- upload the following file(s) to /data/qconnector/ecosway-adaptor/ directory via ftp or sftp:
- application.properties
- database.properties
- upload the following file(s) to /data/qconnector/ecosway-adaptor/registration/ directory via ftp or sftp:
- template.properties
- make sure everyone has the read-access to the above files
- 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)
- see the Deployment section for the deployment target
- upload the following file(s) to /data/qconnector/ws-status/ directory via ftp or sftp:
- database.properties
- make sure everyone has the read-access to the above files
- done
ecwyadaptor¶
List of the properties files to be uploaded:- Note: replace {environment} with either production (for production environment) or development (for development environment)
- see the Deployment section for the deployment target
- upload the following file(s) to /data/qconnector/ecwyadaptor/ directory via ftp or sftp:
- make sure everyone has the read-access to the above files
- 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:- choose one of the methods:
- build from source files:
- build the deployment file (see Build components from sources)
- rename the deployment file to ecwyconnector.war
- download the binary from internal repository (see Nexus):
- component name: ecwyconnector
- component version: see Latest Version
- build from source files:
- 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
- if target server is Jboss AS 4.2.2
- restart jboss
- done
Deploy ecosway-adaptor¶
Deploy ws-mimic¶
Steps:- choose one of the methods:
- build from source files
- build the deployment file (see Build components from sources)
- rename the deployment file to ws-mimic.war
- download the binary from internal repository (see Nexus):
- component name: ws-mimic
- component version: see Latest Version
- build from source files
- upload the file to target server
.../jboss5.1.0.GA/server/{profile name}/deploy
- restart jboss
- done
Deploy ws-status¶
See Deploy ws-status
Updated by chin-yeh over 13 years ago · 24 revisions