 |
Page History
...
| Anchor | ||||
|---|---|---|---|---|
|
Property files use to determine configurations for packaging and deployments.
package.sh: Properties available for package.properties
Property | Description |
|---|---|
master_lbconfig | Full path to "lbconfig.props" file. Used as the "source" environment to package from. |
publish_dir | Full path to the directory to "publish" to. Needs to be large enough to contain the LexEVS 51 database export files as well Lucene index files for the selected terminologies. |
...
| Anchor | ||||
|---|---|---|---|---|
|
deploy.sh: Properties available for deploy.properties
Property | Description | ||
|---|---|---|---|
target_lbconfig | Full path to the "lbconfig.props" file of the target environment to be deployed to. | ||
publish_dir | Full path to the publishing directory. | ||
ssh.key.file | Full path to the SSH private key. A SSH public key needs to be installed under JBoss user account (as normally done with BDA projects). | ||
| The following "target_name_#" properties can be repeated for each web application that needs to be stopped/started after a data deployment. To uniquely identify server properties, target names are appended by a '_#' where '#' is an integer value from 0 to 9 to indicating the server number.
Note: Starting deploy.sh with a '-r' option disables stopping and starting of application servers all together. | ||
target_url_# | URL to the lexevsapi51 server. Used by "deploy.sh" to determine if the lexevsapi51 application is running or not. | ||
target_server_# | The application server name. | ||
target_user_# | JBoss user id. Used for the SSH connection needed to stop/start the various application servers. | ||
target_start_jboss_path_# | Full path to JBoss start_jboss script. | ||
target_stop_jboss_path_# | Full path to JBoss stop_jboss script. |
...
| Info | ||
|---|---|---|
| ||
|
Additional Notes
Stopping/starting Jboss
JBoss servers are stopped/started via SSH by invoking the JBoss start_jboss and stop_jboss scripts (as defined in deploy.properties). Up to 10 JBoss servers can be stopped and started this way.
(Stopping/starting of application servers can be disabled using ‘-r’ option on deploy.sh)
Checking if Jboss has started
The deploy app checks the web applications JBoss URL to see if it has started.
