Order and Service Management (Communications Industry) (MOSC)

MOSC Banner

Before OSM goes into production - the checklist

edited Jun 12, 2014 9:18AM in Order and Service Management (Communications Industry) (MOSC) 1 comment

Recently I saw several OSM productions and they have some major issues, these issues were caused by poorly configured OSM.

As a lesson and learn practice, this thread is created and hopefully  it can offer some help before you put OSM into production

  1. Check OSM Servers log file,

WLS Server should be started with following settings in addition to other settings

-server

-verbose:gc

-Djava.io.tmpdir=different_directory_for_different_server

-Djava.awt.headless=true

Optionally

-d64

Please give at least 4GB heap to OSM WLS Servers

  1. Check OSM WLS domain console

All OSM internal JMS queues should have the following settings

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center