ETM Server Program

The ETM Server program will help automate the process to setup and configure items for the tomcat server. The system has a defined set of options to setup the default package that should get the user up and running. The system also has built in portability for advanced options such as changing the rule engine version jars or adding SYSUSER to the tomcat user list. Other features include starting the server or updating java and javascript files. Once system has finished running updates, a log file is generated and displayed to the user to show info/error reports. Below is a general overview of features are installed in the ETM Server Program. See end of document for detailed features.

Basic Features

Initial Setup Flag

- This flag will run all the pre-defined settings for setting up your local environment.

Update java and javascript

- This flag will only run updates on java and javascript that already have SVN paths and have been checked out.

Start server automatically

- This will run the command to startup the tomcat server and set proper environment variables; the command can be combined with the ‘Update java and javascript’ flag option.

Advanced Features

The advanced feature checkbox must be enabled before any changes will take place below.

Selecting rule engine version

- System will allow the user to select from different meridian rule engine releases if the user does not wish to use the latest version. System pulls all folders found on server and defaults to the newest version. If new versions are released, the system will get the latest from the server and set as default.

Adding SYSUSER to tomcat

- This will allow the user to setup the account on the tomcat users group for the SYS user.

Override default user/pass

- By default, the system does an auto lookup of the current user i.e., “rvmad01” and sets the ETM tomcat user as this with the default password. If the user does not want this configuration the ETM Server program gives the user the option to create a custom username and password, given the values entered are valid.

Log Reports

- After the system runs setup, depending on the configuration options selected, the system generates a detailed log report. Most of the entries are informational data but if an error was generated or a feature was skipped it will be displayed in red in the log report.

o Red – Error the system displayed how it was handled.o Yellow – Warn the user of a potential problem.o Black – (DEFAULT) Info that lets the user see what actions took place.

Future Enhancements

• Build the ETM project, run the generate tool and then deploy. This would make it a better use to update the java and javascript.

• Progress bar - so the user knows how much is finished of the process or where the system is in the process.

Detailed Features

1. Initial Setup Feature

a. System will first check to see if initial setup has been run before. If it has ,alert the user and let them know if they want to override and run again.

b. The system will run method to determine current rv ID and set ETM user based on the current rv ID and default password as “password”.

c. The system will copy over three meridian rules jars to the user’s directory.

d. The system will create a repository for the java and javascript paths, then ask the user to confirm these paths and click ‘ok’ and then click ‘yes’ to check the folders out.

e. The system will update the tomcat user xml files to include the current user based on a lookup preformed at the start of the program. The xml files include ncdor-tomcat-users.xml and tomcat-users.xml. Depending on advanced features selected the SYS user could be added to the xml file as well.

f. System will copy over Hibernate 3.2ga files and set the registry path for the hibernate destination.

g. System will edit the environ.ini file to remove the encrypted password with the unencrypted db password.

h. System will search for and replace all encrypted passwords in the hibernate.properties files.

i. System will search for server.xml content lines and comment out, if necessary.

j. System will edit spl.cmd and replace eclipse options variables, if necessary.

k. System will copy over tnsNames.ora over to the correct directory for the user.

l. System will search for and check spl.properties for correct spl.tools.loaded.applications line; if incorrect, it will replace and update.

m. System will copy over eclipse.bat to the current user’s desktop.

2. Updating SVN Features

a. System will update java folder and javascript folder with no user input required, only halts if errors are found.

3. Starting Server Features

a. System will set the necessary environment variables and then start the tomcat server for the user.