C OSM Installed Components

This appendix describes the components that are automatically configured for OSM cloud native.

Productized Cartridges

The OSM DB Installer deploys the following cartridge:

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

WebLogic Installed Components

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

WebLogic Deployments

Table C-1 lists the WebLogic deployments.

Table C-1 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.

Coherence Clusters

The following coherence cluster is configured:

  • osmCohClustproject-instance

    where project-instance is the project and instance name of your OSM cloud native instance.

Work Managers

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

Note:

Also, see the OSM default Work Managers, Constraints related to upgrade process (Doc ID 3019290.1) knowledge article on My Oracle Support, if you are upgrading from OSM version 7.3.1 or lower (source version) to OSM version 7.3.5 or higher (target version).

The following table lists and describes the work managers that are configured.

Table C-2 Configured Work Managers

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.
osmAutomationMaxThreadConstraint Maximum Thread Constraint Used to ensure that the maximum thread size is not more than the JDBC connection pool size.
osmGuiMaxThreadConstraint Maximum Thread Constraint N/A
osmHttpApiMaxThreadConstraint Maximum Thread Constraint N/A
osmJmsApiMaxThreadConstraint Maximum Thread Constraint N/A
osmGuiMinThreadConstraint Minimum Thread Constraint N/A
JMS Servers

The following JMS server is configured:

  • oms_jms_server

JMS Module

The following JMS module is configured:

  • oms_jms_module: Contains the JMS system resources for OSM.

Queues and Topics

Distributed Destinations in a Cluster

In a clustered WebLogic deployment, 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 osm_behavior_queue queue has the following:

  • A distributed destination called osm_behavior_queue

  • Two members called oms_jms_server@ms1@osm_behavior_queue and oms_jms_server@ms2@osm_behavior_queue

Table C-3 Queues and Topics Configured for OSM

Name Type JNDI Description

osm_behavior_queue

Queue

mslv/oms/oms1/internal/jms/behaviors

Used to customize task assignment.

osm_cartridge_deploy

Queue

mslv/provisioning/internal/ejb/deployCartridgeQueue

Internal use only.

osm_events

Queue

mslv/oms/oms1/internal/jms/events

Internal use only.

osm_order_events

Topic

mslv/provisioning/external/orderevents

Where order lifecycle events are published.

osm_order_updates

Queue

mslv/provisioning/internal/ejb/orderupdates

Internal use only.

osm_signal_topic

Topic

mslv/oms/oms1/internal/jms/InternalSignalTopic

Internal use only.

osm_ws_cluster_correlates

Queue

oracle/communications/ordermanagement/WebServiceClusterCorrelateQueue

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.

osm_ws_cluster_requests

Queue

oracle/communications/ordermanagement/WebServiceClusterRequestQueue

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

osm_ws_cluster_responses

Queue

oracle/communications/ordermanagement/WebServiceClusterResponseQueue

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.

osm_ws_requests

Queue

oracle/communications/ordermanagement/WebServiceQueue

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

N/A
ErrorQueue Queue oracle/error_queue N/A
Quotas

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

Table C-4 lists and describes the quotas that are configured.

Table C-4 Configured Quotas

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 following connection factories are configured:

  • osm_connection_factory

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

  • oms_events_connection_factory
Destination Key

The following destination key is configured:

  • osmDescendingPriorityDestinationKey

For information about configuring destination keys, see Oracle Fusion Middleware Administration Console Online Help for Oracle WebLogic Server.

JMS Template

A JMS template for the OSM destinations is created. This template applies recommended defaults for the following settings:

  • Redelivery Limit

  • Redelivery Delay

  • Error Destination

The following JMS template is configured:

  • osmJmsTemplate

For information about JMS templates, see Oracle Fusion Middleware Administration Console Online Help for Oracle WebLogic Server.

Data Sources

The following standalone data sources are configured:

  • osm-app-conn-pool-0

  • osm-infra-conn-pool

Users and Groups

This section describes the users and groups that are configured for OSM cloud native.

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.

The OSM cloud native default configuration creates the following accounts in the WebLogic Security Realm.

The following tables list the users, groups, and their descriptions.

Table C-5 Application Accounts

Account Description Assigned Groups

OSM Administrator account

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

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

Design Studio administrator account

The Design Studio administrator account and password for managing OSM cartridges are specified during OSM installation. Two users (deployadmin and sceadmin) are created.

Cartridge_Management_WebService
WebLogic The default administrative account for WebLogic. Administrators

Table C-6 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 run 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.
OSM_USER_manager Manage user accounts
osmEntityClientGroup Entity UI access
osmRestApiGroup OSM REST API
OMS_log_manager Manage log settings

Database Configuration

The OSM DB Installer creates the following database schemas:

  • Core schema

  • Rule engine schema

  • Reporting schema

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

Table C-7 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