Follow the steps in this chapter to prepare your application server for Waveset.
This chapter includes the following sections:
When installing Waveset on UNIX or Linux systems, the /var/opt/sun/install directory must exist and be writable by the user running the installer.
When running Waveset on multiple physical servers, the servers' system clocks must be synchronized. Each Waveset server regularly issues a timestamped “heartbeat” to the Waveset repository. If any server observes that another server's heartbeat is too old (by default five minutes), then it will mark that server as “recovered” and mark all tasks currently executing on that server as terminated. Proper Waveset operation requires that all server clocks be synchronized to within five minutes of each other, and preferably within one minute.
For a list of supported application server versions, see Application Servers in Oracle Waveset 8.1.1 Release Notes
You may need to perform one or more of these general steps when installing the software:
Use the Oracle GlassFish Server typical installation.
Specify the location for the Installation directory.
Specify the administrator name and password for Application Server administration.
Install the Tomcat software according to the instructions included with Tomcat. You may find helpful information at the Jakarta Project site: http://tomcat.apache.org/
Specify the Tomcat installation location.
Select to start Tomcat as a service, and then select the port to run on. The default port is 8080.
After downloading and unpacking the Tomcat installation bundle, modify the Tomcat startup script by using this procedure:
In the setclasspath.sh file in the $TOMCAT_HOME/bin directory, add these lines to the top of the file:
JAVA_HOME=Location of a JDK BASEDIR=Location of your unpacked Tomcat export JAVA_HOME BASEDIR |
When configuring Tomcat to support UTF-8, add the URIEncoding="UTF-8" attribute to the connector element in the TomcatDir/conf/server.xml file, for example:
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified during installation --> <Connector port="8080" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8" /> |
When configuring Tomcat to support UTF-8, also add -Dfile.encoding=UTF-8 in your Java VM options.
Install WebLogic using the instructions provided with the software. To configure WebLogic before installing Waveset, see Step 1: Configure the WebLogic Software.
Install WebSphere using the instructions provided with the software. To configure WebSphere before installing Waveset, see Step 1: Configure WebSphere.
Install JBoss using the instructions provided with the software. You may find helpful information at the JBoss Project site, at http://www.jboss.org/jbossas .
You may need to perform one or more of these general steps when installing the software:
Install the full JBoss application server.
Ensure that the JBoss installation path does not contain spaces.
Specify the administrator name and password for Application Server administration.
When configuring JBoss to support UTF-8, add the URIEncoding="UTF-8" attribute to the Connector element in the InstallDir\server\default\deploy\jbossweb-tomcat55.sar\server.xml file, for example:
<!-- A HTTP/1.1 Connector on port 8080 --> <Connector port="17001" address="${jboss.bind.address}" maxThreads="250" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8" />
When configuring JBoss to support UTF-8, also add -Dfile.encoding=UTF-8 in your Java VM options.
Increase the JBoss PermGen space to avoid out-of-memory errors. For example, add the following arguments in your JAVA_OPTS environment variable to increase the space to 128 MB:
-XX:PermSize=128m -XX:MaxPermSize=128m
Follow these general steps when installing the software. For details, see the documentation provided by Oracle.
Use the Oracle Enterprise Manager 10g Application Server typical installation.
Specify the location for the installation directory.
Specify the administrator name and password for Application Server administration.
The application server should be configured to use the same locale or encoding as the database and the Java Virtual Machine (JVM).
Inconsistent encodings may introduce certain globalization issues, such as incorrect handlings of multibyte characters. In globalized environments, UTF-8 should be implemented on all products.
Refer to your application server documentation for information about setting the locale/encoding. Also, when loading or unloading data using CSV or XML files, ensure that their encodings are consistent with Waveset’s deployment environment encoding to retain data integrity. For enabling localization support see Enabling Language Support.
You must create the directory where you will store application files before launching the installation program. You can store application files in a staging directory, or you can install into your application server’s Web application directory.
Because Waveset applications are based on J2EE Web, you can store them in a staging directory. This staging directory is used to deploy the application into your specific application server. Typically, a Web Application Archive (.war) file is created for use in the deployment steps.
You may choose to install directly into an application server’s Web application directory. In this case, you will specify the Web application directory during installation. The installation program will place the Waveset files in a folder named idm in that location by default.
If you use a localfiles repository instead of a database, set the localfiles repository to a location outside of the Waveset directory on the application server. See If You Are Not Using a Database for more information.
The application server requires a Java compiler and a Java Virtual Machine (JVM) to run the Java classes that perform actions within Waveset. Both of these can be found in a Java SDK. (The JRE packages do not include a Java compiler.)
Many application servers include a JDK bundled with their installation. The JDK version that is shipped with the application server is always preferred to any other JDK installed on your server.
You can run Waveset on BEA WebLogic application servers with all WebLogic-supported 1.5 JVMs.
You should add JAVA_HOME to your list of system environment variables and to your system path. To do this, add JAVA_HOME to your system environment and JAVA_HOME\bin to your path, making sure to list it before any other Java variables. While adding JAVA_HOME to your list of system environment variables is helpful for Waveset, it may affect other applications.
The JVM should be configured to use the same locale or encoding as the application server and the database.
You should determine your memory needs and set values in your application server’s JVM. Do this by adding maximum and minimum heap size to the Java command line; for example:
java -Xmx512M -Xms512M
For best performance, set these values to the same size. Depending on your specific implementation, you may need to increase these recommended values if you run reconciliation.
For performance tuning purposes, you may also set the following in the waveset.property file:
max.post.memory.size value
The property max.post.memory.size specifies the maximum number of bytes that a posted file may contain without being spooled to the disk. For cases where you do not have permission to write to temp files, you should increase max.post.memory.size to avoid having to spool to the disk. The default value is 8 Kbytes.
For additional system requirements and information, refer to the Oracle Waveset 8.1.1 Release Notes.