Author: Eunjoo Lee, Principal Product Manager, Oracle
Oracle Enterprise Manager Applications Management team is pleased to announce
the release of their latest whitepaper (available here)
and associated screenwatch (available here)
on configuration management for Siebel.
task of managing configuration parameters in a dynamic, multi-target environment
can be extremely challenging. A large, production scale environment can
have dozens of unique targets, and each target can have several hundred
different configuration parameters.
Enterprise Manager 12c, with the Siebel Plug-in, provides advanced,
out-of-the-box tools to manage the complexity of Siebel configuration
management. Oracle Enterprise Manager has advanced configuration capture,
change detection, and comparison reporting capabilities that can dramatically
reduce the amount of time that System Administrators spend on configuration
purpose of the whitepaper and screenwatch is to provide customers with
details on Oracle’s Best Practices for managing Siebel Configurations.
It addresses several key areas including;
comparison templates in Oracle Enterprise Manager
configuration templates for Siebel servers, components groups, and components
configuration templates to compare Siebel servers
of configuration comparison results
configuration templates for Siebel patch analysis
of using configuration templates to manage Siebel applications are substantial,
compare configuration parameters for targets within a Siebel Enterprise,
or between two different Siebel Enterprises
compare configuration parameters for a Siebel target against a gold
standard or baseline.
comparison reports once and re-run multiple times
this white paper and screenwatch help to provide you with a good starting
point to manage your Siebel Application configurations more efficiently
Contributed by Eunjoo Lee, Product Manager, Oracle Enterprise Manager.
Service Level Management, or SLM, is a key tool in the proactive management of any Oracle Packaged Application (e.g., E-Business Suite, Siebel, PeopleSoft, JD Edwards E1, Fusion Apps, etc.). The benefits of SLM are that administrators can utilize representative Application transactions, which are constantly and automatically running behind the scenes, to verify that all of the key application and technology components of an Application are available and performing to expectations.
A single transaction can verify the availability and performance of the underlying Application Tech Stack in a much more efficient manner than by monitoring the same underlying targets individually.
In this article, we’ll be demonstrating SLM using Siebel Applications, but the same tools and processes apply to any of the Package Applications mentioned above. In this demonstration, we will log into the Siebel Application, navigate to the Contacts View, update a contact phone record, and then log-out.
This transaction exposes availability and performance metrics of multiple Siebel Servers, multiple Components and Component Groups, and the Siebel Database - in a single unified manner. We can then monitor and manage these transactions like any other target in EM 12c, including placing pro-active alerts on them if the transaction is either unavailable or is not performing to required levels.
The first step in the SLM process is recording the Siebel transaction. The following screenwatch demonstrates how to record Siebel transaction using an EM tool called “OpenScript”. A completed recording is called a “Synthetic Transaction”.
The second step in the SLM process is uploading the Synthetic Transaction into EM 12c, and creating Generic Service Tests. We can create a Generic Service Test to execute our synthetic transactions at regular intervals to evaluate the performance of various business flows. As these transactions are running periodically, it is possible to monitor the performance of the Siebel Application by evaluating the performance of the synthetic transactions.
The process of creating a Generic Service Test is detailed in the next screenwatch. EM 12c provides a guided workflow for all of the key creation steps, including configuring the Service Test, uploading of the Synthetic Test, determining the frequency of the Service Test, establishing beacons, and selecting performance and usage metrics, just to name a few.
The third and final step in the SLM process is the creation of Service Level Agreements (SLA).
Service Level Agreements allow Administrators to utilize the previously created Service Tests to specify expected service levels for Application availability, performance, and usage. SLAs can be created for different time periods and for different Service Tests.
This last screenwatch demonstrates the process of creating an SLA, as well as highlights the Dashboards and Reports that Administrators can use to monitor Service Test results.
Hopefully, this article provides you with a good start point for creating Service Level Agreements for your E-Business Suite, Siebel, PeopleSoft, JD Edwards E1, or Fusion Applications.
Enterprise Manager Cloud Control 12c, with the Application Management Suites, represents a quick and easy way to implement Service Level Management capabilities at customer sites.