This chapter describes how to install Oracle Communications Order and Service Management (OSM) by using the graphical user interface (GUI) Installer. It also provides information about default Oracle WebLogic Server accounts, and modifying deployment parameters.
Before installing OSM, read the following chapters:
This section describes an interactive installation of OSM. The installation procedure applies to all supported platforms.
Note:
If you are localizing OSM, make a backup of your WebLogic Server configuration before running the OSM Installer. See OSM Developer's Guide for more information about localizing OSM. See Administering Oracle Fusion Middleware for backup and recovery recommendations for WebLogic Server.Note:
If you are re-using the installation directory or the operating system temporary directory from a previous installation, you might not be able to run the installer on a UNIX or Linux system. For information about how to resolve this issue, see "OSM Installer Issues for UNIX or Linux."To install OSM:
Download and unpack JBoss and GraphViz (optional) to a suitable location on the same machine on which you will install OSM. See Table 2-1, "OSM Required Software" for download links.
Tip:
If you intend to install more than one OSM instance on the same machine, it is a good idea to put these libraries in a location outside any OSM_home.Download the OSM software media pack for your operating system from the Oracle software delivery website, located at:
and save it to a temporary directory.
Unzip the OSM software media pack.
Ensure that the Oracle Database and Oracle WebLogic Server instances that you intend to use for OSM are running.
For a Linux system, ensure that you have installed all required software packages, including Software Development Workstation. For information about the available software packages, see the latest Oracle Linux Installation Guide.
On UNIX or Linux systems:
Verify that your DISPLAY environment variable is properly set.
Remove the ANT_HOME environment variable if it appears.
Remove any weblogic.jar file entries from the CLASSPATH variable.
Verify that the OSM UNIX or Linux user has read, write, and execute permissions for the /tmp/vfs_cache directory.
Note:
If you cannot use this directory, or the contents of the /tmp directory get purged periodically, you can change the location of the /vfs_cache directory by adding the -Djava.io.tmpdir=new_path argument to the OSM WebLogic Server startup scripts (where new_path is the new /vfs_cache location).Change to the temporary directory containing the installation executable file.
Run the following command:
chmod 500 InstallOS_name.bin
where OS_name is Linux, Sparc (Solaris), AIX, or HpuxItanium, depending on your system.
Run the OSM Installer by doing one of the following:
On Oracle Linux and Red Hat Enterprise Linux, run the following command:
InstallLinux.bin
On Oracle Solaris, run the following command:
InstallSparc.bin
On IBM AIX, run the following command:
InstallAix.bin
On HP-UX Itanium, run the following command:
InstallHpuxItanium.bin
On Windows, run the following command:
Install.exe
Table 6-1 gives troubleshooting information for error messages you may receive after executing the command.
Note:
If you are concerned that there is insufficient temporary disk space in your current temporary directory, specify the location of a different temporary directory for the OSM Installer to use during the installation.You can also specify a log file that logs all OSM Installer activity.
To specify a different temporary directory and specify a log file, use the following attributes when running the OSM Installer:
-is:tempdir temp_directory -is:log log_file.log
where temp_directory is the location for the temporary directory used by the OSM Installer and log_file is the log file name.
For example:
./InstallLinux.bin -is:tempdir /tmp/osm -is:log osmlog.log
Table 6-1 Troubleshooting OSM Installer Startup Errors
| Error | Solution | Operating System |
|---|---|---|
|
After running the InstallLinux.bin command: Setup.product.install, com.installshield.wizard.StandardWizardListener, err, could not initialize interface awt... |
Set the following environment variable and run the OSM Installer again: export AWT_TOOLKIT=MToolkit |
Oracle Linux or Enterprise Red Hat Linux |
|
After running the InstallSparc.bin command: UnsatisfiedLinkError: java: fatal: libXm.so.4: open failed: No such file or directory ... |
Set the following environment variable and run the OSM Installer again: export AWT_TOOLKIT=XToolkit |
Oracle Solaris |
|
After running the InstallSparc.bin command: Setup.product.install, com.installshield.wizard.StandardWizardListener, err, could not initialize interface awt... |
Set the following environment variable and run the OSM Installer again: export AWT_TOOLKIT=MToolkit |
Oracle Solaris |
|
After the Installer starts, on the Welcome screen: ERROR: null Installer log shows InstallShield errors. For example: [java.lang.NullPointerException]) at com.installshield.wizard.service.LocalImplementorProxy.invoke(Unknown Source) ... |
Delete the vpd.properties file located in the following directory and run the OSM Installer again: userHome/InstallShield/Universal/common/Gen1/_vpddb/ where userHome is your home directory. |
All |
The Welcome screen is displayed.
Review the pre-installation checklist and additional third-party component requirements.
Note:
The third-party components are required for the OSM Server and software development kit (SDK) components.Verify that the View third party readme check box is selected and click Next.
The Order and Service Management Third-party Component Information screen is displayed.
Review the readme contents for the third-party components, then click Next.
The Installation Directory screen is displayed.
Specify the installation directory for OSM by doing one of the following:
Accept the default path provided by the Installer.
Specify another location by entering a path name or click Browse to locate the directory.
Note:
If you are installing to the same directory as an existing OSM 7.0.x installation, the automation module in the SDK is not upgraded. Specify a new directory to ensure complete installation of the new OSM SDK.Click Next.
The Setup Type screen is displayed.
Select which of the components listed in Table 6-2 to install by doing one of the following:
Table 6-2 OSM Installation Components
| Component | Description |
|---|---|
|
Database Schema |
The database schemas required to support OSM |
|
Server |
The OSM server application |
|
SDK Tools |
The OSM SDK, which includes the OSM Javadocs, the XML Import/Export tool, and various other files in support of OSM development activities. |
|
SDK Samples |
Sample files for use with the SDK. Includes sample code and web service requests. This also includes silent installation template files to use if you want to run subsequent silent installations. For more information about silent installations, see "Performing a Silent Installation of OSM." |
To install everything except the SDK Samples (on Windows), or to install the Database Schema and Server (on UNIX or Linux), select Typical Installation and click Next.
To choose which components to install do the following:
Select Custom Installation and click Next.
Select the components to install and click Next.
The Installation Overview screen is displayed.
Review the upcoming stages of the installation, and click Next.
The Database Connection Information screen is displayed.
Specify the Oracle Database instance where the OSM database schema will be installed by entering the values supplied by your database administrator (DBA) in the following fields.
If you are installing an Oracle Real Application Clusters (Oracle RAC) database, specify connection information for the primary database instance. You will specify secondary database instances in a later step.
In the Host field, enter the IP address or DNS name of the host where the database listens for request. For an Oracle RAC database, enter the Single Client Access Name (SCAN).
In the Port field, enter the port where the database listens for requests.
In the Service Name field, enter the service name of the database. If the database is a pluggable database (PDB) within a container database (CDB), use the service name of the PDB. For example, the name of either the default database service or a service created specifically for OSM.
For an Oracle RAC database instance with a remote listener (SCAN listener), you must enter both service name and SID. For other types of database, or an Oracle RAC database instance with only local listeners, you can enter either a database service name or SID, but both fields cannot be empty.
Note:
If a service is configured for OSM, all WebLogic database transactions are executed against that service as expected. However, OSM jobs run by the Notification Engine are submitted to the database through the DBMS_JOB package and are not subject to any restrictions that may have been placed on the service.In the Instance SID field, enter the name (system identifier) of the database instance. If the database is a PDB within a CDB, use the system identifier of the CDB.
For an Oracle RAC database instance with a remote listener, you must specify the SID and the service name. Otherwise, the WebLogic data source will not be able to override server-side load balancing. See "Listener Considerations for Oracle RAC" for a discussion of listener functionality.
Click Next.
The Database Administrator Credential Information screen is displayed.
Enter the credentials supplied by your DBA in the following fields:
In the Database Admin Username field, enter the user name for the database administrator user.
In the Database Admin Password field, enter the password for the database administrator user.
Note:
If you choose to connect as the sys user and you have not set the O7_DICTIONARY_ACCESSIBILITY database parameter to TRUE, append as sysdba to the value in the User Name field.Click Next.
The Database Credential Information screen is displayed.
Do one of the following:
Select Use different passwords for these accounts to manually configure the OSM schema names and passwords:
In the Schema column, you can view the Core, Rule Engine, and Reporting schemas. These fields are read-only.
In the Username column, OSM generates ordermgmt, ordermgmt_rule, and ordermgmt_report as the default user name for the Core, Rule Engine, and Reporting schemas. Double-click on any default user name to edit the user name.
In the Password column, enter a password for each schema.
In the Password Confirmation column, enter the same password again.
Note:
If the Oracle accounts that you enter in the Username fields do not exist, new accounts with these names will be created for you during installation.Select Use same passwords for all accounts to use the same password for all OSM schemas.
In the Password field, enter a password.
In the Password Confirmation field, enter the password again.
Note:
If you edit the default schema user names in the Use different passwords for these accounts Username column, but specify the same password for all schemas using the Use same password for all accounts field, OSM uses the edited user names and applies the same password for each schema.The OSM Server uses the Core and Rule Engine credentials to connect to Oracle Database schemas. You can use Reporting credentials with the OSM Reporting Interface to generate reports (see OSM Reporting Interface Guide for more information).
Click Next.
Do one of the following:
If Order and Service Management Database Schema Not Found is displayed, click Next, which creates a new database.
If Order and Service Management Database Schema Found is displayed, and the existing database version is the same as the version to be installed, click Next.
If Order and Service Management Database Schema Found is displayed, and the existing database version is different from the version to be installed, you must upgrade the database.
Do the following to review a report analyzing the impact of upgrading:
On the schema status screen, click Analyze and click Next (the analysis can take a few minutes to run).
The Database Analysis Report screen is displayed.
On reviewing the report, either save the report and click Next, or click Back without saving the report.
The Database Schema Localization Information screen is displayed.
Do one of the following:
If you have not localized your database schema, accept the default setting (the Use localized Order and Service Management Data check box deselected).
If you have localized your database schema, select the Use localized Order and Service Management Data check box, and click Browse to specify the path to your localized .jar file.
Click Next.
The Database Schema Tablespaces screen is displayed.
Note:
If the Installer takes an unusual amount of time to progress to the Database Schema Tablespaces screen, Oracle recommends that you purge the database recycle bin to ensure the Installer progresses more quickly the next time you run it. For information, see "OSM and RCU Installers Are Slow to Run Database Tablespace Query."Select tablespaces for the OSM database schemas:
Default Tablespace: Specifies the tablespace for the default tablespace option <default> available to all database schemas (except for the Temporary Tablespace).
Temporary Tablespace: Specifies the temporary tablespace for the database schema.
Model Data Tablespace: Specifies the model data tablespace for the database schema.
Model Index Tablespace: Specifies the model index tablespace for the database schema.
Order Data Tablespace: Specifies the order data tablespace for the database schema.
Order Index Tablespace: Specifies the order index tablespace for the database schema.
For each tablespace, you are shown how much space you have available and how much space is required. For more information, see "Tablespaces."
Click Next.
The Database Schema Partition Information screen is displayed.
Do one of the following:
If you have a license for Oracle Partitioning, accept the default selection (Use Oracle Partitioning features for optimal performance in high volume production environment) and do the following:
In the Orders per Partition field, enter the number of orders that will be allowed in a partition.
In the Number of Sub-partitions field, enter the number of sub-partitions allowed in a partition.
After installation, you can change the values that you selected during the installation process by updating the range_partition_size and subpartitions_number OSM database parameters. However, updates to these parameters do not affect existing partitions.
Note:
For more information about partitioning, see OSM System Administrator's Guide.If you do not want to use Oracle Partitioning, deselect the Use Oracle Partitioning features for optimal performance in high volume production environment check box. You may not need Oracle Partitioning features in a development environment.
Important:
Oracle strongly recommends partitioning in all production deployments or production test environments, particularly those with high order volumes or any volume of large or complex orders. If you choose not to partition your OSM schema, it could be expensive to later reverse your decision. Changing a non-partitioned schema that has accumulated a large volume of data to a partitioned schema involves time-consuming and resource intensive export/import.Click Next.
The Database Timezone Information screen is displayed.
From the Database Timezone list, select the time zone that corresponds to the time zone for your database server, and click Next.
Note:
For more information on time zone settings, see "Configuring Time Zone Settings in the Database" or OSM System Administrator's Guide.The WebLogic Configuration - Configuration Type screen is displayed.
Select Connect to a running WebLogic server to create resources and deploy OSM, and click Next.
Note:
Use the Connect to a running WebLogic server to create resources and deploy OSM option when you want to install the OSM server and create resources in WebLogic.Reserve the second option, Do not connect to a WebLogic server. Order and Service Management must be manually deployed, for situations where OSM has already been deployed and WebLogic Server resources already configured.
The WebLogic Server Connection Information screen is displayed.
Do the following:
In the WebLogic Host Name field, enter the name or IP address of the machine where WebLogic is installed.
In the WebLogic Port Number field, enter the port where WebLogic is operating.
In the WebLogic Admin User field, enter the name of the WebLogic administrator.
In the WebLogic Admin Password field, enter the password of the WebLogic administrator.
Select Connect to WebLogic via SSL to use an SSL connection to the WebLogic admin server. The server's SSL port must be enabled to use this feature. By default, a non-SSL connection is used.
If using SSL, in the WebLogic SSL Port Number field, enter the port number of the WebLogic admin server.
If using SSL, specify the location of the key store file required for the SSL connection by typing the full path and directory, or click Browse to locate the directory.
The default location of the cacerts key store file is WebLogic_home/server/lib.
Click Next.
The WebLogic Server Deployment Target screen is displayed.
From the list, select the server or cluster as follows:
If you created a single WebLogic admin server, select the admin server.
If you created a WebLogic admin server with managed server, select the managed server.
If you created a WebLogic cluster, select the cluster.
Note:
The list shows only the targets on which ADF has been configured.Click Next.
If you are performing an upgrade and there are open connections to the database schema, the Open Database Sessions Detected screen is displayed.
If you specified an Oracle RAC database with its SID, and there are no open connections to the database schema, the Oracle Real Application Clusters Configuration screen is displayed. Go to step 36.
Otherwise, the Third-party Software Configuration Information screen is displayed. Go to step 41.
If you are performing an upgrade and there are database connections currently open, decide whether you want the OSM installer to remove the sessions or whether you would prefer to manually remove them outside the OSM installer. If you would like the OSM installer to remove the connections, ensure that Kill all sessions automatically during the upgrade process is selected. Otherwise, deselect that option. Click Next.
The Database Configuration Comparison screen is displayed.
This screen displays the existing JDBC configuration and the proposed new JDBC configuration. Do one of the following:
If you want to replace the existing configuration with the proposed new configuration, select Replace the existing JDBC data source configuration...
Note:
The OSM installer does not perform any data migration. Therefore, if you select this option, all configuration parameters will be reset.If you do not want to replace the existing configuration with the proposed new configuration, select Leave the existing JDBC data source configuration intact.
Click Next.
If you specified an Oracle RAC database with its SID, the Oracle Real Application Clusters Configuration screen is displayed.
Otherwise, the Third-party Software Configuration Information screen is displayed. Go to step 41.
Do one of the following:
If you want to use Oracle RAC, select Use Oracle RAC and click Next.
If you do not want to use Oracle RAC, deselect Use Oracle RAC and click Next.
The Installer configures a single data source for the Oracle RAC instance specified in step 15, but does not create a multi data source. OSM will not use Oracle RAC for load balancing or failover.
The Third-party Software Configuration Information screen is displayed. Go to step 41.
Note:
If you decide in the future to implement Oracle RAC for load balancing or failover, you must run the Installer again and select Use Oracle RAC. You cannot manually add and configure the primary Oracle RAC database instance.Do one of the following:
In the Configure WebLogic JDBC data sources area select one of the following options:
to use additional RAC Database instances now
The Installer preconfigures the database connections in WebLogic.
manually after installation completes
You can add more Oracle RAC database instances manually after installation. See "Manually Configuring Additional Data Sources for an Oracle RAC Instance" for configuration details.
In the RAC operation mode area, select one of the following options:
Load Balancing (Active Active) - Order and Service Management WebLogic Cluster Installations
The Installer groups the WebLogic Server instances according to the number of Oracle RAC database instances. Each group is configured to a separate Oracle RAC database as the primary data source, and the remaining Oracle RAC database instances as secondary data sources.
This option is available only if OSM is deployed to a WebLogic cluster.
Failover (Active Passive)
The Installer configures multi data sources and data sources according to the number of Oracle RAC database instances. The first data source of each multi data source connects to the primary database instance specified in step 15, and the subsequent data sources connect to other database instances to be specified. This option preconfigures the database connections in WebLogic for warm standby.
In the Listener Configuration area, select one of the following options:
Remote Listener (SCAN Listener)
Local Listeners
See "Listener Considerations for Oracle RAC" for a discussion on listener functionality.
Click Next.
Do one of the following:
Do one of the following:
If you selected the remote listener option:
In the SCAN Address field, you can modify the SCAN address if required. For example, you may need to do this if you entered an incorrect address in the Host field in step 15.
In the SCAN Port field, you can modify the SCAN port if required. For example, you may need to do this if you entered an incorrect port in the Port field in step 15.
Add a new row and specify the same Service Name as you did for the primary instance and a unique SID for each additional Oracle RAC instance. For a container database, use the PDB service name and the CDB SID.
If you did not specify the SID of the primary Oracle RAC instance in step 15, do so now in the first row. For a container database, use the CDB SID.
If you selected the local listeners option, add a new row for each additional Oracle RAC instance and specify:
The host and port: Each row must use a different combination of host and port. For example, if you use the same host, you must use a different port.
The service name or SID: Each row must specify either the same service name as the primary instance or a unique SID. Rows can also specify both service name and SID. Specify the same fields as you did for the primary instance. For example, if you only specified the SID for the primary instance, specify unique SIDs for the additional instances. For a container database, use the PDB service name and the CDB SID.
All instances must be in the same database.
Click Next.
The Third-party Software Configuration Information screen is displayed.
Enter or browse to the locations for the JBoss software. The JBoss libraries are located in the lib directory inside the directory where you unzipped JBoss. Click Next.
If the value of the Java Transaction API (JTA) Timeout Seconds parameter for your WebLogic domain is less than 600 seconds (the default WebLogic value is 30), the Installer prompts you to increase the Timeout Seconds value. The current value is displayed in the Timeout in Seconds field. Do one of the following:
Update the Timeout Seconds value to a value greater than or equal to 600 and click Next.
Do not update the Timeout Seconds value and click Next.
A warning is displayed. Click OK to accept the warning and continue with installation.
For more information about the JTA Timeout Seconds parameter, see the WebLogic Server Administration Console Help.
If you selected a WebLogic cluster, the WebLogic Cluster Web Service Request Configuration screen is displayed. Update the following fields:
Front End Host and Front End Port for Web Service HTTP requests. The Installer automatically populates these fields with the values configured for your WebLogic domain, proxy server, or load balancer.
If the WebLogic default values of <blank> and 0 appear, update the fields with the correct values. You must update these values to proceed with the installation.
For information about updating these fields again after installation, see the discussion about how to configure HTTP settings for a cluster in the WebLogic Server Administration Console Help.
(Optional) Front End SSL Port for Web Service HTTP requests.
Click Next.
If you specified a single-instance database in the Database Server Connection Information screen (step 15), the Database Connection Pool Information screen is displayed. Go to step 46.
If you specified an Oracle RAC database with its SID, the Oracle Real Application Clusters Configuration screen is displayed. Go to step 36.
Click Next.
The Database Connection Pool Information screen is displayed.
If you are not sure how to size the pool at this time, use the default settings. These settings can be tuned later from the WebLogic Server console. Do the following:
In the Initial Capacity field, enter the number of database connections initially reserved in the WebLogic connection pool.
Note:
In an Oracle RAC configuration, the initial capacity is set to 0 (read-only).In the Maximum Capacity field, enter the maximum number of database connections reserved in the WebLogic connection pool.
In the Capacity Increment field, enter the number of connections added when the connection pool maintained by the WebLogic Server is exhausted.
Note:
In an Oracle RAC configuration, this connection pool information will be shared.Click Next.
The JMS Store Information screen is displayed.
Accept the default setting of JMS File Store or select the alternate JMS JDBC Store.
If you choose JMS File Store, OSM will use the default WebLogic file-based persistent store as the JMS store. After installation is complete, Oracle recommends that you configure one custom file store for each managed server and JMS server. For more information, see "Creating and Configuring Persistent File Stores."
While file stores provide better performance than JDBC stores, the benefit of JDBC stores is that online database backups can obtain consistent snapshots of both OSM data and JMS messages. However, there is currently no mechanism for consistent backup of JDBC stores and transaction logs. For more information about backup strategies, see OSM System Administrator's Guide.
Click Next.
If OSM is being deployed to a WebLogic cluster, the WebLogic Coherence Cluster Configuration screen is displayed.
If OSM is being deployed to a single WebLogic server, the OSM Administrator and Deployment Credentials screen is displayed. Go to step 50.
Accept the settings for the WebLogic coherence cluster that the Installer has detected, or create a new coherence cluster by modifying the default values. The coherence cluster name is generated using the pattern: osmCoherenceClusterNNNN, where NNNN is a random four-digit number. Ensure that the IP Address value corresponds to the IP address or machine name of the WebLogic Server where the coherence cluster is running.
Note:
Oracle recommends using unicast cluster messaging mode. The Installer uses unicast mode and does not allow you to use the Installer to change the mode to multicast. Even if the target WebLogic cluster is a member of a coherence cluster that uses multicast mode, the Installer modifies the cluster messaging mode to unicast. For information about using WebLogic to change the cluster messaging mode to multicast, see "Configuring a Multicast IP Address for the Cluster Messaging Mode."Click Next. The OSM Administrator and Deployment Credentials screen is displayed.
The user names and passwords you provide will be used to create initial user accounts with administrator privileges and access to Oracle Communications Design Studio (the deployment tool). Do the following:
In the Admin User Name field, enter a user name, or use the default admin.
In the Password field, enter a password for the OSM Administrator user.
In the Password Confirmation field, re-enter the password for the OSM Administrator user.
In the Deploy Admin User Name field, enter a user name or use the default deployAdmin. Design Studio uses this user to deploy cartridges to OSM.
In the Password field, enter a password for the Deploy Admin user.
In the Password Confirmation field, re-enter the password for the Deploy Admin user.
Click Next.
The OSM WebLogic User Account Passwords screen is displayed.
You use this screen to create passwords for the standard users that are created for the application. The Automation User Name and OSM Core User Name are provided on this screen for reference only and are not editable. The passwords you enter must meet the password requirements for your WebLogic domain. Do the following:
In the Automation User Password field, enter the password for the oms-automation user. This is the internal automation user, used for processing OSM automation and email notifications. Re-enter the password in the second Confirm Password field.
In the OSM Core User Password field, enter the password for the oms-internal user. It is used for internal processing when an operation must be performed on behalf of the application rather than on behalf of the user. Re-enter the password in the third Confirm Password field.
Click Next.
The OSM Server Session Information screen is displayed.
The information in this screen is used to configure your OSM user sessions. Do the following:
In the Session Timeout field, enter the time in minutes that Order Management web client and Task web client sessions remain active.
In the Server Domain Suffix field, enter the domain suffix for the computers on which the OSM server will run.
In the Landing Page field, select the first page that Task web client users will see after login.
Click Next.
The Order and Service Management Remarks and Attachment Information screen is displayed.
The information on this screen is used to configure the text remarks and file attachments that users can add to OSM orders. Do the following:
In the Maximum Attachment Size field, enter the maximum attachment size in MB that can be appended to a remark.
In the Remark Change Timeout field, enter the length of time in hours that a remark can be edited before it becomes read-only.
Click Next.
The OSM Web Client Preferences screen is displayed.
The information in this screen is used to configure the number of records retrieved and displayed in the Task web client's Worklist, Query list, and Notification list. Do the following:
In the Worklist Rows Retrieved field, enter the number of rows OSM should retrieve when the worklist is refreshed.
In the Worklist Rows per Page field, enter the number of rows OSM should display on each Worklist page.
In the Query Rows Retrieved field, enter the number of rows OSM should retrieve when a query is run.
In the Query Rows per Page field, enter the number of rows OSM should display on each query results page.
In the Notification Rows Retrieved field, enter the number of rows OSM should retrieve when the notification list is refreshed.
In the Notification Rows per Page field, enter the number of rows OSM should display on each notification page.
Click Next.
The Order and Service Management Notification Emails screen is displayed.
The information in this screen is used to configure the email notifications for OSM. Do the following:
In the Notification Email Server field, enter the DNS name or IP address of your email server.
In the Notification Email Server Port field, enter the port on which the email server is listening.
In the Administrator Email Address field, enter the OSM Administrator's email address.
Click Next.
The Task Processor Configuration screen is displayed.
The information in this screen is used to control the rule and delay task evaluation. You can change these settings at any time after installing OSM. See OSM System Administrator's Guide for information about changing these values in oms-config.xml.
Do the following:
In the Task Processor Interval field, enter the number of seconds between task processor polls.
In the Maximum Rule Processor Count field, enter the maximum number of rule task processors used to evaluate rules.
In the Maximum Delay Processor Count field, enter the maximum number of delay task processors used to evaluate delays.
Note:
The total number of processors will be adjusted automatically at run time to exceed not more than 10% of the connection pool size. For a non-production environment, you can use the default values.Click Next.
The Order and Service Management Application Deployment State screen is displayed.
Do one of the following:
If you want OSM to start when installation is complete, ensure that Start the OSM application after installation is complete is selected and click Next. You should always select this option for a new installation of OSM. You should also use this option if you are performing an upgrade, except as noted below.
If you do not want OSM to start when installation is complete, deselect Start the OSM application after installation is complete and click Next. This option can be used in an upgrade when you want to ensure that you can perform WebLogic configuration before OSM begins to process any queued orders.
Note:
If you decide not to start OSM after installation is complete, you will not be able to select any of the server features in the next screen.The Order and Service Management Server Features screen is displayed.
Select Job Orders if you want to install the job control order cartridges that enable the job control order feature.
If you chose to manually deploy the cartridges for this feature later, see OSM_home/ProductCartridges/install/ReadMe.txt for instructions to manually deploy the product cartridges after you have installed OSM.
Click Next.
The Configuration Overview screen is displayed.
This screen displays all of your WebLogic Server and OSM configuration settings. and allows you to save those settings to a file. Do the following:
To save your settings to a silent installation configuration file for future use, select the Save Configuration check box. Saving your settings is optional.
When you select Save Configuration, a field is added to the screen that allows you to enter or browse to the directory in which you would like to save the configuration file.
You can also choose to save the passwords in the configuration file as clear text by selecting the Save Password check box.
Note:
Among the configuration parameters displayed on the Configuration Overview screen, the following parameters are for internal use only:Existing-Schema-Action
Halt-on-Warning
Halt-on-Error
Warning-Property
Error-Property
Oracle recommends that you do not modify these parameters. For example, to ensure a successful installation, do not modify the Existing-Schema-Action parameter to any value other than upgrade, not even when creating a new OSM database schema.
Click Next.
A screen is displayed containing the location and components to be installed and the total size of the OSM installation.
Click Next.
The OSM installation begins.
When the installation completes, the installation summary displays the location of the installation and database logs, which contain detailed information about your installation, including any warnings or problems encountered.
If you have selected to install OSM with product features, such as the job control order feature, the Order and Service Management Server restart required screen appears. Manually shutdown and restart the Oracle WebLogic Server. When the Oracle WebLogic Server restarts, click Next.
The Deploying product cartridges progress bar appears showing the progress of the product cartridge deployment that support the selected features.
Note:
If you want to complete the installation without restarting the OSM server, that is, without having to wait for the OSM application to deploy a product cartridge (such as the job control cartridge), click Cancel.Click Finish.
The installation is complete.
Note:
After installing OSM, shut down and restart the Oracle WebLogic Server if you have not already done so after deploying the product cartridges. To verify that OSM installed properly, see "Verifying the OSM Installation."When the installer fails during an installation, you receive an error message. Before you continue with the installation, you must find and resolve the issue that caused the failure. There are several places where you can look to find information about the issue.
The database installation plan action spreadsheet is a file that contains a summary of all the installation actions that are part of this OSM database schema installation or upgrade. The actions are listed in the order that they are performed. The spreadsheet includes actions that have not yet been completed. To find the action that caused the failure, go to the OSM_home/Database/dbinstall/install/om_$install$plan_actions.csv file and review the status column. The failed action is the first action with a status that is FAILED. The error_message column of that row contains the reason for the failure.
The database installation log file gives a more detailed description of all the installation actions that have been run for this installation. The issue that caused the failure is located in the OSM_home/Database/dbinstall/install/dbInstaller.log file. The failed action is typically at the bottom, that is, the last action that was performed.
There are also the following database tables that contain information about the database installation:
om_$install$plan_actions: Contains the same information as the database plan action spreadsheet. Compare this table to the spreadsheet in cases of a database connection failure.
om_$install$plan: Contains a summary of the installation that have been performed on this OSM database schema.
When you install the Oracle database schema for the first time and the database schema installation fails, you must do the following high-level steps:
Delete the new schema, or use a new schema user name for the subsequent installation.
Restart the database schema installation from the beginning.
Note:
If you are upgrading the database schema, you can restart the installation from the point of failure. For more information, see "Recovering from a Database Upgrade Failure."