Manual Installation Guide ParaDM Document Management
Manual Installation Guide ParaDM Document Management
ParaDM
Deployment Guide for Windows
Version 3.2.3
Version Control
Document Information
Prepared By Saichu Cheng
Version History
Date Version Author Description of Changes
Number
03 January 2008 3.2.3 Saichu Cheng Enriched Contents with Different Web Application and
Database Servers
Table of Contents
VERSION CONTROL ............................................................................................ 2
1 OVERVIEW ..................................................................................................... 5
1 Overview
In this document, the installation procedure of Full functions of ParaDM system
version 3.2.X with MySQL, MSSQL and Oracle database and Tomcat, WebLogic and
Websphere Web Application Server in the same Windows 32-bit server machine will
be discussed. All paths discussed in this installation guide are predefined for simplicity.
Applications are recommended to be installed in the same partition of operation system
(usually C drive) while ParaDM system and storage of database should be installed in
another partition which has a bigger storage capacity (usually D drive). Those paths may
need to be changed according to the deployment server environment. The following
installation steps will be covered.
Source http://java.sun.com/j2se/1.4.2/download.html
File j2sdk-1_4_X_XX-windows-i586-p.exe
Source http://tomcat.apache.org/download-55.cgi
File jakarta-tomcat-5.0.XX.exe
Source http://tomcat.apache.org/download-55.cgi
File jakarta-tomcat-5.0.XX.exe
ParaDM System
Producer ParaDM Company Limited
Files i. paradm-web-3.2.X.zip
Click “Install” and “Next” until finishing the installation as below screens.
When below windows prompts, check “Configure the MySQL Server now” in the
windows for the configuration of MySQL server. Click “Finish”.
Check “Enable TCP/IP Networking” with Port Number “3306” and “Enable Strict
Mode”; then click “Next”.
Choose “Best Support For Multilingualism” which is UTF8 by default, and click
“Next”.
Check “Install As Windows Service” with Service Name “MySQL”, and “Include
Bin Directory in Windows PATH”, and click “Next”.
Check “Modify Security Settings” and provide a password for the account “root”; then
click “Next”.
(Remember and keep secure for this password that will be used for database creation)
Click “Execute”.
Input the password which was created during installation of MySQL, press “enter”
button.
Create Database for ParaDM with the following commands except the sentence in (…).
USE ParaDM;
SOURCE D:\ParaDM\DB\structure.sql
SOURCE D:\ParaDM\DB\data.sql
-- Run this SQL if you are want to change the default physical files storage location
SET @PARADM_PATH='D:/ParaDM/file';
(The above strings marked as RED colours may be different according to the
favourites from End User)
ParaDM.* – refers to the database created above
'paradm'@'localhost' – refers to the database granted to a user
“paradm” who can log on the MySQL in this local machine only
'password' – refers to the logon password of the user “paradm”
4.2 MSSQL
Input the database server IP address or fully qualified domain name (FQDN)
and log on as system administrator.
Click mouse right-button on “Logins” under Security and choose “New Login”.
Input “paradmuser” as Login name with the password under “SQL Server
authentication”, then check and uncheck “Enforce password policy” and “Enforce
password expiration” respectively as follows.
(The Login name can be any other you like, and remember this user account that
will be used later)
You can see the new user account is in the summary tab of details panel.
Right click the root directory of ParaDM database and choose “New Query”.
Copy the following SQL statements into SQL Query Analyser for the update the
file location.
(The value of the path may be different if your folder hierarchy for the ParaDM
system is different to this document)
-- Run this SQL if you are want to change the default physical files storage
location
DECLARE @PARADM_PATH VARCHAR(100);
SET @PARADM_PATH = 'D:/ParaDM/file';
UPDATE SYS_PARAMETER SET PARAMETER_VALUE = REPLACE(PARAMETER_VALUE,
'D:/ParaDM/file', @PARADM_PATH) WHERE PARAMETER_VALUE LIKE
'D:/ParaDM/file%';
Click “Execute” to update the physical file storage location of the ParaDM System.
4.3 Oracle
Select the “Create a Database” radio button and then click on the “Next” button.
Select the “General Purpose” radio button and then click on the “Next” button.
Select the “Configure the Database with Enterprise Manager” checkbox and select
the “Use Database Control for Database Management” radio button. Leave the
“Enable Email Notifications” and “Enable Daily Backup” checkboxes as blank.
Click on the “Next” button to move on.
Select the “Use the Same Password for All Accounts” radio button and enter your
password (Note: remember this password which will be used to login to the Oracle
Enterprise Manager).
Select the “File System” radio button and then click on the “Next” button.
Select the “Use Common Location for All Database Files” radio button and enter
“D:\Oracle\Data” as the database files location. This means that all the ParaDM
database file will go into this directory.
Select the “Specify Flash Recovery Area” checkbox and keep the default setting
for the “Flash Recovery Area” and “Flash Recovery Area Size” values. Click on
the “Next” button.
On the Sample Schemas tab, leave the “Sample Schemas” as blank. On the Custom
Scripts tab, select the “No Scripts to run” radio button and then click on the “Next”
button.
Keep every thing as the default values expect the “Character Sets” tab. Click on
the Character Sets” tab and specify the character sets as follow:
Select the “Create Database” checkbox and leave the “Save as Database Template”
and “Generate Database Creation Scripts” as blank. Click on the “Finish” button to
move on.
Click on the “OK” button to confirm the configuration and begin the creation.
Once its completed, a summary page will be shown up. Click on the “Exit” to
complete the creation.
Click on the “Users” action link under the “User & Privileges” section.
Click on the “Roles” tab to modify the user roles. Select the “DBA” from the
Available Roles list and then click on the “Move” arrow to add to the Selected Roles
list.
Click on the “OK” button to confirm the modification. The DBA role should now be
shown in the User Roles list.
Still in the Oracle Database Control of “orcl”. Under the “Administration” tab, click on
the “iSQLPlus” action link.
Select the Connect as “Normal” radio button and then click the “Continue” button.
Copy the “structure.sql” from the database folder and then paste it into the text area.
Click on the “Execute” button to execute the SQL statement.
Once its executed, click on the “Clear” button to clean up the text area.
Copy the “data.sql” from the database folder and then paste it into the text area. Click on
the “Execute” button to execute the SQL statement.
Once its executed, click on the “Clear” button to clean up the text area.
Now update the file location by copy and paste the following command into the text
area. Click on the “Execute” button to execute the update.
-- Run this SQL if you are want to change the default physical files storage
location
DEFINE PARADM_PATH='D:/ParaDM/file';
UPDATE SYS_PARAMETER SET PARAMETER_VALUE = REPLACE(PARAMETER_VALUE,
'D:/ParaDM/file', '&PARADM_PATH') WHERE PARAMETER_VALUE LIKE
'D:/ParaDM/file%';
UPDATE DMS_LOC_MASTER SET LOC_PATH= CONCAT('&PARADM_PATH','/ParaDOC');
Choose “Custom” as the installation type and check “Service”; then click “Next”.
Set “8080” for HTTP Connector Port, and the information for “Administrator Login”.
(Remember and keep highly secure for this password)
Choose the “Java Virtual Machine” location as “C:\J2SE1.4”, and click “Install”.
Uncheck both “Run Apache Tomcat” and “Show Readme”; then click “Finish” to complete the
installation.
6.2 WebLogic
Choose “Production Mode” as “WebLogic Domain Startup Mode”, and “Sun SDK
1.X.X@C:\bea\jdk1XX_XX” as default JDK for this domain.(Version may be different to
the following figure), then click “Next”
Resources
In order to enable WebDAV in Weblogic 9.2 or above, you need to turn off the application
server BASIC authentication.
Add the <enforce-valid-basic-auth-credentials> element to config.xml within the
<security-configuration> element.
<security-configuration>
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-cr
edentials>
</security-configuration>
Reference links:
http://www.mail-archive.com/[email protected]/msg01562.html
http://www.wso2.org/library/880 (Security Provider Configuration section)
7.2.1 MySQL
Edit the “struts-config.xml” by notepad located at
“D:\ParaDM\Webapp\WEB-INF” for the modification of the database connection
string.
Search “<!-- MySQL Data Source -->”, and locate the following paragraph under
the string.
<set-property property="password"
value="1"/>
<set-property property="url"
value="jdbc:mysql://localhost:3306/eip?useUnicode=true&characterEncoding=UTF-
8&autoReconnect=true"/>
<set-property property="username"
value="root"/>
Modify the values as follows; then save and exit the file.
<set-property property="password"
value="password"/>
<set-property property="url"
value="jdbc:mysql://localhost:3306/ParaDM?useUnicode=true&characterEncoding=
UTF-8&autoReconnect=true"/>
<set-property property="username"
value="paradm"/>
(The above four strings (values) marked as RED Colours are dependent on during
the creation of MySQL database and privileges of user account; therefore, the
values may be different.)
7.2.2 MSSQL
Edit the “struts-config.xml” by notepad located at
“D:\ParaDM\Webapp\WEB-INF” for the modification of the database connection
string.
Search the following statements and ensure their sub-tabs are all commented.
<!-- MySQL Data Source -->
<!-- MS SQL Data Source using JTDS jdbc driver -->
<!-- Oracle Data Source -->
Search the following statement and ensure its sub-tab is uncommented.
<!-- MS SQL Data Source using Microsoft jdbc driver -->
Find the following statements under
<!-- MS SQL Data Source using Microsoft jdbc driver -->
<set-property property="password"
value="password"/>
<set-property property="url"
value="jdbc:sqlserver://localhost:1433;databaseName=paradm;selectMethod=cursor"/>
<set-property property="username"
value="ParaDM_User"/>
Modify the values as follows; then save and exit the file.
<set-property property="password"
value="pass1234"/>
<set-property property="url"
value="jdbc:sqlserver://192.168.0.233:1433;databaseName=paradm;selectMethod=cursor"/>
<set-property property="username"
value="paradmuser"/>
(The above four strings (values) marked as RED Colours are dependent on the location and
the user account of MSSQL database server; therefore, the values may be different.)
7.2.3 Oracle
Edit the “struts-config.xml” by notepad located at
“D:\ParaDM\Webapp\WEB-INF” for the modification of the database connection
string.
Comment out the default database connection. Search “<!-- MySQL Data Source
-->” and modify as following
<!-- MySQL Data Source -->
<!--
<data-source type="org.apache.commons.dbcp.BasicDataSource">
<set-property property="defaultAutoCommit"
value="false"/>
<set-property property="defaultReadOnly"
value="false"/>
<set-property property="description"
<set-property property="driverClassName"
value="com.mysql.jdbc.Driver"/>
<set-property property="maxActive"
value="60"/>
<set-property property="maxIdle"
value="3"/>
<set-property property="maxWait"
value="5000"/>
<set-property property="poolPreparedStatements"
value="true"/>
<set-property property="maxOpenPreparedStatements"
value="500"/>
<set-property property="password"
value=""/>
<set-property property="url"
value="jdbc:mysql://localhost:3306/eip320?useUnicode=true&characterEnc
oding=UTF-8&autoReconnect=true"/>
<set-property property="username"
value="root"/>
<set-property property="logAbandoned"
value="true"/>
<set-property property="removeAbandoned"
value="true"/>
<set-property property="testWhileIdle"
value="true"/>
<set-property property="validationQuery"
value="SELECT NULL"/>
</data-source>
-->
Uncomment the oracle database connection section. Search “<!-- Oracle Data
Source -->” and remove the comment tag “<!--" and “-->”.
Locate the following paragraph under the string.
Modify the values as follows; then save and exit the file.
<set-property property="url"
value="jdbc:oracle:thin:@//127.0.0.1:1521/paradm"/>
(The above four strings (values) marked as RED Colours are dependent on during the
creation of Oracle database and privileges of user account; therefore, the values may be
different.)
<layout class="org.apache.log4j.PatternLayout">
</layout>
</appender>
<appender name="ROLLING_FILE"
class="org.apache.log4j.DailyRollingFileAppender">
<layout class="org.apache.log4j.PatternLayout">
</layout>
</appender>
7.4.1 Tomcat
Open the “Configure Tomcat” program in the “All programs” from “Start”
menu.
Press the tab “Java”, and input “1024” into both “Initial memory pool” (IMP) and
“Maximum memory pool” (MMP) respectively; then press “OK”.
(Value of MMP should be half of physical memory and cannot exceed 1024 in
Win32 System.)
</Context>
Click “Add” to put this Universal Resource Locator (URL) as a trusted web site.
Click “Close”.
Once you find the following page prompts, the deployment finishes.
7.4.2 WebLogic
Be sure the following contents already into weblogic.xml (create this file if it is
unavailable) in D:\ParaDM\Webapp\WEB-INF
(In the following tab, the value in context-root will represent the context path of the
URL for ParaDM)
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
<context-root>/ParaDM</context-root>
</weblogic-web-app>
Input the weblogic user account created above and click “Log In”.
Provide the Name “ParaDM” for this deployment, and click “Finish”.
Go back to “Deployments” and start its service by click “Serving all requests”.
Once you find the following page prompts, the deployment finishes.
7.4.3 Websphere
Important Notes: there is a critical bugs in Websphere version 6.1.0, please make
sure you have apply the latest patch to upgrade the Websphere to version 6.1.0.13 or
above.
Create a war file. Add the ParaDM webapp to archive and name it “webapp.war”.
Click on the “Install New Application” action link under the “Applications” panel.
Select the “Local file system” radio button and locate the “webapp.war” file you
have just created. In this case, the webapp.war file is in the D:\ParaDM\Webapp\
folder. Enter “ParaDM into the “Context root” text box and select the “Prompt me
only when additional information is required” radio button. Click on the “Next” to
continue the installation
In the “Select installation option” page, keep the setting as it is and only enter
“ParaDM” into the “Application name” text box. Click on the “Next” button to
continue.
In the “Map modules to servers” page, keep the setting as it is. Click on the “Next”
button to continue.
In the “Map virtual hosts for web modules” page, keep the setting as it is. Click on
the “Next” button to continue.
The status page is then shown up. Once the installation is done, your page should be
be the same as the following figure. Click on the “Manage Applications” action link
to configure the ParaDM application.
Click on the ParaDM application. Note: do not click on the “Save” button yet, we
will do so once the ParaDM application is well configured.
Click on the “Class loading and update detection” action link under the Detail
Properties section.
Now the ParaDM application is well configuration. Click on the “Save” action link
to save the configuration.
Once the configuration is saved, a little red cross will be shown in the Application
Status column under the ParaDM application.
Select the “ParaDM” checkbox and then click on the “Start” button to startup the
application.
Once its started, the Application Status will be changed to a green arrow.
To test the application, open up the Internet Explorer and enter the following URL:
http://{Server IP Address}:9080/ParaDM
Note: by default, WebSphere will run the enterprise application under 9080 port.