| Oracle® Health Sciences Empirica Signal Installation Guide Release 8.0.1.0.316 E73006-01 |
|
 Previous |
| Oracle® Health Sciences Empirica Signal Installation Guide Release 8.0.1.0.316 E73006-01 |
|
Previous |
This section describes how to do the following steps:
Install WebLogic.
Install Oracle ADF Runtime.
Install required database repositories
Perform additional setup tasks before installing the Empirica Signal software
You must perform these steps before installing the Empirica Signal application.
For information about the required versions of each component and the download location, see the System Requirements chapter in the Empirica Signal Release Notes.
|
Note: For any input, do not include trailing whitespace. Most text is case sensitive. Paths might vary depending on your environment. |
Prerequisites:
The user account you use for these steps must not be the root user.
The following steps describe the graphical mode for installing WebLogic. Therefore, you must set the DISPLAY environment variable before running the installer.
To install WebLogic:
Log in to the application server as the non-privileged user.
Using a tool such as the tar command, unzip /u01/stage/V29856-01.zip file to the /u01/stage directory. For example, use the following command:
$ cd /u01/stage/ $ mkdir weblogic $ cd weblogic $ unzip /u01/stage/V29856-01.zip
In a command shell, execute the following command:
$ java -jar wls1036_generic.jar
The Welcome page appears.
Click Next.
The Choose Middleware Home Directory page appears.
Select Create a new Middleware Home.
In the Middleware Home Directory field, browse to the Middleware directory, such as:
/u01/app/oracle/product/Middleware
Click Next.
The Register for Security Updates page appears.
To receive security updates, leave I wish to receive security updates selected, and type your e-mail address and password for My Oracle Support.
If you do not want to receive security updates, deselect I wish to receive security updates, and click Yes when prompted to confirm.
Click Next.
The Choose Products and Components page appears.
Select Custom, and click Next.
The Choose Products and Components page appears.
Deselect the following options:
WebLogic Server
Oracle Coherence
Select the following options:
Core Application Server
Administration Console
Configuration Wizard and Upgrade Framework
WebLogic JDBC Drivers
Click Next.
The JDK Selection page appears.
In the Local JDK list at the bottom of the page, deselect any selected options.
Click Browse, and select the JDK 1.7 path, such as the following path: /u01/app/oracle/java/jdk1.7.x_xx.
Click Next.
The Choose Product Installation Directories page appears.
Click Next.
The Installation Complete page appears.
Deselect Run Quickstart, and click Done.
Copy the following files from $WL_HOME/modules to $JAVA_HOME/jre/lib/endorsed, where WL_HOME is the WebLogic Server installation home directory. If the endorsed directory does not exist, create it.
javax.annotation_1.0.0.0_1-0.jar
javax.xml.bind_2.1.1.jar
javax.xml.ws_2.1.1.jar
Log in to the application server as the non-privileged user.
Using a tool such as the tar command, unzip /u01/V37382-01.zip file to the /u01/stage directory. For example, use the following command:
$ cd /u01/stage/ $ mkdir adf $ cd adf $ unzip /u01/stage/V37382-01.zip
In a command shell, type the following command:
$ cd disk1/install/linux64
Type the following command:
$ ./runInstaller
Information about the Oracle Universal Installer appears.
You are prompted to enter the JDK location.
Type the JDK directory. Replace the following directory with the path to your JDK, and change XX to your JDK version number:
/u01/app/oracle/java/jdk1.7.X_XX
The Welcome page appears.
Click Next.
The Install Software Updates page appears.
Select either Skip Software Updates or Search My Oracle Support for Updates.
If you selected Search My Oracle Support for Updates, type your My Oracle Support credentials. If an update is required, you are prompted to install it.
Click Next.
The Prerequisite Checks page appears.
Review the checks, and click Next.
The Specify Installation Location page appears.
Make sure the Oracle Middleware Home field points to the directory created in the WebLogic installation.
Click Next.
The Application Server page appears.
Click Next.
The Installation Summary page appears.
Click Install.
The Installation Progress page appears.
After the installation completes, click Next.
The Installation Complete page appears.
Click Finish.
Log in to the application server as the non-privileged user.
Using a tool such as the tar command, unzip /u01/V37394-01.zip file to the /u01/stage directory. For example, use the following command:
$ cd /u01/stage/ $ mkdir rcu $ cd rcu $ unzip /u01/stage/V37394-01.zip
In a command shell, type the following command:
$ ./rcuHome/bin/rcu &
The Welcome page appears.
Click Next.
The Create Repository page appears.
Click Next.
The Database Connection Details page appears.
Type the database information, including a user name with sysdba privileges, and click Next.
The Repository Creation Utility dialog box appears.
After the progress completes, click OK.
The Select Components page appears.
Expand Oracle AS Common Schemas, and select Metadata Services and Oracle Platform Security Services.
In the Create a new Prefix field, type a prefix, such as EMPIRICA.
Click Next.
The Repository Creation Utility - Checking Prerequisites dialog box appears.
Click OK.
The Schema Passwords page appears.
Specify the schema passwords, and click Next.
|
Note: Remember these passwords. |
The Map Tablespaces page appears.
Click Next.
The Repository Creation Utility - Confirmation dialog box appears.
Click OK.
The Repository Creation Utility - Creating Tablespaces dialog box appears.
Click OK.
The Summary page appears.
Click Create.
The Completion Summary page appears.
Click Close.
This section includes the following topics:
The Empirica Signal application requires a WebLogic domain that includes Enterprise Manager and is configured for Web Service security. You can either create a new WebLogic domain or extend an existing WebLogic domain. This procedure describes how to create a new WebLogic domain.
You must use the same user account that you used when you .
In a command shell, type the following command:
$ cd /u01/app/oracle/product/Middleware/wlserver_10.3/common/bin
Type the following command:
$ ./config.sh &
The Welcome page appears.
Select Create a new WebLogic domain, and click Next.
The Select Domain Source page appears.
Select Generate a domain configured automatically to support the following products, and select the following products:
Oracle Enterprise Manager - 11.1.1.0 [oracle_common]
Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]
Oracle JRF - 11.1.1.0 [oracle_common]
Click Next.
The Specify Domain Name and Location page appears.
Type a domain name, such as empirica, and click Next.
The Configure Administrator User Name and Password page appears.
Type a user name and password for WebLogic administration.
|
Note: Remember these credentials. You use them to administer the WebLogic instance. |
Click Next.
The Configure Server Start Mode and JDK page appears.
In the WebLogic Domain Startup Mode section, select Production Mode.
In the JDK Selection section, select Available JDKs, and select the 1.7.x_xx JDK that is specified in the system requirements in the Empirica Signal Release Notes.
Click Next.
The Configure JDBC Component Schema page appears.
In the table at the bottom, select the OWSM MDS schema.
Fill in the following fields:
From the Driver drop-down list, select the driver for either a service or instance connection.
For DBMS/Service, type the appropriate value for the driver you selected:
If the name of the driver contains the words for Instance connections, type the SID.
If the name of the driver contains the words for Service connections, type the service name.
For Schema Owner, type a value, such as EMPIRICA_MDS.
For Schema Password, type the password that you created when you created the schema in Installing RCU and creating repositories.
Click Next.
The Test JDBC Component Schema page appears.
Click Next.
The Select Optional Configuration page appears.
Select the following options:
Administration Server
Managed Servers, Clusters and Machines
Deployments and Servers
Click Next.
The Configure the Administration Server page appears.
Select SSL enabled, and for SSL listen port, type 7002.
Click Next.
The Configure Managed Servers page appears.
Click Add.
A row in the table becomes editable.
Select SSL enabled, and fill in the fields as follows:
Name—Type SignalServer
Listen address—Type the fully qualified name of the application server.
Listen port—Type 7003.
SSL listen port—Type 7004.
Click Next.
The Configure Clusters page appears.
Click Next.
The Configure Machines page appears.
Select the Unix Machine tab.
Click Add.
A row in the table becomes editable.
Fill in the fields as follows:
Name—Type SignalMachine.
Node manager listen address—Type the fully qualified name of the application server.
Node manager listen port—Type 5556, if the value is not already present.
Click Next.
The Assign Servers to Machines page appears.
In the right list of machines, select SignalMachine.
In the left list of servers, select SignalServer, and click the right arrow button.
The server is added to the machine.
Click Next.
The Target Deployments to Clusters or Servers page appears.
Assign deployments to the AdminServer:
In the list of target servers on the left, select AdminServer.
Deselect the FMW Welcome Page entry, and make sure all other entries are selected.
Assign deployments to the SignalServer:
In the list of target servers on the left, select SignalServer.
Deselect the FMW Welcome Page entry.
Select the following options, if they are not already selected, and make sure all other options are not selected:
wsil-wls
wsm-pm
Click Next.
The Target Services to Clusters or Servers page appears.
In the list of target servers on the left, select SignalServer.
In the list of services on the right, select the following services, if they are not already selected:
JRF Startup Class
JPS Startup Class
JDBC, as well as all of its child options.
Click Next.
The Configuration Summary page appears.
Click Create.
The Creating Domain page appears.
When progress reaches 100 percent, click Done.
The wizard closes.
Store your WebLogic administrator credentials so that you are not prompted for your credentials when you start WebLogic:
In the command shell, navigate to the AdminServer directory under the empirica domain. For example, navigate to the following location:
/u01/app/oracle/Middleware/user_projects/domains/empirica
If the following directory structure does not exist within the empirica directory, create it:
servers/AdminServer/security
|
Note: The directory names are case-sensitive. Capitalize the words as they are shown. |
Using a text editor, edit the boot.properties file in the security directory. This step creates the file, if it does not already exist.
Type the following lines in the file, providing the user name and password that you created when you created and configured the WebLogic domain. For more information, see Creating and configuring the WebLogic domain.
username=<weblogic_admin_user>
password=<weblogic_admin_password>
Save the file, and close the text editor.
Perform these steps as the non-privileged user on the application server.
Navigate to the $WL_HOME/server/bin directory, such as:
/u01/app/oracle/Middleware/wlserver_10.3/server/bin
Start the Node Manager by executing the following command:
$ ./startNodeManager.sh <listen_address> 5556
where <listen_address> is the value you entered in Creating and configuring the WebLogic domain.
After the console says <secure socket listener started on port 5556>, press Ctrl+C.
The Node Manager stops.
Navigate to the $WL_HOME/common/nodemanager directory, such as:
/u01/app/oracle/Middleware/wlserver_10.3/common/nodemanager
Review the nodemanager.properties file:
Edit the nodemanager.properties file. For example:
$ vi nodemanager.properties
Set the values of the following properties to true:
SecureListener
|
Note: For a non-SSL environment, set this property to false. |
StopScriptEnabled
StartScriptEnabled
Save the file, and exit the vi editor.
Navigate to the WebLogic default domain bin directory, using a command such as the following:
$ cd /u01/app/oracle/Middleware/user_projects/domains/empirica/bin
Start WebLogic using the following command:
$ nohup ./startWebLogic.sh > /dev/null &
|
Note: Information messages might appear. You might need to press Enter to see the prompt. |
Navigate to $WL_HOME/server/bin directory, such as:
/u01/app/oracle/Middleware/wlserver_10.3/server/bin
Execute following command
$ nohup ./startNodeManager.sh &
Verify that the Node Manager can be reached:
In an internet browser, enter the URL for the WebLogic Administration Console, such as the following:
https://<servername>:7002/console
In the left pane, expand Environment, and select Machines.
The Summary of Machines page appears.
In the list of machines, select SignalMachine.
The Settings for SignalMachine page appears.
Select the Monitoring tab.
Confirm that the status is Reachable. If status is Inactive, the Node Manager is not running.
Start Managed Server using the Node Manager:
In an internet browser, enter the URL for the WebLogic Administration Console, such as the following::
https://<servername>:7002/console
In the left pane, expand Environment, and select Servers.
Select the Control tab.
Select SignalServer, and click Start.
Apply the JRF Template to the Managed Server:
Restart the SignalServer managed server:
In an internet browser, enter the URL for the WebLogic Administration Console, such as the following:
https://<servername>:7002/console
In the left pane, expand Environment, and select Servers.
The Summary of Servers page appears.
Select the Control tab.
From the list of servers, select the SignalServer.
From the Shutdown drop-down list, select Force Shutdown Now.
After the state of the SignalServer changes to Shutdown, select the check box for SignalServer in the table, and click Start.
To set up a data source in the WebLogic Administration Console for the credential store:
In an internet browser, enter the URL for the WebLogic Administration Console, such as the following:
https://<servername>:7002/console
In the left pane, expand Services, and select Data Sources.
In the upper-left corner of the page, in the Change Center section, click Lock & Edit.
In the right pane, click the New button, and from the drop-down list that appears, select Generic Data Sources.
The JDBC Data Source Properties page appears.
Type values for the following fields:
Name—For example, type Empirica Credential Store.
JNDI Name—For example, type jdbc/mds/opss.
Click Next.
The JDBC Data Source Properties page appears.
Click Next.
The Transaction Options page appears.
Click Next.
The Connection Properties page appears.
Fill in the following names:
Database Name—Type the SID.
Host Name
Port
Database User Name—For example, EMPIRICA_OPSS.
Password, Confirm Password—Type the password that you entered when you .
Click Next.
Click Next.
The Test Database Connection page appears.
At the top of the page, click Test Configuration.
A Connection Test Succeeded message appears.
Click Next.
The Select Targets page appears.
From the Servers list, select AdminServer and SignalServer.
Click Finish.
In the upper-left corner of the page, in the Change Center section, click Activate Changes.
A message appears, indicating that the changes have been activated. The Credential Store Data Source entry is created.
In an internet browser, enter the URL for the Oracle Enterprise Manager, such as the following:
In the left pane, expand WebLogic Domain, and select empirica.
In the right pane, expand the WebLogic Domain drop-down menu at the top of the page, and select Security > Security Provider Configuration.
The Security Provider Configuration page appears.
In the Security Stores area, click Change Store Type.
The Configure Security Stores page appears.
From the Store Type drop-down list, select Oracle Database.
Next to the Data Source JNDI Name field, click Select, select the Empirica Credential Store, and click OK.
In the Data Source Properties area, type the:
User name—Name of the database user name, such as EMPIRICA_OPSS.
Password, Confirm Password—Password for the schema that you created in Installing RCU and creating repositories.
In the Root DN field, type cn=root.
Select Create new domain.
In the Domain Name field, type empirica.
Click OK.
A message appears, indicating that the domain must be restarted.
Click Yes.
The domain restarts. A confirmation dialog box appears and displays the results.
Click Close.
The credential store is set up.
Stop and restart the WebLogic server.
In an internet browser, enter the URL for the WebLogic Administration Console, such as the following:
https://<servername>:7002/console
In the left pane, expand Environment, and select Servers.
The Summary of Servers page appears.
Select the Control tab.
From the list of servers, select the SignalServer.
From the Shutdown drop-down list, select Force Shutdown Now.
After the state of the SignalServer changes to Shutdown, select the check box for SignalServer in the table, and click Start.
The WebLogic server is configured by default to use a demo SSL certificate. This certificate is intended for demonstration purposes only. Do not use the demo SSL certificate for production environments.
Perform the following steps to configure WebLogic to use SSL for production use of the Empirica Signal application. For more information, see the following document:
http://docs.oracle.com/cd/E23943_01/web.1111/e13707/ssl.htm
Obtain an SSL certificate from a Certification Authority.
Using the WebLogic Administration Console, configure both AdminServer and SignalServer to use your SSL certificate. For more information, see the following document:
Configure the Node Manager to use your SSL certificate. For more information, see the following document:
http://docs.oracle.com/cd/E23943_01/doc.1111/e15483/node_manager.htm#CCHEBIHI
This section includes the following topics:
Resolution:
Try these steps in order, testing after each step to determine whether the issue is resolved.
Restart WebLogic using the following commands:
$ ./stopWebLogic.sh
$ nohup ./startWebLogic.sh > /dev/null &
In the WebLogic Administration Console, verify that the data source user name is set up as EMPIRICA_OPSS with the correct password. Test the connection.
In the Oracle Enterprise Manager, under System Policies, verify the codebase paths match the installation.
To check for specific permission errors, enable debugging, and examine error messages in the log file:
Open the WebLogic start script (startWebLogic.sh) in your domain directory, such as the following directory:
/u01/app/oracle/Middleware/user_projects/domains/empirica/bin
Add the following text below the # START WEBLOGIC entry in the file:
JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.security.debug=access,failure -Djps.auth.debug=true -Djps.auth.debug.verbose=true"
Restart WebLogic using the following commands:
$ ./stopWebLogic.sh
$ nohup ./startWebLogic.sh > /dev/null &
Examine the startWebLogic.sh output to see whether it contains the following permission error:
java.security.AccessControlException: access denied
If the error exists, look below the error at the code source, such as the following text:
CodeSource=file:/u01/app/oracle/product/Middleware/user_projects/domains/empirica/servers/AdminServer/stage/signal/signal/…
In Enterprise Manager, update the permission codebase paths in System Policies to reflect the missing permission.
Restart WebLogic using the following commands:
$ ./stopWebLogic.sh
$ nohup ./startWebLogic.sh > /dev/null &
After the permission issue is resolved, remove the debug options, and start WebLogic using the following commands:
$ ./stopWebLogic.sh
$ nohup ./startWebLogic.sh > /dev/null &
Resolution: In the Enterprise Manager, check that the OWSM user token policy, either SSL or non-SSL, is correctly added.
This issue occurs when the password for the EMPIRICA_OPSS account expires or changes, for example, due to password expiration policies.
Resolution:
You must register the new password in the following locations:
The bootstrap wallet file.
In a command shell, navigate to the directory for the bootstrap wallet file using a command such as:
$ cd /u01/app/oracle/Middleware/user-projects/domains/empirica/config/fmwconfig.
In a command shell, start WLST using a command such as:
$ /u01/app/oracle/Middleware/oracle_common/common/bin/wlst.sh
The following prompt appears:
wls:/offline>
Execute the following command:
modifyBootStrapCredential(jpsConfigFile='./jps-config.xml', username='<user>', password='<new password>')
where:
<user> is the name of the OPSS schema database account, such as EMPIRICA_OPSS.
<new password> is the new password of the OPSS schema database account.
To exit WLST, execute the exit() command.
The data source associated with the OPSS schema database account.
Open the WebLogic Administration Console.
Expand Services, and select Data Sources.
Select the Data Source entry.
If you followed the recommendations in Creating a data source for credential access, the data source is named Empirica Credential Store, and the JDNI name is jdbc/mds/opss.
Select the Configuration tab, and select the Connection Pool tab.
In the Change Center section on the left, click Lock & Edit.
Scroll to the Password and Confirm Password fields.
Type the account password in both fields, and click Save.
In the Change Center section on the left, click Activate Changes.
This issue occurs when the password for the EMPIRICA_MDS account expires or changes, for example, due to password expiration policies.
Perform the following steps to register the new password in the data source associated with the MDS schema database account.
Open the WebLogic Administration Console.
Expand Services, and select Data Sources.
Select the Data Source entry.
Select the mds-owsm data source.
Select the Configuration tab, and select the Connection Pool tab.
In the Change Center section on the left, click Lock & Edit.
Scroll to the Password and Confirm Password fields.
Type the account password in both fields, and click Save.
In the Change Center section on the left, click Activate Changes.
|
 Copyright © 2002, 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|