C OSM Installed Components

When you run the various installers and follow the configuration procedures, the system creates and populates a directory structure and installs the components that OSM requires. For information about installing Oracle Communications Order and Service Management (OSM), see OSM Installation Guide.

This appendix describes the OSM directory structure and the components that are automatically configured by OSM Installer.

OSM Directory Structure

Table C-1 lists and describes the OSM directories.

Table C-1 OSM Directories

Directory Description

OSM_home/bin

Contains copies of the oms.ear file and cartridge management web service (cartridge_management_ws) application.

OSM_home/Database

Contains the following database installation files, in the /Database/osm-db-installer-core/install directory:

  • om_$install$plan_actions.csv

  • dbInstaller.log

  • omsmodel_l10n.jar

OSM_home/ProductCartridges

Contains the product cartridges.

OSM_home/SDK

Contains the SDK and SDK samples (optional). The following sub-directories are available in the SDK:

  • Automation: Used by Design Studio for compiling when there are automation plug-ins.

  • CartridgeManagementTool: Used for compiling and deploying task assignment.

  • Compliance: Needed to run the compliance tool. See OSM Installation Guide for more information.

  • Customization: Needed to manage the oms.ear file when updates are required for localization files.

  • Reporting: Needed to run reporting queries.

  • Samples: Contains development samples, for example, web services samples.

  • WebService: Contains web service definition language (WSDL) files.

  • XMLImportExport: Contains command line utilities for metadata management.

    Note: Oracle recommends using Design Studio for cartridge management.

  • XMLSchema: Contains schema definitions for the XML API.

Productized Cartridges

OSM provides the following cartridge that you can deploy when you run the Installer:

  • Job Order cartridge: Enables the job control order feature. For information about using job orders, see OSM Modeling Guide.

    Note:

    To manually deploy product cartridges, see OSM_home/ProductCartridges/install/ReadMe.txt for instructions about manually deploying the product cartridges after you have installed OSM.

WebLogic Installed Components

This section lists and describes the OSM WebLogic installed components and configurations.

WebLogic Deployments

Table C-2 lists the WebLogic deployments that are completed by the Installer.

Table C-2 WebLogic Deployments

Deployment Name Description

cartridge_management_ws

Application used to deploy, undeploy, and query cartridges.

oms

The Order and Service Management application.

WebLogic Configuration

This section lists and describes the WebLogic configuration that is completed by the Installer.

Coherence Clusters

The Installer configures the following coherence cluster:

  • osmCoherenceClusteruniqueid

    where uniqueid is a random four digit number used to generate a unique string.

For information about configuring Oracle coherence for an OSM cluster, see OSM Installation Guide.

Work Managers

See "Using Work Managers to Prioritize Work" for information about work managers.

Table C-3 lists and describes the work managers that are configured by the Installer.

Table C-3 Work Managers Configured by OSM Installer

Name Type Description

osmAutomationWorkManager

Work manager

Used to process work performed by automation tasks.

osmOmClientWorkManager

Work manager

Used to process requests from manual users using the Order Management web client.

osmTaskClientWorkManager

Work manager

Used to process requests from manual users using the Task web client.

osmWsHttpWorkManager

Work manager

Used to process OSM HTTP WebService requests.

osmWsJmsWorkManager

Work manager

Used to process OSM JMS WebService requests.

osmXmlWorkManager

Work manager

Used to process requests coming in from external clients for the OSM XML API.

osmMaxThreadConstraint

Maximum thread constraint

Used to ensure that the maximum thread size is not more than the JDBC connection pool size.

osmMinThreadConstraint

Minimum thread constraint

Used to ensure that there are always a number of threads available to log into the OSM web clients to avoid deadlock situations.

JMS Servers

The Installer configures the following JMS server:

  • oms_jms_server_ManagedServerName

    where ManagedServerName is the managed server that the JMS server is targeted to. In a non-clustered environment, the JMS server name is oms_jms_server.

JMS Module

The Installer configures the following JMS module:

  • oms_jms_module: Contains the JMS system resources for OSM.

Queues and Topics

Table C-4 lists the queues and topics that are configured by the Installer. A single managed server is named oms_jms_server.

In a cluster deployment, which has more than one managed server, each server is named according to the following format:

oms_jms_server_managedservername

where managedservername is the name of the managed server.

Each queue or topic listed in the table is configured on each of the servers. For example, the queue named oms_behavior_queue is configured as follows:

  • oms_behavior_queue_MS1

  • oms_behavior_queue_MS2

where MS1 is the first server in the cluster, and MS2 is the second server.

See "Using JMS Queues to Send Messages" for more information. Most queues are distributed when they are in a cluster. For information about setting up custom distributed queues, see OSM Installation Guide.

Distributed Destinations in a Cluster

In a clustered WebLogic deployment, if the destination is to be distributed, a distributed destination is created for each queue and topic. This distributed destination then has members created (a queue or topic) on each of the managed servers.

For example, in a clustered deployment that contains two managed servers called MS1 and MS2, the oms_behavior_queue queue has the following:

  • A distributed destination called oms_distributed_behavior_queue

  • Two members called oms_behavior_queue_MS1 and oms_behavior_queue_MS2

Table C-4 Queues and Topics Configured by OSM Installer

Name Type JNDI Distributed Cluster Name Description

oms_behavior_queue

Queue

mslv/oms/oms1/internal/jms/behaviors

oms_distributed_behavior_queue

Used to customize task assignment.

oms_cartridge_deploy

Queue

mslv/provisioning/internal/ejb/deployCartridgeQueue

N/A

Internal use only.

oms_events

Queue

mslv/oms/oms1/internal/jms/events

oms_distributed_events_queue

Internal use only.

oms_order_events

Topic

mslv/provisioning/external/orderevents

oms_distributed_order_events_queue

Where order lifecycle events are published.

oms_order_updates

Queue

mslv/provisioning/internal/ejb/orderupdates

oms_distributed_order_updates_queue

Internal use only.

oms_signal_topic

Topic

mslv/oms/oms1/internal/jms/InternalSignalTopic

oms_distributed_signal_topic

Internal use only.

oms_ws_cluster_correlates

Queue

oracle/communications/ordermanagement/WebServiceClusterCorrelateQueue

oms_distributed_cluster_ws_correlates_queue

Used to route OSM service requests, in the context of an existing order in a WebLogic Server cluster, to the managed server that owns the order.

oms_ws_cluster_requests

Queue

oracle/communications/ordermanagement/WebServiceClusterRequestQueue

oms_distributed_cluster_ws_requests_proxy_queue

Used to receive requests for order amendments in a WebLogic Server cluster. Can also be used for new order creation requests.

oms_ws_cluster_responses

Queue

oracle/communications/ordermanagement/WebServiceClusterResponseQueue

oms_distributed_cluster_ws_response_proxy_queue

Used to fetch a correlated message from the web service cluster correlate queue, analyze the original JMS properties, and forward the response to the original JMSReplyTo.

oms_ws_requests

Queue

oracle/communications/ordermanagement/WebServiceQueue

oms_distributed_ws_requests_queue

Used to receive order creation and amendment requests in a single-server WebLogic Server environment. Can also be used for new order creation requests for a WebLogic Server cluster.

osmErrorQueue

Queue

oracle/communications/ordermanagement/osm/ErrorQueue

osmErrorDistributedQueue

N/A

OrchestrationDependenciesQueue

Queue

oracle/communications/ordermanagement/OrchestrationDependenciesQueue

oms_distributed_orchestration_dependencies_queue

N/A

Quotas

Quotas are used to control the allotment of system resources available to OSM destinations (queues or topics).

Table C-5 lists and describes the quotas that are configured by the Installer.

Table C-5 Quotas Configured by OSM Installer

Quota Name Destination Name

oms_behavior_queue.Quota

oms_behavior_queue

oms_cartridge_deploy.Quota

oms_cartridge_deploy

oms_events.Quota

oms_events

oms_order_events.Quota

oms_order_events

oms_order_updates.Quota

oms_order_updates

oms_signal_topic.Quota

oms_signal_topic

oms_ws_cluster_correlates.Quota

oms_ws_cluster_correlates

oms_ws_cluster_requests.Quota

oms_ws_cluster_requests

oms_ws_cluster_responses.Quota

oms_ws_cluster_responses

oms_ws_requests.Quota

oms_ws_requests

OrchestrationDependeciesQueue.Quota

OrchestrationDependeciesQueue

osmErrorQueue.Quota

osmErrorQueue

Connection Factories

The Installer configures the following connection factories:

  • oms_connection_factory

  • omsExternalClientConnectionFactory: Use this connection factory to submit OSM Web Service and XML API requests (including order creation) from an external system.

Destination Key

The Installer configures the following destination key:

  • osmDescendingPriorityDestinationKey

For information about configuring destination keys, see Oracle Administration Console Online Help.

JMS Template

The installer configures a JMS template for the OSM destinations. This template applies recommended defaults for the following settings:

  • Redelivery Limit

  • Redelivery Delay

  • Error Destination

The Installer configures the following JMS template:

  • osmJmsTemplate

For information about JMS templates, see Oracle Administration Console Online Help.

File T3

The installer configures the following file:

  • Oms_Remote_File_System

For information about configuring the T3 file path to support attachments, see OSM Installation Guide.

Data Sources

OSM Installer configures the following types of data sources:

  • Active Active

  • Active Passive

The Installer also configures the following standalone data source:

  • oms_pool

Table C-6 lists the load balancing data sources configured by the Installer. For information about connecting Oracle RAC with JDBC multi data sources, see OSM Installation Guide.

Table C-6 Load Balancing Data Sources Configured by OSM Installer

Name Type Description

oms_pool_group

Multi

One oms_pool_group is required for each target server for failover.

osm_pool_rac_group

Generic

One osm_pool_rac_group is required for each target server. For example:

osm_pool_rac2_group_b

Table C-7 lists the failover data sources configured by the installer.

Table C-7 Failover Data Sources Configured by OSM Installer

Name Type Description

oms_pool

Multi

One oms_pool data source is configured for the cluster.

osm_pool_rac

Generic

  

Users and Groups

This section describes the users and groups that are created by the OSM Installer. For information about the users and groups that are created by the WebLogic Server Installer, see Fusion Middleware Securing Resources Using Roles and Policies for Oracle WebLogic Server.

A security realm consists of a set of configured security providers, users, groups, security roles, and security policies that protect WebLogic resources. To access WebLogic resources that belong a security realm, a user must be defined in that realm.

Add users to groups by using WebLogic Server Administration Console. For more information, see "Adding Users to Groups in the WebLogic Server Administration Console."

When OSM is installed, several default accounts are created in WebLogic Security Realm.

Table C-8 and Table C-9 list the users, groups, and their descriptions.

Table C-8 Default Application Accounts

Default Account Description Assigned Groups

Default OSM Administrator account

The OSM Administrator account name and password are specified during OSM installation. The default is admin.

OMS_user_assigner

OMS_workgroup_manager

OMS_client

OMS_xml_api

OMS_ws_api

OMS_ws_diag

oms-automation

Used for processing OSM automation and email notifications.

OSM_automation

osm-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

Default Design Studio administrator account

The Design Studio administrator account and password for managing OSM cartridges are specified during OSM installation. The default is deployAdmin.

Cartridge_Management_WebService

Table C-9 Default Groups in the Server Security Realm

Group Name Description

Cartridge_Management_WebService

OSM cartridge management access. This group also allows access to the features in the View Cartridges option in the Order Management web client. See OSM Order Management Web Client User's Guide for information about this feature.

This belongs to the Administrator group.

OMS_cache_manager

Monitoring and control of order cache.

OMS_client

Provides access to Order Management, Task, and Order Lifecycle Manager web clients.

OMS_user_assigner

Users in this group can do the following:

  • Associate users with workgroups

  • Manage notifications

  • Manage system events

  • Refresh the metadata cache

OMS_workgroup_manager

Users in this group can do the following:

  • Modify workgroup schedules

  • Delete workgroups

  • Manage notifications

  • Manage system events

  • Refresh the metadata cache

OMS_ws_api

WebService API access

OMS_ws_diag

WebService diagnostic access

OMS_xml_api

XML API access

OSM_automation

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

The Installer automatically assigns the oms-automation user to this group, and Design Studio automatically assigns users specified in the Run-As property of the automation plug-in.

Database Configuration

The OSM Installer creates the following database schemas:

  • Core schema

  • Rule engine schema

  • Reporting schema

Table C-10 shows the roles and permissions that are granted to database schema users.

Table C-10 Roles and Permissions Granted to Database Schema Users

Schema Roles and Permissions

Core

resource

create session

create table

create view

create synonym

create sequence

alter session

unlimited tablespace

create job

create any context

execute on dbms_lock

select on v_$parameter

Rule engine

resource

create session

create table

create view

create synonym

create sequence

alter session

unlimited tablespace

Reporting

resource

create session

create view

create synonym

unlimited tablespace