Installation
- Unzip the ilign-server.zip file to the appropriate directory. This is typically c:\ but it can be anywhere. Make sure that you select the option to use folder names when unzipping.
- It will unzip to five directories - db contains JDBC drivers for the databases we support, instance001 is your production instance, instance002 is your test instance, jre contains the Java Runtime Environment and jsw contains start-up configuration files plus code to run the application as a service.
- From the db directory, copy the jtds-1.2.jar file to instance001/tomcat/common/lib and instance002/tomcat/common/lib. (Oracle users should copy the ojdbc14.jar file instead.)
- Rename the mssql-context-template.xml file in instance001/tomcat/conf to context.xml (Oracle users should rename oracle-context-template.xml).
- Edit the context.xml file:
- update the user credentials - set the user and password parameters as per your production database (refer previous step: Create Databases)
- in the jdbcUrl parameter, SQL Server users should replace hostname with the hostname or IP address of their database server and databasename with the name of the production database (ie ilign).
- Oracle users should replace hostname with the hostname or IP address of their database server and SID with the SID
- Save the file and repeat the process with the context.xml file from instance002/tomcat/conf using the test database details.
- Rename the server-template.xml file in instance001/tomcat/conf to server.xml; repeat for instance002. The server.xml file defines which port number and optionally which IP address the application will listen on.
- Copy the ROOT.war file to instance001/webapps and instance002/webapps.
- There is a feature in i-lign where users can send server log files back to the i-lign web site in case of errors. For this to work in your network the i-lign server must either be able to make a direct connection to the i-lign web site, or you must edit the ilign-main.conf file in the jsw directory and set the http.proxyHost and http.proxyPort to be the hostname and port number of your proxy server. Note that i-lign is not able to authenticate to the proxy server, so you may also need to configure your proxy to not require authentication from the server running i-lign.
- If you are using Oracle then find the lines in ilign-main.conf containing ‘wrapper.java.additional.9='. Comment the first line (which indicates SQL Server) and uncomment the last line (which indicates Oracle).
- If you did not install i-lign into the c: drive you'll need to edit the ilign-properties.conf file and change the set.ILIGN_INSTALL parameter appropriately. It needs to point to the ilign-server directory.
- By default each instance is allowed to use up to 1GB of memory. If you need to change this, edit instance001.conf or instance002.conf in the jsw directory and change maxmemory setting.
- By default the name and description of the i-lign services are called eg ‘i-lign - instance001'. To change this, edit the instance001.conf, add the following lines and change as required (do the same for instance002.conf):
wrapper.ntservice.name=i-lign - %INSTANCE%
wrapper.ntservice.displayname=i-lign - %INSTANCE%
wrapper.ntservice.description=i-lign - %INSTANCE%
- To install the Windows services, open a command prompt and change the directory to the jsw directory. Type 'wrapper -i instance001.conf' and then 'wrapper -i instance002.conf'. To remove the services use ‘wrapper -r instance001.conf'.
- Once this is completed start both instances from the Services control panel.
- By default, instance001 will run on port 80 and instance002 will run on port 8180. These can be changed by editing the tomcat\conf\server.xml file and changing <connector port="xxx"> to the desired port number.
- The URLs will be http://hostname for production and http://hostname:8180 for test.
|
