Skip Headers
Oracle® Communications Order and Service Management Installation Guide
Release 7.2.2

E35412-06
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

6 Installing OSM in Interactive Mode

You can install Oracle Communications Order and Service Management (OSM) in two modes: interactive mode or silent (unattended) mode. This chapter provides instructions on installing OSM in interactive mode.

Oracle recommends that you perform an interactive installation first in order to save the settings. You can use these settings to perform subsequent silent installations on other systems. See "Installing OSM in Silent Mode" for information on installing OSM in silent mode.

In general, for test systems, product evaluation, development, or process modeling, you can install OSM using the default configuration, performance tuning is not required. For a production installation, you need to tune the OSM configuration to your specific requirements, based on the number of orders you process, the number of OSM users you need to support, and other factors. For information on configuring OSM after installation, see OSM System Administrator's Guide or contact Oracle.

Before you can install OSM, you must install the Oracle Database server, Oracle Database Client (required only if you are installing OSM Administrator), and the Oracle WebLogic Server. Both Oracle Database and Oracle WebLogic Server must be running during installation. See Chapter 4, "Installing and Configuring the Oracle Database" and Chapter 5, "Installing and Configuring WebLogic Server."

You will also need to create a WebLogic domain. See the Oracle WebLogic Server documentation for information about domain structures and their configuration. See "WebLogic Deployment Options" for more information about Oracle WebLogic Server deployment options.

To perform an interactive installation:

  1. Download the installation executable from the Oracle software delivery Web site at:

    http://edelivery.oracle.com/

  2. Use the OSM installation wizard to perform the installation. See "Interactive Installation of OSM" for details.

  3. Verify the installation. See "Verifying the OSM Installation".

Interactive Installation of OSM

This section describes a first time interactive installation in which all OSM components are installed. This type of installation is known as a Custom installation. Selecting the Custom installation type allows you to install one or more OSM components, such as the Database Schema, Server, Administrator, SDK Tools, and SDK Samples.

On a Windows platform, selecting the Typical installation type installs everything except the SDK Tools and Samples. On a non-Windows platform (such as Linux), a Typical installation installs the Database Schema and Server. Some components, such as Database Utilities, Administrator, and Web clients, are supported only on Windows-based machines. See "Installing Windows-Only Components" for more information.

The following installation procedure installs all components and applies to all supported platforms.

Note:

If localizing, make a backup of your WebLogic Server configuration prior to running the OSM installation procedure. See OSM Developer's Guide for more information on localizing. See OSM System Administrator's Guide for backup and restore procedures.

To perform a custom installation (all components):

  1. On UNIX systems:

    1. Make sure your DISPLAY environment variable is properly set.

    2. Make sure that the OSM UNIX user has full access to /tmp/vfs_cache folder.

      Note:

      If you cannot use this folder, or the contents of the /tmp folder gets purged periodically, you can change the location of the /vfs_cache folder 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).
    3. Change to the directory containing the installation executables.

    4. Modify the installation file attributes so it is executable: chmod 500 InstallOS_name.bin

  2. Download and unpack the required third-party components. Save the third-party components to a folder on the same machine on which the installer is running. See "Downloading Third-Party Components" and Table 2-1 for more information about required software.

  3. Do one of the following:

    • On Oracle Linux and Red Hat Enterprise Linux, execute the command: InstallLinux.bin

      Note:

      If the GUI installer screen does not start and you receive the following error message:
      Setup.product.install, com.installshield.wizard.StandardWizardListener, err, could not initialize interface awt...
      

      set the following environment variable and try running the installer again:

      export AWT_TOOLKIT=MToolkit
      
    • On Oracle Solaris, execute the command: InstallSparc.bin

      Note:

      If the GUI installer screen does not start and you receive the following error message:
      UnsatisfiedLinkError: java: fatal: libXm.so.4: open failed: No such file or directory ...
      

      set the following environment variable and try running the installer again:

      export AWT_TOOLKIT=XToolkit
      

      Or, if you receive the following error message:

      Setup.product.install, com.installshield.wizard.StandardWizardListener, err, could not initialize interface awt...
      

      set the following environment variable and try running the installer again:

      export AWT_TOOLKIT=MToolkit
      
    • On IBM AIX, execute the command: InstallAix.bin

    • On Windows, navigate to the directory containing the installation executables and double-click Install.exe.

      Note:

      For UNIX systems, you can optionally specify the location of the OSM log file that logs all OSM installer activity. Use the following attributes when running the installation command:
      -is:tempdir temp_directory is:log log_file.log
      

      where temp_directory is the location of the log file and log_file is the log file name.

      For example:

      ./InstallLinux.bin -is:tempdir /tmp/osm -is:log osmlog.log
      

    The Welcome screen is displayed.

  4. Review the pre-installation checklist and additional third-party component requirements.

    Note:

    The third-party components are required for the OSM Server and SDK Tools components.
  5. Select the View 3rd party readme now check box and click Next.

    The Order and Service Management 3rd party Requirements Information is displayed.

  6. Review the readme contents for the third-party components, then click Next.

    The OSM installation screen is displayed.

  7. Do 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, part of the SDK (the automation module) is not upgraded. Specify a new directory to ensure complete installation of the new OSM SDK.

      Click Next. The setup type screen is displayed.

  8. Select Custom and click Next.

    The Component Selection screen is displayed.

  9. Select the components you want to install, and click Next.

    Note:

    A Custom Installation allows you to install Database Schema, Server, Administrator, SDK Tools and SDK Samples. Installation of the OSM Server and SDK Samples also includes silent installation template files (installOptions.txt and install_cfg.xml) in the OSM_home\SDK\Samples\installation directory. These files serve as templates in silent mode. For more information on silent installations, see Chapter 8, "Installing OSM in Silent Mode".

    The installation overview screen is displayed, outlining the upcoming stages of the installation.

  10. Click Next to continue.

    The Database Connection Information screen is displayed.

  11. Use this screen to specify the Oracle Database instance where the OSM database schema will be installed/upgraded.

    You can specify a single-instance database or an Oracle RAC database. If you want to configure an Oracle RAC database for failover, specify the primary database instance here. You will specify the secondary database instance in a later step.

    Do the following:

    1. In the Database Instance Host field, enter the IP address or DNS name of the host where the database listens for requests.

      Note:

      If you specify an Oracle RAC database, enter the Single Client Access Name (SCAN) in this field.
    2. In the Database Instance Port field, enter the port where the database listens for requests.

    3. In the Database Service Name field, enter the service name of the database. For example, this could be the default database service or a service created specifically for OSM.

      Note:

      You must enter either the database service name or SID, both fields cannot be empty.
    4. In the Database Instance SID field, enter the name (system identifier) of the database instance.

      Note:

      If you specify an Oracle RAC database instance and are using a remote listener (server-side load balancing), you must specify the SID. 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.

      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.
    5. Click Next.

      The Database Administrator Credential Information screen is displayed.

  12. Enter the user name and password for the database administrator (DBA) user and click Next.

    The Database Credential Information screen is displayed. This information is used by the OSM server to connect to Oracle Database.

    Note:

    The DBA user requires the following permissions to configure and administer the Oracle database:
    • Connect to a resource with administrator option

    • Execute on dbms_lock with grant option

    • Select on dba_jobs with grant option

    • Execute on exp_full_database and imp_full_database with administrator option

    • Create table with admin option

    • Create materialized view with administrator option

    • Query rewrite with administrator option

    • Select on v_$parameter with grant option

    • sysdba role

    Note:

    If you choose to connect as a sys user and your database settings require you to connect the sys user as a sysdba, append "as sysdba" to the value for the db connection string parameter. Note that appending "as" in the connection string may cause the connection to become unreliable.
  13. Enter the required user names and passwords.

    1. In the Core Schema Username field, enter the name of the Oracle account for the OSM database schema.

    2. In the Core Schema Password field, enter the password for the primary schema Oracle account.

    3. In the Password Confirmation field, enter the password for the primary schema Oracle account again.

    4. In the Rule Engine Schema Username field, enter the name of the Oracle account for the OSM rule engine database schema.

    5. In the Rule Engine Schema Password field, enter the password for the rule engine schema Oracle account.

    6. In the Password Confirmation field, enter the password for the rule engine schema Oracle account again.

      Note:

      If these user accounts do not exist, they will be created for you during installation.
    7. Click Next.

  14. One of the following schema status screens is displayed:

    • Order and Service Management Database Not Found

      Click Next to create a new database and continue with the installation.

    • Order and Service Management Database Schema Found

      If the existing database version is the same as the version to be installed, click Next to continue the installation.

      If the existing database version is different from the version to be installed, you need to upgrade the database.

      1. On the schema status screen, click Analyze and click Next (the analysis can take a few minutes to run).

        The analysis report screen is displayed.

      2. On reviewing the report, either save the report and click Next, or click Back without saving the report.

  15. In the Database Schema Localization Information screen, do one of the following, and click Next.

    • If you have not localized your database schema, accept the default setting (check box deselected).

    • If you have localized your database schema, enable the Use localized Order and Service Management Data check box, and click Browse to specify the path to your localized jar file.

    The Database Schema Tablespaces screen is displayed.

  16. 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".

  17. Click Next.

    The Database Schema Partition Information screen is displayed.

  18. Do the following:

    1. Select the Use Oracle Partitioning features for optimal performance in high volume production environment check box.

    2. In the Orders per Partition field, enter the number of orders that will be allowed in a partition.

    3. In the Number of Sub-partitions field, enter the number of sub-partitions allowed in a partition.

      Note:

      For more information on partitioning, see OSM System Administrator's Guide.
    4. Click Next.

      The Database Timezone Information screen is displayed.

  19. From the Database Timezone list, select the Non-Daylight-Saving time zone that corresponds to the time zone for your database server, and then click Next.

    Note:

    For more information on time zone settings, see OSM System Administrator's Guide.

    The next screens configure the Oracle WebLogic Server.

    The WebLogic Configuration - Configuration Type screen is displayed.

  20. Select Connect to a running WebLogic server to create resources and deploy OSM, and click Next.

    Note:

    The option "Connect to a running WebLogic server to create resources and deploy OSM" is used when you want to install the OSM server and create resources in WebLogic.

    The second option "Do not connect to a WebLogic server. Order and Service Management must be manually deployed." should only be reserved for situations where OSM has already been deployed and WebLogic Server resources already configured.

    The WebLogic Server Connection Information screen is displayed.

  21. Do the following:

    1. In the WebLogic Host Name field, enter the name or IP address of the machine where WebLogic is installed.

    2. In the WebLogic Port Number field, enter the port where WebLogic is operating.

    3. In the WebLogic Admin User field, enter the name of the WebLogic administrator.

    4. In the WebLogic Admin Password field, enter the password of the WebLogic administrator.

    5. 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.

    6. In the WebLogic SSL Port Number field, enter the port number of the WebLogic admin server.

    7. 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 MW_home/wlserver_10.3/server/lib.

    8. Click Next.

  22. If you have a single WebLogic server, the screen for selecting the Third Party Software location is displayed. Go to step 24.

    If you have multiple WebLogic servers, the server selection screen is displayed. Go to step 23.

  23. From the list, select the server/cluster do the following:

    • 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.

    Click Next to go to the screen for selecting the Third Party Software location.

  24. In the screen for selecting the Third Party Software location, enter or browse to the locations for the JBoss and Saxon software. The JBoss libraries are located in the lib directory inside the directory where you unzipped JBoss. The Saxon directory location is the same directory where you unzipped the Saxon software. Click Next.

  25. If you specified a single-instance database in the Database Server Connection Information screen (step 11), go to step 30.

    If you specified an Oracle RAC database with its SID, the Oracle Real Application Clusters (RAC) Configuration screen is displayed. Go to step 26.

  26. Do one of the following:

    • If OSM is deployed to a single WebLogic Server instance, you can configure Oracle RAC for failover. Select one of the following options:

      • Configure an additional (secondary) Oracle RAC instance for failover using the installer.

        The installer configures a multi data source and two data sources. The first data source connects to the primary instance previously specified, and the second data source connects to the secondary instance to be specified. This option preconfigures the database connections in WebLogic for warm standby. See "Configuring Oracle Database with Real Application Clusters (RAC)" for database configuration details.

      • After installation completes, manually configure an additional Oracle RAC instance for failover in WebLogic.

        The installer configures a multi data source and one data source which connects to the primary instance previously specified. This option offers the flexibility to add one or more Oracle RAC database instances, post installation. See "Configuring an Additional Data Source for an Oracle RAC Instance" for configuration details.

      • Do not use Oracle RAC.

        The installer configures a single data source for the Oracle RAC instance previously specified but does not create a multi data source. OSM will not use Oracle RAC failover.

        Note:

        If you decide in the future to implement Oracle RAC for failover, you must run the installer again and select either the first or second configuration option described here. You cannot manually add and configure the Oracle RAC database instance.
    • If OSM is deployed to a WebLogic cluster, you can configure Oracle RAC for either load balancing or failover. Select one of the following options:

      • Configure an additional Oracle RAC instance for load balancing using the installer.

        The installer configures half of the WebLogic Server instances to one Oracle RAC database instance as the first data source, and the other Oracle RAC database instance as the second data source. The other half of the instances in the WebLogic Server cluster are configured with the sequence of the Oracle RAC database instances swapped. See "Connecting Oracle RAC with JDBC Multi Data Source" for more information.

      • Configure an additional (secondary) Oracle RAC instance for failover using the installer.

        The installer configures a multi data source and two data sources. The first data source connects to the primary instance previously specified, and the second data source connects to the secondary instance to be specified. This option preconfigures the database connections in WebLogic for warm standby. See "Connecting Oracle RAC with JDBC Multi Data Source" for more information.

      • After installation completes, manually configure an additional Oracle RAC instance for load balancing in WebLogic.

        The installer configures a multi data source and one data source which connects to the Oracle RAC database instance previously specified. This option offers the flexibility to add one or more Oracle RAC database instances, after installation. See "Configuring an Additional Data Source for an Oracle RAC Instance" for configuration details.

      • After installation completes, manually configure an additional Oracle RAC instance for failover in WebLogic.

        The installer configures a multi data source and one data source which connects to the primary instance previously specified. This option offers the flexibility to add one or more Oracle RAC database instances, after installation. See "Configuring an Additional Data Source for an Oracle RAC Instance" for configuration details.

      • Do not use Oracle RAC.

        The installer configures a single data source for the Oracle RAC instance previously specified but does not create a multi data source. OSM will not use Oracle RAC for load balancing or failover.

        Note:

        If you decide in the future to implement Oracle RAC for load balancing or failover, you must run the installer again and select one of the first four options described here. You cannot manually add and configure the Oracle RAC database instance.
  27. Click Next.

    If you chose any option other than the first option in step 26, go to step 30.

    If you chose to configure an additional Oracle RAC instance for load balancing or failover using the installer (first option), the Oracle RAC Listener Configuration screen is displayed.

  28. Specify whether your Oracle RAC instances use a remote listener (server-side load balancing enabled) or local listeners and click Next. See "Listener Considerations for Oracle RAC" for a discussion on listener functionality.

    If you chose the remote listener option and you did not previously specify the SID of the primary Oracle RAC instance (step 11), the installer takes you to the Database Connection Information screen to enter the SID (the host, port, and service name are protected). After entering the SID, you will be prompted to configure your Oracle RAC database instance for failover or load balancing, depending on your deployment. If you select any option other than the first option, the Database Connection Pool Information screen is displayed. If you select the first option, installation resumes at the next step.

    The Additional Oracle RAC Instance Connection Information screen is displayed.

  29. Specify the connection information for the additional Oracle RAC instance. Both instances must be in the same database.

    If you chose the remote listener option, enter the SID (all other fields are protected).

    If you chose the local listeners option, you can edit any field except the service name.

    Click Next. The Database Connection Pool Information screen is displayed.

  30. 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:

    1. 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).
    2. In the Maximum Capacity field, enter the maximum number of database connections reserved in the WebLogic connection pool

    3. 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.
    4. Click Next.

    The JMS Store Information screen is displayed.

  31. Accept the default setting of JMS File Store or select the alternate JMS JDBC Store.

    If you choose JMS File Store, OSM will use a 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.

    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 on backup strategies, see OSM System Administrator's Guide.

    Click Next. The OSM Administrator User Information screen is displayed.

  32. The user name and password you provide will be used to create an initial user account with access to the OSM Administrator. Do the following:

    1. In the Username field, enter a user name, if it is different from the default.

    2. In the Password field, enter the password.

    3. In the Password Confirmation field, re-enter the password.

    4. Click Next.

      The OSM User Credential Information screen is displayed.

  33. You use this screen to create passwords for the standard users that are created for the application. These passwords must meet the password requirements for your WebLogic domain. Do the following:

    1. In the Design Studio User Password field, enter the password for the sceadmin user. This user is used by Oracle Communications Design Studio to deploy cartridges from Studio to OSM. Re-enter the password in the first Confirm Password field.

    2. 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.

    3. 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.

    4. Click Next.

      The OSM Server Session Information screen is displayed.

  34. The information in this screen is used to configure your OSM user sessions. Do the following:

    1. In the HTTP Login Security Setting field, select whether or not to use SSL while logging in to the Order Management Web client and Task Web client.

    2. In the Session Timeout field, enter the time in minutes that Order Management Web client and Task Web client sessions remain active

    3. In the Server Domain Suffix field, enter the domain suffix for the computers on which the OSM server will run.

    4. In the Landing Page field, select the first page that Task Web client users will see after login.

    5. Click Next.

      The Order and Service Management Remarks and Attachment Information screen is displayed.

  35. 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:

    1. In the Maximum Attachment Size field, enter the maximum attachment size in MB that can be appended to a remark.

    2. In the Remark Change Timeout field, enter the length of time in hours that a remark can be edited before it becomes read-only.

    3. Click Next.

      The OSM Web Client Preferences screen is displayed.

  36. 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:

    1. In the Worklist Rows Retrieved field, enter the number of rows OSM should retrieve when the worklist is refreshed.

    2. In the Worklist Rows per Page field, enter the number of rows OSM should display on each Worklist page.

    3. In the Query Rows Retrieved field, enter the number of rows OSM should retrieve when a query is run.

    4. In the Query Rows per Page field, enter the number of rows OSM should display on each query results page.

    5. In the Notification Rows Retrieved field, enter the number of rows OSM should retrieve when the notification list is refreshed.

    6. In the Notification Rows per Page field, enter the number of rows OSM should display on each notification page.

    7. Click Next.

      The Order and Service Management Notification Emails screen is displayed.

  37. The information in this screen is used to configure the email notifications for OSM. Do the following:

    1. In the Notification Email Server field, enter the DNS name or IP address of your email server.

    2. In the Notification Email Server Port field, enter the port on which the email server is listening.

    3. In the Administrator Email Address field, enter the OSM Administrator's email address.

    4. Click Next.

      The Task Processor Configuration screen is displayed.

  38. The information in this screen is used to control the rule and delay task evaluation. Do the following:

    1. In the Task Processor Interval field, enter the number of seconds between task processor polls.

    2. In the Maximum Rule Processor Count field, enter the maximum number of rule task processors used to evaluate rules.

    3. 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. See OSM System Administrator's Guide for information about configuring the rule engine for performance.
    4. Click Next.

      The Configuration Overview screen is displayed.

  39. 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:

    1. To save your settings to a silent installation configuration file for future use, select the Save Configuration check box. Saving your settings is optional.

    2. 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.

    3. You can also choose to save the passwords in the configuration file as clear text by selecting the Save Password check box.

    4. Click Next.

      A screen is displayed containing the location and components to be installed and the total size of the OSM installation.

  40. 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.

  41. Click Finish.

    The installation is complete.

    Note:

    After installing OSM, shut down and restart the Oracle WebLogic Server. To verify that OSM installed properly, see "Verifying the OSM Installation".

Default Accounts in WebLogic Security Realm

When OSM is installed, several default accounts are created in WebLogic Security Realm. These accounts are required for application functionality. To see the accounts:

  1. Log in to the WebLogic Server using WebLogic username and password.

    The WebLogic Administrator Console is displayed.

  2. Under the Domain Structure, click Security Realm.

    The Summary of Security Realms is displayed.

  3. Click myrealm from the table.

    The Settings for myrealm is displayed.

  4. Click Users and Groups tab.

    This page displays information about each user that has been configured in this security realm.

Table 6-1 and Table 6-2 list the users, groups, and their descriptions.

Table 6-1 Default Application Accounts

Default Account Description Assigned Groups

Default administrator account

Default OSM Administrator.Account name and password are specified during application installation.

OMS_designer

OMS_user_assigner

OMS_workgroup_manager

OMS_client

OMS_xml_api

OMS_ws_api

OSM_USER_Manager

oms-automation

Used for processing of OSM automation and email notifications.

OSM_automation

OMS_client

oms-internal

Used for internal processing when operation must be performed on behalf of the application rather than on behalf of the user.

Administrators

OSM_automation

sceadmin

Used by Design Studio Admin

Cartridge_Management_WebService


Table 6-2 Default Groups in the Server Security Realm

Group Name Description Assigned Groups

OMS_client

Provides access to application Web client

N/A

OMS_designer

Process, modeling, and system maintenance

N/A

OMS_user_assigner

Allows add users to workgroups

N/A

OMS_workgroup_manager

Allows create or modify workgroups

N/A

OMS_log_manager

Allows management of application log settings

N/A

OMS_cache_manager

Monitoring and control of order cache

N/A

OMS_xml_api

XML API access

N/A

OMS_ws_api

WebService API access

N/A

Cartridge_Management_WebService

OSM cartridge management API access.

Administrators

OSM_automation

This role is granted to the user that is allowed to execute the automation plug-in.

N/A

OSM_USER_Manager

Required to manage users and workgroups.

N/A


Note:

Security-related changes in OSM 7.0
  • To be able to use the OSM Administrator application, users must be assigned to the osm_workgroup_manager and osm_user_assigner groups in WebLogic.

  • All users that need to access or run automation plug-ins are assigned to the OSM_automation group. This is performed automatically by the OSM Installer (for the oms-automation user) and by Design Studio (for automation users specified in the "Run As" property of the automation plug-in).

Modifying Deployment Parameters

When deploying cartridges to a remote database, do the following to prevent a connection timeout before you complete the deployment:

  • Increase the value of the Stuck Thread Max Time parameter in the WebLogic Server console.

    For more information on this parameter, see the Oracle WebLogic Server documentation.

  • Increase the value of the Timeout Seconds Java Transaction API (JTA) parameter in the WebLogic Server Administration Console.

  • Increase the value of the transaction timeout parameter in the WebLogic Server startup script.

To increase the value of the Stuck Thread Max Time parameter:

  1. Log in to the WebLogic Server Administration Console.

  2. In the Domain Structure tree, expand Environment and then click Servers.

    The Summary of Servers page is displayed.

  3. Click the name of the WebLogic Server where you want to deploy the cartridges.

    The configuration parameters for the server are displayed on a tabbed page.

  4. Click the Tuning tab, and modify the value of the Stuck Thread Max Time parameter to an appropriate value in seconds.

  5. Click Save.

To increase the value of the Timeout Seconds parameter:

  1. Log in to the WebLogic Server Administration Console.

  2. In the Domain Structure tree, click the name the WebLogic server domain.

    The configuration parameters for the domain are displayed on a tabbed page.

  3. Click the JTA tab, and modify the value of the Timeout Seconds parameter to an appropriate value. In most cases, a value of 300 seconds is sufficient.

  4. Click Save.

To modify the cartridge deployment transaction timeout parameter:

  1. Open the startWebLogic.sh (UNIX or Linux) or startWebLogic.cmd (Windows) file for your WebLogic domain, and increase the value of

    -Dcom.mslv.oms.cartridgemgmt.DeployCartridgeMDB.CartridgeDeploymentTransaction

    Note:

    The maximum value for this parameter is 3600 seconds. If you exceed this limit, the value is restored to the default of 600 seconds. Try again with a value that is less than or equal to the maximum.

    For example in startWebLogic.sh on UNIX or Linux:

    export JAVA_OPTIONS="${JAVA_OPTIONS} -Dcom.mslv.oms.cartridgemgmt.DeployCartridgeMDB.CartridgeDeploymentTransactionTimeout=2400"
    

    For example in startWebLogic.cmd on Windows:

    set JAVA_OPTIONS=%JAVA_OPTIONS% -Dcom.mslv.oms.cartridgemgmt.DeployCartridgeMDB.CartridgeDeploymentTransactionTimeout=2400
    

Installing Windows-Only Components

The Windows-only components include the Database Utilities and the OSM Administrator application (used for managing users). These components are supported only on Windows-based machines.

If you are installing OSM from a UNIX-based platform, it is recommended that you perform two separate installations (UNIX and Windows).

To install Windows-only components:

  1. On a Windows machine, navigate to the directory containing the installation executables and double-click Install.exe.

  2. In the Choose Installation Type window, select Custom and then click Next.

  3. From the component selection list, select Database Utilities and Administrator, and click Next.

  4. Perform the remaining installation steps.

Note:

The files associated with these components are installed in the /bin and /Database directories of UNIX-based installations. You can transfer these files to a Windows machine (by FTP, for example) instead of performing a separate Windows installation. However, this method does not create the required shortcuts and menu items and is therefore not recommended.