This chapter contains the following topics:
This chapter provides an overview of JD Edwards EnterpriseOne OMW configuration and discusses how to select a configuration option.
This section discusses:
JD Edwards EnterpriseOne OMW configuration options.
The configuration process flow.
Project and Object Logging.
Object Save Locations
Object Action Notifications
Application and User Role Security
The JD Edwards EnterpriseOne OMW automates many of the object management tasks users performed manually in previous releases of the software. Much of this automation requires careful configuration by the system administrator through the JD Edwards EnterpriseOne OMW Configuration program.
Use the JD Edwards EnterpriseOne OMW Configuration program to configure these optional features:
|Constants||Enables you to set general constants pertaining to JD Edwards EnterpriseOne OMW projects.|
|SAR System Integration||Enables you to disable SAR system integration with JD Edwards EnterpriseOne OMW and, thus, JD Edwards EnterpriseOne development tools.|
|Logging System||Enables you to specify the project and object events to be logged. In the event that logging fails, you can also disable development or allow development but disable transfers.|
|Object Action Notification||Enables you to enable and disable Object Action Notification, which sends a notification message when an action such as checkin or checkout is performed on an object.|
|Notification Setup||Enables developers to be notified, using subscription, when actions are performed on an object.|
|Activity Rules||Enables you to add and modify project statuses and object transfer activity rules.|
|User Roles||Enables you to maintain user roles.|
|Allowed Actions||Enables you to assign to a user role the actions allowed for each object type during a specific project status.|
|Save Locations||Enables you to add, modify, and delete the locations where you save objects.|
This list provides a recommended process flow for using all of the JD Edwards EnterpriseOne OMW configuration tools. The list contains each configuration function in the process flow, along with the topic in which you can find more information about each function.
Note:These items in the process flow require advance preparation: assigning user roles, applying allowed actions to users, and setting up project status rules and object transfer rules.
Before configuring these functions, make sure you understand user roles, allowed actions, project status rules, and object transfer rules.
This table shows the recommended process flow for JD Edwards EnterpriseOne OMW configuration as follows:
|Configuration Function||Procedure Location|
|Assigning User Roles||See "Configuring OMW Users Roles and Allowed Actions" in the JD Edwards EnterpriseOne Tools Security Administration Guide.|
|Applying Allowed Actions to Users||See "Configuring OMW Users Roles and Allowed Actions" in the JD Edwards EnterpriseOne Tools Security Administration Guide.|
|Disabling SAR Integration with JD Edwards EnterpriseOne OMW||See Configuring JD Edwards EnterpriseOne OMW Functions.|
|Setting Up Project Constants||See Configuring JD Edwards EnterpriseOne OMW Functions.|
|Setting Up Project Status and Object Transfer Rules||See Configuring Activity Rules.|
|Adding, Modifying, and Deleting Object Save Locations||See Configuring Object Save Locations.|
|Controlling Development in the Event of Logging Failure||See Configuring JD Edwards EnterpriseOne OMW Functions.|
|Controlling Logging Detail||See Configuring JD Edwards EnterpriseOne OMW Functions.|
|Enabling or Disabling Object Action Notification||See Creating Notification Subscriptions.|
|Adding, Modifying, and Deleting Notification Subscriptions||See Creating Notification Subscriptions.|
|Viewing Major and Detail Logs||See Working with Logs.|
These two types of activity rules exist:
Project status activity rules
Object transfer activity rules
Project status activity rules define the possible paths for an JD Edwards EnterpriseOne OMW project. For a given project status, these rules define the possible next project statuses to which the project can be advanced.
For each project status activity rule, one or more object transfer activity rules can exist. Each object transfer activity rule defines a FROM and TO location, where objects of this type are moved from and to for a specific software release.
For example, one object transfer activity rule can specify that all APPL objects be transferred from the DV810 location to the PY810 location during a specified project status change.
The Allowed Actions form enables you to assign allowed actions to user roles for each object type during a specific project status. You must create the user role before configuring any allowed user actions.
Using allowed actions, administrators can restrict the actions that users with a specific role can perform.
JD Edwards EnterpriseOne OMW logging tracks information about projects and objects. A major log is created whenever:
A project is created, copied, or deleted.
The project status is changed.
A new or existing object is added to or removed from a project.
An object is created, copied, or deleted.
An object is checked in, checked out, saved, restored, transferred, or retrieved.
For every significant step or event within these actions, the system creates a detail log and attaches it to the major log record.
The Object Management Constants form enables an administrator to set these general constants pertaining to JD Edwards EnterpriseOne OMW projects:
|Type of Constant||Description|
|Project Status for Users' Personal Default Projects||The default status assigned to a default project within the JD Edwards EnterpriseOne OMW. This project constant can be any one of the standard project status codes.|
|Project Status for All New Projects||The status assigned to a project when it is first created. This project constant can be any one of the standard project status codes or you can create a status and code for this purpose.|
|User Role to be Assigned to the Project's Originator||When a project is created, the originator is added as a user on the project. This project constant defines the user role assigned to the originator.|
The Object Save Locations form indicates the save location for Object Librarian (OL) objects. Defining the save location will enable users to transfer objects that are saved into the path code specified. Currently, only the save locations for Object Librarian objects may be defined.
The Object Action Notifications form enables you to activate or deactivate object action notification. The Object Action Notification System sends you an email each time an event, such as check in or checkout, occurs to one of your objects. Object action notification is enabled by default.
The notification system sends email messages to users about changes to objects, such as object check in and checkout, in the system. The Notification Subscriptions form enables you to add, delete, and modify notification subscriptions, as well as to sort notification subscription records by criteria that you select.
You should secure these applications using application security:
P98230 - JD Edwards EnterpriseOne OMW Configuration System
R98210B - Object Management Log Purge
P98231 - JD Edwards EnterpriseOne OMW Transfer Activity Rules Director
You can prevent users from adding a user to a project by using row-level security for the F98221.puJD Edwards EnterpriseOne OMWur field. This field contains the user defined code of the user role for each user in a specific project.
However, all users must be able to add these user roles when setting up a new project:
If these roles are not assigned when a user attempts to perform certain actions on a project, then the actions will fail. The administrator role should be secured from all but a few users. Although you can secure the manager and supervisor roles, you should not. Instead, you should create a role, such as product manager, that can be secured. This new user role can be granted security attributes, such as being allowed to switch a token from one project to another.
You should secure all actions, including project status change, for project statuses 40 (Production Development), 41 (Transfer Production to Prototype), and 42 (Transfer Prototype to Development). These statuses enable administrators to apply fixes to objects in the Production path code and then to promote the objects back to development. The ability to do so should be limited to administrators only.
All configuration options are set up through the JD Edwards EnterpriseOne OMW Configuration System application (P98230). You select the option that you want to configure by clicking the button that corresponds to the desired option.
Select Cross Application Development Tools (GH902) then Object Management Configuration (P98230).
Access the JD Edwards EnterpriseOne OMW Configuration System application.
If necessary, click the General Tab to display function options.
Click one of these buttons to configure the corresponding function:
SAR System Integration
Object Action Notification
Some of the function buttons on the Object Management Setup Form have setting indicators next to them. Settings indicators describe the current setting for the SAR System Integration, Logging System, and Object Action Notification options. The purpose of each setting indicator is as follows:
|SAR System Integration Indicator||Indicates whether the SAR (Software Action Request) system is integrated with the JD Edwards EnterpriseOne OMW. SAR integration is enabled or disabled.|
|Logging System Indicator||Indicates whether full or reduced logging of project or object events is selected.|
|Object Action Notification Indicator||Indicates whether the object notification system is enabled or disabled.|
The H95 CA UDC determines the file type a user can check into OMW while creating business services, and the package prefixes they can select.
To add a new file extension
In EnterpriseOne, type UDC in the Fast Path.
On Work With User Defined Codes, type H95 in the Product Code field.
Type CA in the User Defined Codes field.
In the new row that displays in the grid, complete the following fields:
Codes: Enter the new file extension that you want users to be able to check in.
Type a description of the type of extension you are adding.
The Special Handling and Hard Coded fields are optional.
To add a new package prefix
In EnterpriseOne, drill down to the Object Configuration Management menu.
From the Form exit, click BSSV Package Prefix.
In the blank line at the bottom of the Package Prefix grid, type the new package prefix you want to add.