This part of the installation guide contain instructions on how to install Waveset.
Complete the instructions in the chapter for your application server.
These instructions are divided into the following steps. During installation, you will need to know the password you selected when you set up the database.
If you are installing multiple instances of Waveset on a single application server, change the waveset.serverId system property to a unique name for each Waveset instance. By default, the waveset.serverId Java system property is the name of the machine the application server is installed on. To set this property to another value, add the following command to the startup script for your application server.
-Dwaveset.serverId=Name
You may install the software using one of two methods:
Using the installer Graphic User Interface
Run the install.bat (for Windows) or install (for UNIX) command to launch the installation process.
If you copy the files from the installation media to your own location, note that the idm.war and install.class files must be in the same directory.
The installer displays the Welcome panel.
Using the nodisplay option (UNIX only)
On UNIX systems, open the directory where the software is located. Enter the following command to activate the installer in nodisplay mode:
install -nodisplay
The installer displays the Welcome text. The installer then presents a list of questions to gather installation information in the same order as the Graphic User Interface installer in these procedures.
If no display is present, the installer defaults to the nodisplay option. The DISPLAY environment variable must be set to a valid X server or the installation may fail.
Click Next.
The installer displays the Install or Upgrade? panel.
Leave the New Installation option selected, and then click Next.
The installer displays the Select Installation Directory panel.
Replace the displayed directory location with the location where you want to install Waveset. This could be a staging location or a specific folder. Enter the location (or click Browse to locate it), and then click Next.
If the directory you enter does not exist, Waveset prompts for confirmation, and then creates the directory.
Click Next to begin installation.
After installing the files, Waveset displays the Launch Setup panel.
Before you continue, if you plan to use a database, you may need to copy one or more files to the idm\WEB-INF\lib directory. For example, you may need to place into idm/WEB-INF/lib a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. When finished, click Launch Setup to launch the Setup Wizard and continue with setup steps. If you click Launch Setup before copying your database files, setup will not proceed correctly. If this happens, quit the installation program, and then use the lh setup command to restart the setup portion of the installation process.
Click Next on the Setup Wizard panel.
The installer displays the Locate the Repository panel.
Select a database from the list provided. Depending on your selection, setup prompts for additional setup information.
See Appendix C, Database Reference, for selections and setup instructions.
Click Next.
The Continue Waveset Demo Setup? panel appears.
If this is a non-demo installation click No, I will configure Waveset myself.
Otherwise, if appropriate, click Yes, I would like to continue setting up a demonstration environment. This option allows you to quickly configure users and enter environment and server information.
Enter the following personal information:
First name
Last name
Email address
This personal information is used to create the Approver user (with configurator privileges.)
Enter the following Approver information:
Approver name
Approver password
Click Next.
Select the Server Type from the list.
Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.
If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
Click Next.
The installer displays the Import Save Configuration panel.
Click Execute to perform all the listed functions. If desired, click Hide Details.
When all functions complete, click Done in the setup panel.
If the application server is installed on a UNIX machine, change directories to the $WSHOME/bin directory and run the following command to allow the scripts in this directory to be executed.
chmod -R +x * |
When installation completes, the installer displays the Installation Summary panel. For detailed information about the installation, click Details.
Not all messages may not be displayed here. View the log file (identified in details) for more information.
When finished, click Close to exit the installer.
After completing installation, continue by optionally installing the Waveset Gateway.
Open a command prompt, then change to the staging directory where you installed the Waveset files. (This is the directory you specified in Step 1: Install the Waveset Software.)
Create a .war file with the Waveset files by using the jar.exe (on Windows) or jar (on UNIX) command:
c:\java1.5\bin\jar.exe cvf ..\idm.war * /usr/bin/jar cvf ../idm.war *
Launch your application server and log in to the Java System Application Server Admin Console.
Navigate to and expand the Applications folder in the left panel.
Click the Web Applications folder.
Click Deploy in the right panel.
Enter the file path for the idm.war file, and then click Next.
When prompted, set the Application Name to idm. Set the Context Root to /idm, and then click Finish.
If you are deploying on Platform Edition 9, perform the following steps to ensure that you can create resources in Waveset.
Do NOT restart the application server. Continue to Step 3: Edit the server.policy File on the Application Server.
Waveset must be given permissions to perform certain actions.
Add the following lines to the server.policy file for the domain in which Waveset is installed (located in ApplicationServerHome/domains/domainName/config). Note that the ${waveset.home} variable must be expanded in the server.policy file.
grant { permission java.lang.RuntimePermission "accessClassInPackage.sun.io"; permission java.lang.RuntimePermission "getClassLoader"; permission java.lang.RuntimePermission "createClassLoader"; permission java.lang.RuntimePermission "accessDeclaredMembers"; permission com.waveset.repository.test.testConcurrentLocking "read"; permission java.net.SocketPermission "*", "connect,resolve"; permission java.io.FilePermission "*", "read"; permission java.util.PropertyPermission "*", "read,write"; }; grant codeBase "file:${waveset.home}/-" { permission java.util.PropertyPermission "waveset.home", "read,write"; permission java.util.PropertyPermission "security.provider", "read,write"; permission java.io.FilePermission "${waveset.home}${/} *", "read,write,execute"; permission java.io.FilePermission "${waveset.home}/help/index/-", "read,write,execute,delete"; permission java.io.FilePermission "$(java.io.tmpdir)$(/)*", "read,write,delete"; permission java.util.PropertyPermission "*", "read,write"; permission java.lang.RuntimePermission "accessClassInPackage.sun.io"; permission java.net.SocketPermission "*", "connect,resolve"; permission javax.management.MBeanServerPermission "*"; permission javax.management.MBeanPermission "*", "*"; permission javax.management.MBeanTrustPermission "*"; }; |
If you want to deploy Waveset Service Provider, add the following permissions to the above server.policy file entries.
grant { permission java.lang.RuntimePermission "shutdownHooks"; permission java.io.FilePermission "${waveset.home}/WEB-INF/spe/config/spe.tld", "read"; }; |
If you fail to update the old server.policy file with the above, and try to use the search engine, lock files may be created in the index directory that cannot be removed by the container. This always causes queries to hang, even if the server.policy file is subsequently updated.
For example, the contents of the help/index/docs directory should contain these five files:
AL MF p1.dict p1.fields p1.post |
In addition to the above, there may be two lock files:
AL.lock MF.lock |
These must be deleted manually. Once these are removed (and the server.policy file updated correctly), search queries will work as expected.
If you want to run with trace set to write to a file, you will need to add the following additional permissions to the server.policy file.
grant { permission java.io.FilePermission "/var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/ idm/config/trace1.log", "read,write"; permission java.io.FilePermission "$(java.io.tmpdir)$(/)*", "read,write,delete"; permission java.util.PropertyPermission "trace.file", "read"; permission java.util.PropertyPermission "trace.destination", "read"; permission java.util.PropertyPermission "trace.enabled", "read"; }; |
where FilePermission is the actual path of the trace file. Adjust the path to the output file as needed.
Restart the application server.
To verify setup, log in to Waveset. You can do this within the Admin Console by clicking the Launch button on the “idm” line of the Web Applications folder.
If your IT environment has Windows Active Directory, Novell NetWare, Domino, Remedy, or RSA ACE/Server resources, you should install the Waveset Gateway.
If your IT environment has Windows Active Directory domains, you should also install PasswordSync. The Waveset PasswordSync feature keeps user password changes made on Windows Active Directory domains synchronized with other resources defined in Waveset.
See Part III, Installing Optional Components for installation information.
Follow these steps to install Waveset on the Apache Tomcat application server.
If you are installing multiple instances of Waveset on a single application server, change the waveset.serverId system property to a unique name for each Waveset instance. See Setting the waveset.serverId System Property for more information.
You may install the software using one of two methods:
Using the installer Graphic User Interface
Run the install.bat (for Windows) or install (for UNIX) command to launch the installation process.
If you copy the files from the installation media to your own location, note that the idm.war and install.class files must be in the same directory.
The installer displays the Welcome panel.
Using the nodisplay option (UNIX only)
Change to the directory where the Waveset software is located. Enter the following command to activate the installer in nodisplay mode:
install -nodisplay
The installer displays the Welcome text. The installer then presents a list of questions to gather installation information in the same order as the Graphic User Interface installer in these procedures.
If no display is present, the installer defaults to the nodisplay option. The DISPLAY environment variable must be set to a valid X server or the installation may fail.
Click Next.
The Install or Upgrade? panel opens.
Leave the New Installation option selected, and then click Next.
The installer displays the Select Installation Directory panel.
Replace the displayed directory location with the location where you want to install Waveset. This could be a staging location or a specific folder. Enter the location (or click Browse to locate it), and then click Next.
Unless you plan to create a new context (virtual directory) in Tomcat’s server.xml directory, Oracle recommends installing to %TOMCAT_HOME%/webapps/idm.
If the directory you enter does not exist, the installer prompts for confirmation, and then creates the directory.
Click Next to begin installation.
After installing files, the installer displays the Launch Setup panel.
Add the Java mail.jar, activation.jar, and jms.jar files to the $WSHOME/WEB-INF/lib directory (UNIX), or the %WSHOME%\WEB-INF\lib directory (Windows). These files can be found at:
http://java.sun.com/products/javamail
http://java.sun.com/javase/technologies/desktop/javabeans/glasgow/jaf.html
http://www.oracle.com/technetwork/java/index-jsp-142945.html
To get the latest jms.jar file, download and install Sun GlassFish Message Queue. The jms.jar file is located in the MessageQueue/lib folder in the base Message Queue directory.
Before you continue, if you plan to use a database, you may need to copy one or more files to the idm/WEB-INF/lib directory. For example, you may need to place into idm/WEB-INF/lib a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix C, Database Reference.
When finished, click Launch Setup to launch the Setup Wizard and continue with setup steps. If you click Launch Setup before copying your database files, setup will not proceed correctly. If this happens, uninstall Waveset and repeat these installation steps.
Click Next on the Setup Wizard panel.
The product displays the Locate the Repository panel.
Select a database from the list provided. Depending on your selection, setup prompts for additional setup information.
See Appendix C, Database Reference, for selections and setup instructions.
Click Next.
The Continue Waveset Demo Setup? panel appears.
If this is a non-demo installation, click No, I will configure Waveset myself. Go to Step 1: Install the Waveset Software.
If appropriate, click Yes, I would like to continue setting up a demonstration environment.
This allows you to quickly configure users and enter environment and server information.
Enter the following personal information:
First name
Last name
Email address
This personal information is used to create the Approver user (with configurator privileges.)
Enter the following Approver information:
Approver name
Approver password
Click Next.
Select the Server Type from the list.
Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.
If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
Click Next.
The installer displays the Import Save Configuration panel.
Click Execute to perform all the listed functions. If desired, click Hide Details.
When all functions complete, click Done in the setup panel.
If the application server is installed on a UNIX machine, change directories to the $WSHOME/bin directory and run the following command to allow the scripts in this directory to be executed.
chmod -R +x * |
When installation completes, the installer displays the Installation Summary panel. For detailed information about the installation, click Details.
Some messages may not be displayed here. View the log file (identified in details) for more information.
When finished, click Close to exit the installer.
If you are installing multiple instances of Waveset on a single application server, change the waveset.serverId system property to a unique name for each Waveset instance. You do not need to update the waveset.serverId property otherwise.
By default, the waveset.serverId property is set to the name of the machine the application server is installed on.
Log on to the Administrator user interface. See To Start Waveset and Log in to the User Interface for instructions.
In the menu click Configure > Servers.
Verify that the host names that you configured for your instances appear and are listed as active.
If your IT environment has Windows Active Directory, Novell NetWare, Domino, Remedy, or RSA ACE/Server resources, you should install the Waveset Gateway.
If your IT environment has Windows Active Directory domains, you should also install PasswordSync. The Waveset PasswordSync feature keeps user password changes made on Windows Active Directory domains synchronized with other resources defined in Waveset.
See Part III, Installing Optional Components for installation information.
Follow these steps to install Waveset on the BEA WebLogic application server.
Select the domain that will be referenced when installing the software.
Set the environment variables JAVA_HOME and WSHOME:
set JAVA_HOME=/PathTo/java
set WSHOME=Path To IDMDirectory
Make sure the value of the WSHOME environment variable does NOT contain the following:
Quotation marks (“ ”)
A slash or backslash at the end of the path (/ or \)
Do not use quotation marks, even if the path to the application deployment directory contains spaces.
If using at least WebLogic 9.1, add the Java mail.jar and activation.jar files to the $WSHOME/WEB-INF/lib directory (UNIX), or the %WSHOME%\WEB-INF\lib directory (Windows). These files can be found at:
http://java.sun.com/products/javamail
http://java.sun.com/javase/technologies/desktop/javabeans/glasgow/jaf.html
If you are installing multiple instances of Waveset on a single application server, change the waveset.serverId system property to a unique name for each Waveset instance. By default, the waveset.serverId Java system property is the name of the machine the application server is installed on. To set this property to another value, add the following command to the startup script for your application server.
-Dwaveset.serverId=Name
You may install the software using one of two methods:
Using the installer Graphic User Interface
Run the install.bat (for Windows) or install (for UNIX) command to launch the installation process.
If you copy the files from the installation media to your own location, note that the idm.war and install.class files must be in the same directory.
The installer displays the Welcome panel.
Using the nodisplay option (UNIX only)
On UNIX systems, change directory to the Waveset software location. Enter the following command to activate the installer in nodisplay mode:
install -nodisplay
The installer displays the Welcome text. The installer then presents a list of questions to gather installation information in the same order as the Graphic User Interface installer in these procedures.
If no display is present, the installer defaults to the nodisplay option. The DISPLAY environment variable must be set to a valid X server or the installation may fail.
Click Next. The installer displays the Install or Upgrade? panel.
Leave the New Installation option selected, and then click Next.
The installer displays the Select Installation Directory panel.
Replace the displayed directory location with the location where you want to install Waveset. This could be a staging location or a specific folder. Enter the location (or click Browse to locate it), and then click Next.
If the directory you enter does not exist, the installer prompts for confirmation, and then creates the directory.
The WebLogic Web application home directory is ServerHome/user_projects/domains/DomainName/autodeploy
Click Next to begin installation.
After installing the files, the installer displays the Launch Setup panel.
Before you continue, if you plan to use a database, you may need to copy one or more files to the idm/WEB-INF/lib directory. For example, you may need to place into idm/WEB-INF/lib a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. When finished, click Launch Setup to launch the Setup Wizard and continue with setup steps. If you click Launch Setup before copying your database files, setup will not proceed correctly. If this happens, quit the installation program, and then use the lh setup command to restart the setup portion of the installation process.
Click Next on the Setup Wizard panel.
The installer displays the Locate the Repository panel.
Select a database from the list provided. Depending on your selection, setup prompts for additional setup information.
See Appendix C, Database Reference, for selections and setup instructions.
Click Next.
The Continue Waveset Demo Setup? panel appears.
If this is a non-demo installation click No, I will configure Waveset myself.
Otherwise, if appropriate, click Yes, I would like to continue setting up a demonstration environment. This option allows you to quickly configure users and enter environment and server information.
Enter the following personal information:
First name
Last name
Email address
This personal information is used to create the Approver user (with configurator privileges.)
Enter the following Approver information:
Approver name
Approver password
Click Next.
Select the Server Type from the list.
Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.
If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
Click Next.
The installer displays the Import Save Configuration panel.
Click Execute to perform all the listed functions. If desired, click Hide Details.
When all functions complete, click Done in the setup panel.
If the application server is installed on a UNIX machine, change directories to the $WSHOME/bin directory and run the following command to allow the scripts in this directory to be executed.
chmod -R +x * |
Remove the Cryptix JAR files (cryptix-jce-api.jar and cryptix-jce-provider.jar) from the $WSHOME/WEB-INF/lib directory (UNIX), or the %WSHOME%\WEB-INF\lib directory (Windows).
The Cryptix JAR files are no longer included and no longer supported. You need to remove them if you haven’t already. If you have customized your Waveset.properties file, please make sure that security.jce.workaround property is set to false or removed. An exception will be thrown if this property is set to true because the intention of this property will not be fulfilled.
When installation completes, the installer displays the Installation Summary panel. For detailed information about the installation, click Details.
Not all messages may not be displayed here. View the log file (identified in details) for more information.
When finished, click Close to exit the installer.
After successfully completing, the installer installation, continue setup by configuring the WebLogic server.
By default, WebLogic automatically deploys Waveset from the applications or autodeploy directory. Use the WebLogic Console to deploy Waveset if automatic deployment is not enabled.
If you are using Internet Information Server (IIS) as your Web server, you must add index.html to the list of Default Documents (under Properties) on the Waveset virtual directory in IIS. Otherwise, the Waveset main page will not resolve correctly when accessing the Waveset server.
If you are integrating Waveset with Oracle Identity Analytics (previously Sun Role Manager), or if you are using the SAP Web Services adapter, you need to install the Metro libraries. Metro is a web service stack that you can download from Java.net.
Prior to installing the Metro libraries, remove all saaj directories from webservices-rt.jar.
Download Metro 2.0 and expand the zip file:
Install the Metro libraries into the Waveset WEB-INF/lib directory.
If your IT environment has Windows Active Directory, Novell NetWare, Domino, Remedy, or RSA ACE/Server resources, you should install the Waveset Gateway.
If your IT environment has Windows Active Directory domains, you should also install PasswordSync. The Waveset PasswordSync feature keeps user password changes made on Windows Active Directory domains synchronized with other resources defined in Waveset.
See Part III, Installing Optional Components for installation information.
Follow these steps to install Waveset on the IBM WebSphere Application Server.
Use the following procedure to prepare the application server for Waveset:
You should have a WebSphere application server and servlet engine installed.
Create a staging directory and name it idm_staging.
Copy the idm.war file from the base directory of the installation media to the idm_staging directory.
Unjar the idm.war file in the idm_staging directory:
jar -xvf idm.war
Set the environment variables JAVA_HOME and WSHOME. For example, in Windows do the following:
set JAVA_HOME=c:\Program Files\WebSphere\AppServer\java
set WSHOME=Path To IDMStaging Directory
Make sure the value of the WSHOME environment variable does NOT contain the following:
Quotation marks (" ")
A slash or backslash at the end of the path (/ or \)
Do not use quotation marks, even if the path to the application deployment directory contains spaces.
If you plan to use a database, you may need to copy one or more files to the idm\WEB-INF\lib directory. To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. When finished, launch setup to continue with installation.
If you launch setup before copying your database files, setup will not proceed correctly. Copy the files, and then use the lh setup command to restart the setup portion of the installation process.
If you plan to use the Waveset Service Provider feature and you are using the IBM 1.5 JDK (or later), set the following properties:
In the was-install/java/jre/lib directory, rename the jaxb.properties.sample to jax.properties and uncomment these two lines:
javax.xml.parsers,SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
Save the file and restart the application server.
If you are installing multiple instances of Waveset on a single application server, change the waveset.serverId system property to a unique name for each Waveset instance. By default, the waveset.serverId Java system property is the name of the machine the application server is installed on. To set this property to another value, add the following command to the startup script for your application server.
-Dwaveset.serverId=Name
You may install the software using one of two methods:
Using the installer Graphic User Interface
Run the install.bat (for Windows) or install (for UNIX) command to launch the installation process.
If you copy the files from the installation media to your own location, note that the idm.war and install.class files must be in the same directory.
The installer displays the Welcome panel.
Using the nodisplay option (UNIX only)
Change directory to the Waveset software location. Enter the following command to activate the installer in nodisplay mode:
install -nodisplay
The installer displays the Welcome text. The installer then presents a list of questions to gather installation information in the same order as the Graphic User Interface installer in these procedures.
If no display is present, the installer defaults to the nodisplay option. The DISPLAY environment variable must be set to a valid X server or the installation may fail.
Click Next to display the Install or Upgrade? panel.
Leave the New Installation option selected, and then click Next.
The installer displays the Select Installation Directory panel.
Replace the displayed directory location with the location where you want to install Waveset. This could be a staging location or a specific folder. Enter the location (or click Browse to locate it), and then click Next.
Click Next to begin installation.
After installing files, the installer displays the Launch Setup panel.
Select a database from the list provided. Depending on your selection, setup prompts for additional setup information.
Before you continue, if you plan to use a database, you may need to copy one or more files to the idm/WEB-INF/lib directory. For example, you may need to place a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. If you are planning to use a Data Source as your repository location, see the special instructions in Appendix D, Configuring Data Sources for Waveset.
When finished, click Launch Setup to launch the Setup Wizard and continue with setup steps. If you click Launch Setup before copying your database files, setup will not proceed correctly. If this happens, quit the installation program, and then use the lh setup command to restart the setup portion of the installation process.
Click Next on the Setup Wizard panel.
The product displays the Locate the Repository panel.
Select a database from the list of displayed options.
Depending on your selection, setup prompts for additional setup information.
See Appendix C, Database Reference, for selections and setup instructions.
Click Next.
The Continue Waveset Demo Setup? panel appears.
If this is a non-demo installation, click No, I will configure Waveset myself and go to Step 3: Deploy the Application.
Otherwise, if appropriate, click Yes, I would like to continue setting up a demonstration environment. This option allows you to quickly configure users and enter environment and server information.
Enter the following personal information:
First name
Last name
Email address
This personal information is used to create the Approver user (with configurator privileges).
Enter the following Approver information:
Approver name
Approver password
Click Next.
Select the Server Type from the list.
Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.
If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
Click Next.
The installer displays the Import Save Configuration panel.
Click Execute to perform all the listed functions. If desired, click Hide Details.
When all functions complete, click Done in the setup panel.
If the application server is installed on a UNIX machine, change directories to the $WSHOME/bin directory and run the following command to allow the scripts in this directory to be executed.
chmod -R +x * |
The following procedure uses the Integrated Solutions Console, Version 6.1. The configuration procedure may vary for other versions of the Integrated Solutions Console.
Delete the following files, if they exist:
WEB-INF/lib/log.jar
WEB-INF/lib/j2ee.jar
WEB-INF/lib/ldap.jar
Create a .war file from WSHOME:
jar -cvf idm.war *
Start the application server. You must use WebSphere’s script to do this. For example, if WebSphere’s binary files are installed in c:\Program Files\WebSphere\AppServer\bin and the application server is named server1:
cd c:\Program Files\WebSphere\AppServer\bin startServer.bat server1 |
Start the WebSphere Integrated Solutions Console, and then select Applications—>Install New Application.
The Preparing for the application installation panel displays.
Select the Generate Default Bindings option. (Use the default selections for Override and Virtual Host.) Click Next.
Accept the was.policy file that is displayed under the heading Application Security Warnings. Scroll down to the bottom of this file and click the Continue button.
Configure the Step 1: Select installation options page as needed.
If you want to install the application to a different location than WebSphere’s default location, enter the path to install the application in the Directory to Install Application field. For example:
c:\Program Files\WebSphere\AppServer\installedApps\Hostname
Make sure the Distribute Application and Use Binary Configuration options are selected.
Make sure that the Create Mbeans for Resources and Deploy Enterprise Beans options are not selected.
Enter the name of the application in the Application Name field (the default is idm).
If desired, select the Enable class reloading option.
Click Next after configuring this dialog.
Make sure the Step 2: Map modules to servers panel displays a line for the current release of Waveset and that it maps to the appropriate server. Click Step 6: Map virtual hosts for Web modules.
Make sure the Step 6: Map virtual hosts for Web modules panel displays a line for the current release of Waveset and that it maps to the appropriate virtual host, and then click Step 8: Summary.
Review the summary of options, then click Finish.
After Waveset has been installed, click Save to Master Configuration to save the configuration.
Click Save, and then wait for the page to clear.
Stop the Waveset application.
Add the following line to your WAS_ROOT/profiles/ProfileName/installedApps/nodename/EnterpriseAppName/idm.war/WEB-INF/ibm-web-ext.xmi file
<jspAttributes xmi:id="JSPAttribute_1" name="jdkSourceLevel" value="15"/> |
This line causes the application server to compile JSP files in Java 5.
Restart Waveset.
If your IT environment has Windows Active Directory, Novell NetWare, Domino, Remedy, or RSA ACE/Server resources, you should install the Waveset Gateway.
If your IT environment has Windows Active Directory domains, you should also install PasswordSync. The Waveset PasswordSync feature keeps user password changes made on Windows Active Directory domains synchronized with other resources defined in Waveset.
See Part III, Installing Optional Components for installation information.
Follow these steps to install Waveset on the JBoss application server:
If you are installing multiple instances of Waveset on a single application server, change the waveset.serverId system property to a unique name for each Waveset instance. By default, the waveset.serverId Java system property is the name of the machine the application server is installed on. To set this property to another value, add the following command to the startup script for your application server.
-Dwaveset.serverId=Name
Set the environment variables JAVA_HOME and WSHOME:
set JAVA_HOME=/PathTo/java set WSHOME=Path To IDM Directory
Make sure the value of the WSHOME environment variable does NOT contain the following:
Quotation marks (" ")
A slash or backslash at the end of the path (/ or \)
Do not use quotation marks, even if the path to the application deployment directory contains spaces.
You may install the software using one of two methods:
Using the installer Graphic User Interface
Run the install.bat (for Windows) or install (for UNIX) command to launch the installation process.
The installer displays the Welcome panel.
Using the nodisplay option (UNIX only)
Change directory to the Waveset software location. Enter the following command to activate the installer in nodisplay mode:
install -nodisplay
The installer displays the Welcome text. The installer then presents a list of questions to gather installation information in the same order as the Graphic User Interface installer in these procedures.
If no display is present, the installer defaults to the nodisplay option. The DISPLAY environment variable must be set to a valid X server or the installation may fail.
Click Next to display the Install or Upgrade? panel.
Leave the New Installation option selected, and then click Next.
The installer displays the Select Installation Directory panel.
Replace the displayed directory location with a staging directory. Enter the location (or click Browse to locate it), and then click Next.
If the directory you enter does not exist, the installer prompts for confirmation, and then creates the directory.
Click Next to begin installation.
After installing files, the installer displays the Launch Setup panel.
Add the Java mail.jar and activation.jar files to the $WSHOME/WEB-INF/lib directory (UNIX), or the %WSHOME%\WEB-INF\lib directory (Windows). These files can be found at:
http://java.sun.com/products/javamail
http://java.sun.com/javase/technologies/desktop/javabeans/glasgow/jaf.html
Before you continue, if you plan to use a database, you may need to copy one or more files to the idm\WEB-INF\lib directory. For example, you may need to place into idm/WEB-INF/lib a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. If you are planning to use a Data Source as your repository location, see the special instructions in Appendix D, Configuring Data Sources for Waveset.
When finished, click Launch Setup to launch the Setup Wizard and continue with setup steps. If you click Launch Setup before copying your database files, setup will not proceed correctly. If this happens, quit the installation program, and then use the lh setup command to restart the setup portion of the installation process.
Click Next on the Setup Wizard panel.
The product displays the Locate the Repository panel.
Select a database from the list provided. Depending on your selection, setup prompts for additional setup information.
See Appendix C, Database Reference, for selections and setup instructions.
Click Next.
The Continue Waveset Demo Setup? panel appears.
If this is a non-demo installation, click No, I will configure Waveset myself. Go to Step 2: Install Optional Components.
Otherwise, if appropriate, click Yes, I would like to continue setting up a demonstration environment. This option allows you to quickly configure users and enter environment and server information.
Enter the following personal information:
First name
Last name
Email address
This personal information is used to create the Approver user (with configurator privileges.)
Enter the following Approver information:
Approver name
Approver password
Click Next.
Select the Server Type from the list.
Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.
If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
Click Next.
The installer displays the Import Save Configuration panel.
Click Execute to perform all the listed functions. If desired, click Hide Details.
When all functions complete, click Done in the setup panel.
When installation completes, the installer displays the Installation Summary panel. For detailed information about the installation, click Details.
Not all messages may not be displayed here. View the log file (identified in details) for more information.
When finished, click Close to exit the installer.
Remove the j2ee.jar file from WEB-INF\lib.
Do one of the following:
Remove (or comment out) WarClassLoaderDeployer from the following file:
jboss/server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml
Add WEB-INF/jboss-classloading.xml to the WAR. The jboss-classloading.xml file should contain the following XML:
<?xml version="1.0" encoding="UTF-8"?> <classloading xmlns="urn:jboss:classloading:1.0" name="idm.war" domain="DefaultDomain" export-all="NON_EMPTY" import-all="true"> </classloading>
Create a .war file from WSHOME:
jar -cvf idm.war *
Copy the idm.war file to the JBoss deploy directory. (For example, InstallDir\server\default\deploy)
If the application server is installed on a UNIX machine, change directories to the $WSHOME/bin directory and run the following command to allow the scripts in this directory to be executed.
chmod -R +x * |
If your IT environment has Windows Active Directory, Novell NetWare, Domino, Remedy, or RSA ACE/Server resources, you should install the Waveset Gateway.
If your IT environment has Windows Active Directory domains, you should also install PasswordSync. The Waveset PasswordSync feature keeps user password changes made on Windows Active Directory domains synchronized with other resources defined in Waveset.
See Part III, Installing Optional Components for installation information.
Follow these steps to install Waveset on Oracle Application Server 10g Release 3.
If you are installing multiple instances of Waveset on a single application server, change the waveset.serverId system property to a unique name for each Waveset instance. By default, the waveset.serverId Java system property is the name of the machine the application server is installed on. To set this property to another value, add the following command to the startup script for your application server.
-Dwaveset.serverId=Name
You may install the software using one of two methods:
Using the installer Graphic User Interface
Run the install.bat (for Windows) or install (for UNIX) command to launch the installation process.
If you copy the files from the installation media to your own location, note that the idm.war and install.class files must be in the same directory.
The installer displays the Welcome panel.
Using the nodisplay option (UNIX only)
On UNIX systems, change directory to the software location. Enter the following command to activate the installer in nodisplay mode:
install -nodisplay
The installer displays the Welcome text. Click Next. The installer then presents a series of questions to gather installation information in the same order as the Graphic User Interface installer in these procedures.
If no display is present, the installer defaults to the nodisplay option. The DISPLAY environment variable must be set to a valid X server or the installation may fail.
Click Next. The installer displays the Software License Agreement page. Read the agreement, then if you accept, click the Yes (Accept License) button. The installer displays the Install or Upgrade? panel.
Leave the New Installation option selected, and then click Next.
The installer displays the Select Installation Directory panel.
Replace the displayed directory location with the location where you want to install Waveset. This could be a staging location or a specific folder. Enter the location (or click Browse to locate it), and then click Next.
If the directory you enter does not exist, Waveset prompts for confirmation, and then creates the directory.
On the Ready to Install page, click Install Now to begin installation.
After installing the files, Waveset displays the Launch Setup panel.
Before you continue, if you plan to use a database, you may need to copy one or more files to the idm\WEB-INF\lib directory. For example, you may need to place into idm/WEB-INF/lib a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. When finished, click Launch Setup to launch the Setup Wizard and continue with setup steps.
A pop-up window will ask if you have copied all JAR files. If you have, click Yes, Continue.
If you click Launch Setup before copying your database files, setup will not proceed correctly. If this happens, quit the installation program, and then use the lh setup command to restart the setup portion of the installation process.
Click Next on the Setup Wizard panel.
The installer displays the Locate the Repository panel.
Select a database from the list provided. Depending on your selection, setup prompts for additional setup information.
See Appendix C, Database Reference, for selections and setup instructions.
Click Next.
The Continue Waveset Demo Setup? panel appears.
If this is a non-demo installation, click No, I will configure Waveset myself.
Otherwise, if appropriate, click Yes, I would like to continue setting up a demonstration environment. This allows you to quickly configure users and enter environment and server information.
Enter the following personal information:
First name
Last name
Email address
This personal information is used to create the Approver user (with configurator privileges.)
Enter the following Approver information:
Approver name
Approver password
Click Next.
Select the Server Type from the list.
Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.
If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
Click Next.
The installer displays the Import Save Configuration panel.
Click Execute to perform all the listed functions. If desired, click Hide Details.
When all functions complete, click Done in the setup panel.
If the application server is installed on a UNIX machine, change directories to the $WSHOME/bin directory and run the following command to allow the scripts in this directory to be executed.
chmod -R +x * |
When installation completes, the installer displays the Installation Summary panel. For detailed information about the installation, click Details.
Not all messages may not be displayed here. View the log file (identified in details) for more information.
When finished, click Close to exit the installer.
After completing installation, continue by optionally installing the Waveset Gateway.
Open a command prompt, then change to the staging directory where you installed the Waveset files. (This is the directory you specified in Step 1: Install the Waveset Software in the procedure Step 1: Install the Waveset Software)
Create a .war file with the Waveset files by using the jar.exe (on Windows) or jar (on UNIX) command:
c:\java1.5\bin\jar.exe cvf ..\idm.war * /usr/bin/jar cvf ../idm.war *
Launch your application server and log in to the Oracle Application Server Control Console.
Navigate to the Cluster Topology page. Select View by Application Servers. Then select the OC4J name link.
On the OC4J Home page, click the Applications link.
Click the Deploy... button.
In the Archive text box, enter the file path for the idm.war file.
In the Deployment Plan section, select Automatically create a new deployment plan. Then click Next.
When the Deploy: Application Attributes page displays, set the Application Name to idm. Set the Context Root to /idm, and then click Next.
Set any Deployment Settings as necessary for your site.
Click the Deploy button. The console displays a confirmation page when Waveset has been deployed.
If your IT environment has Windows Active Directory, Novell NetWare, Domino, Remedy, or RSA ACE/Server resources, you should install the Waveset Gateway.
If your IT environment has Windows Active Directory domains, you should also install PasswordSync. The Waveset PasswordSync feature keeps user password changes made on Windows Active Directory domains synchronized with other resources defined in Waveset.
See Part III, Installing Optional Components for installation information.