NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

CSM 5.0 has introduced using AES encryption to encrpt CSM User information while storing it in CSM_USER table. If you are upgrading CSM from 4.x to 5.x, apart from migrating the database, you would need to run encryption migration. This step expects PASSWORD column values in CSM_USER are not altered from the their original values created through CSM API.

 

        1. Download the CSM UPT v5.2 distribution file into a designated folder (for example, c:\csm_52). Be sure to note the folder name and location.
        2. Extract the contents of  the downloaded csm_upgrade5.2.zip into a designated folder (for example, c:\csm_52\csm_upgrade5.2).
        3. In the designated folder, find and modify the upgrade.properties file. Database properties must be updated with the upgraded database connection details. 
        4. Open the cmd window and navigate to c:\csm_52\csm_upgrade5.2 
        5. Run "ant -Dproperties.file=upgrade.properties migration:run".

...

cli and cli and cli that  

#

Action

1

Set up an environment variable JBOSS_HOME to point to the Wildfly installation directory.

Info
titleWindows Platform
Use either double back slashes // or a single forward slash / as the file separator if working on Windows platform, for example, JBOSS_HOME=C:/wildfly-8.2.0.Final (C:\wildfly-8.2.0.Final would fail).

2

Execute the Ant build script build.xml located at <CANANOLAB_SOURCE>/build with the target deploy:cananolab-webpp.

Example: Issue the following commands to execute the Ant script:

C:\>cd C:\caNanoLab_2.1\build
C:\caNanoLab_2.1\build>ant deploy:cananolab-webapp
 

Successful execution of the Ant script generates the following artifacts that include two deployable web archive war files, configuration files and libraries for running the web application in the Wildfly environment, and also places these artifacts in the appropriate directories under <JBOSS_HOME>. Artifacts generated are also available in the following folder under <CANANOLAB_SOURCE>: 

target/dist/cananolab- webapp/caNanoLab.war  
target/dist/common/ApplicationSecurityConfig.xml
 
target/dist/common/csmupt.csm.new.hibernate.cfg.xml
 
target/dist/common/csmupt423.csm.new.hibernate.cfg.xml
 
target/dist/common/login-config.xml
 
target/dist/common/mysql-connector-java-5.1.26.jar
 
target/dist/common/upt-ds.xml
 
target/dist/common/properties-service.xml
 
target/dist/common/upt-ds.xml 
 
target/dist/common/uptEAR.ear
 
target/dist/common/bcprov-jdk15on-1.47.jar
 
target/dist/common/caNanoLab_modules.cli
 
target/dist/common/caNanoLab_setup.cli
 
target/dist/common/caNanoLab_deploy.cli
  target/dist/common/csmapi-5.2.jar

3

We recommend increasing the JBoss JVM heap size to 2G bytes and permanent generation (permgen) memory space to 256M bytes by updating the file <JBOSS_HOME>/bin/standalone.conf with the following JAVA_OPTS:

JAVA_OPTS="-Xms512m -Xmx2048m -XX:PermSize=128m 
-XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000"

This configuration file is read when Wildfly server starts.

For a standalone server, pass in the JVM settings either as command line arguments when executing the $JBOSS_HOME/bin/standalone.sh script, or by declaring them in $JBOSS_HOME/bin/standalone.conf.
(For Windows users, the script to execute is %JBOSS_HOME%/bin/standalone.bat while the JVM settings can be declared in %JBOSS_HOME%/bin/standalone.conf.bat.)

4

1.    Create a new directory structure C:/local/content/caNanoLab/artifacts and move the following artifacts.

  • csmapi-5.2.jar
  • caNanoLab.war
  • uptEAR.ear
  • bcprov-jdk15on-1.47.jar
  • mysql-connector-java-5.1.26.jar
  • caNanoLab_modules.cli
  • caNanoLab_setup.cli
  • caNanoLab_deploy.cli 

Create a new directory structure C:/local/content/caNanoLab/config and move the following artifacts.

  • ApplicationSecurityConfig.xml
  • csmupt.csm.new.hibernate.cfg.xml
  • wikihelp.properties
5

Start JBoss application server in Standalone mode.

From <install-dir>/bin:

./standalone.sh --server-config=standalone-full.xml

The cli scripts assumes the CLI port is running at 19990. If it is different, update the port number at the second line in the script. 

For Windows environment:

jboss-cli.bat --file=C:/local/content/caNanoLab/artifacts/caNanoLab_modules.

cli and press <ENTER>. 

For Linux environment:

jboss-cli.sh --file= /local/content/caNanoLab/artifacts/caNanoLab_modules.cli and press <ENTER>.

Run the remaining caNanoLab_setup.

cli and caNanoLab_deploy.

cli that deploys the caNanoLab and csmUPT.

After successful completion, you should see following output in the window.

{"outcome"=> "success"}
{"outcome"=> "success"}
{"outcome"=> "success"}
{"outcome"=> "success"}
{
"outcome"=> "success",
"result"=> undefined
}

Verification

Once the deployment artifacts are deployed and the Wildfly application server is correctly configured, shutdown and restart the Wildfly application server, which in turn starts the caNanoLab application.

...