![]() ![]() ![]() ![]() ![]() ![]() |
This section contains information on the following subjects:
In releases of Oracle Enterprise Repository prior to Oracle Enterprise Repository release 3.0, the asset registration process required the registrar or advanced submitter to manually initiate and monitor the registration process. The required information was gathered and entered on the appropriate tabs in the Asset Editor. The registrar examined each tab and monitored the workflow. When information for a specific stage of the workflow was acceptable, the registrar approved the data on the appropriate tab. The registrar also had the option to edit any of the information for any stage of the process. The manual process of registering assets is described in the Oracle Enterprise Repository Registrar Guide.
The introduction of Advanced Registration Flows in Oracle Enterprise Repository 3.0 automated the manual asset registration process by providing a set of predefined flows designed to automate a set of common Oracle Enterprise Repository asset registration tasks, such as asset submission, acceptance, registration, and other governance processes.
In this release, the synchronization of Oracle Enterprise Repository and Oracle Service Registry using the Oracle Registry Repository Exchange Utility has also been automated. To learn more about the Oracle Registry Repository Exchange Utility, refer to the Oracle Enterprise Repository Oracle Registry Repository Exchange Utility manual.
To accomplish this, Oracle Enterprise Repository includes an embedded, JMS-based event engine that manages the flow of Oracle Enterprise Repository asset registration events, in the form of Web Service events. These events trigger the pre-defined flows. Once installed, the Advanced Registration Flows can be run out-of-the box or can be tailored to suit your environment.
Note: | The flows do not have their own user interface, but will automate certain asset metadata and state changes in the background based on particular Oracle Enterprise Repository events. |
For ease of use, Oracle Business Process Management is included with your purchase of Oracle Enterprise Repository. You can use Oracle Business Process Management to modify existing workflows that are supplied with Oracle Enterprise Repository and implment new Repository-centric workflows. You can use the predefined Oracle Business Process Management endpoint or create your own Web Service endpoints to subscribe to Oracle Enterprise Repository events. There are also event monitoring and logging tools for troubleshooting and tuning purposes.
You install the Advanced Registration Flows during an Oracle Business Process Management installation. After installing the Advanced Registration Flows, you manually deploy them by following the steps in “Installing Oracle Business Process Management for Advanced Registration Flows” in the Oracle Enterprise Repository Installation Guide.
In previous releases, the asset acceptance, assignment, registration processes required multiple registrars to manually initiate and monitor the process from end-to-end via numerous emails. In some cases, there was only one registrar that was notified about the newly submitted assets, and as a result, the registrar could be overloaded with emails about new assets.
The Community flow provides a way to automate the asset acceptance, assignment, and registration process by allowing the configuration of automated assignment rules and also introduces the notion of federated registrars among different authorities. Rather than spamming many registrars across all communities (through the system registrar notification), you can limit the system registrar to one or a few individuals, and let the Automatic Acceptance flow accept assets on behalf of a registrar-of-record for the community. The Community flow feature can distribute asset submissions to those with the authority to approve them for the community.
For example, you can add two communities and configure two different registrars responsible for each community. Then, depending on the producing projects or asset types, certain assets can belong to a community. The Community flow automatically accepts such assets in the same way it would be manually accepted by a registrar.
Advanced Registration Flows includes the following software components:
The Event Manager emits asset registration events in the form of Web Service messages. These events trigger pre-built flows that automate Oracle Enterprise Repository asset submission, acceptance, registration, and other governance processes. See Configuring the Oracle Enterprise Repository Event Manager.
The Subscription Manager is XML-based configuration file that is responsible for managing the event subscriptions by the Web Service endpoints (either the predefined ALPBM endpoint or user-defined endpoints) where matched events will be delivered. The Event Manager uses the EndPointEventSubscription.xml
file to load information about the endpoints where events need to be delivered. See Configuring the Oracle Enterprise Repository Event Manager.
The Event Manager uses an embedded version of Apache ActiveMQ JMS Server that is enabled by default. The embedded JMS server is configured to run out-of-the-box without any additional configuration. However, you can also configure the Event Manager to use an external JMS server, such as Weblogic Server JMS or IBM MQSeries. See Configuring JMS Servers for Oracle Enterprise Repository.
A tool to monitor the events that are generated by the Event Manager. The Event Monitor peeks into the event traffic and prints information, such as the event body and event properties. See Monitoring and Managing Events.
Oracle Business Process Management is included with your purchase of Oracle Enterprise Repository. You may use Oracle Business Process Management to modify existing workflows that are supplied with Oracle Enterprise Repository and implement new Repository-centric workflows.
The Advanced Registration Flows can be run out-of-the box or can be tailored to suit your environment. See Configuring Advanced Registration Flows.
There are event monitoring and logging tools for troubleshooting and tuning purposes.
The Oracle Business Process Management Process Execution Administrator actively manages the orchestration of asset registration events in the form of Web Service messages. For more information, see Administering Oracle Business Process Management Web Applications.
The Oracle Business Process Management Log Viewer enables you to read information logged by the Process Execution Engine. A set of log files is created for each project you define. The Studio Log Viewer reads the files and displays them to help you monitor and trace Engine execution. For more information, see Using The Oracle Business Process Management Log Viewer.
The Automated Registration Flows automatically send email notifications under many circumstances. Administrators can customize the email subject, body, etc., the same way as other email templates. See Customizing Email Notification Templates.
There are workflow configuration tools for generating new configuration file, refreshing exisiting files, and encrypting passwords. For more information, see Monitoring and Managing Events.
Oracle Enterprise Repository administrators may need to configure and customize flows because there will be new asset types, projects, categorizations, etc. The Generate Config XML tool connects to Oracle Enterprise Repository and creates a new file that can be customized.
The Refresh Config XML tool lets you to refresh a Config XML file without restarting the Event Manager.
The security Encrypt Password tool lets you to encrypt the passwords for security reasons.
![]() ![]() ![]() |