Refresh the WebLogic domain targets post discovery in the OEM console

Posted on : 30-06-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager targets

Tags: , , ,


The targets that are added in a WebLogic Domain post discovery of the domain as managed target in Enterprise Manager Grid Control, are not known by Enterprise Manager Grid Control until the WebLogic Domain is refreshed. The automatic refresh operation is provided by a job that, by default, runs once a day. Regardless of whether automatic refresh is enabled, someone can manually refresh at any time by using ‘Refresh WebLogic Domain’ from the WebLogic Domain menu.

To do so, login in the Oracle Enterprise Manager Grid Control, go to the “Targets >Middleware” tab:

Select the recently modified WebLogic domain, to which new targets were added, and click on its link name and you will be redirected to the selected WebLogic domain home page. In the left-side “WebLogic Domain” pop-up menu click the “Refresh WebLogic Domain” option:

In the Refresh WebLogic Domain page click “Continue”.
In the Confirmation pop-up page click “Close”:

In the “Refresh WebLogic Domain: Assign Agents” page click “Add targets”. In the next Confirmation page click “Close”.
And in the last – “Refresh WebLogic Domain: Results” page click the “OK” button in the top-right side of the screen.

For further details on this topic please consult the following article on Oracle Support:
How to Enable the “Refresh WebLogic Domain” Job ? [ID 1088537.1]

Update an agent’s time zone when the OS TZ has changed

Posted on : 30-06-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager targets

Tags: , , ,


When changing the time zone on an agent machine, at the operating system level the agent loses the connection with the Oracle Management Server and becomes unreachable:

In order to be able to identify if the server time zone is the actual cause of the agent unreachability issue, one can check for the emagent.nohup log residing in the following folder \sysman\log . If there is a server time zone agent problem related to the OS time changethe latest entries in the above mentioned file should resemble the following lines:

—– Wed Jun 23 11:32:51 2010::Agent Launched with PID 3852 at time Wed Jun 23 11:32:51 2010 —–
(pid=3852): starting emagent version
(pid=3852): emagent started successfully
OMS decided to shutdown the agent because of the following reason sent from OMS: AGENT_TZ_MISMATCH(pid=3852): emagent now exiting abnormally – initialization failure. Consult ‘.trc’ and ‘.log’ files.
—– Wed Jun 23 11:34:39 2010::Pid 3852 not found. reaped=3852, processStatus=14080 —–
—– Wed Jun 23 11:34:40 2010::Checking status of EMAgent : 3852 —–
—– Wed Jun 23 11:34:40 2010::EMAgent exited at Wed Jun 23 11:34:40 2010 with return value 55. —–
—– Wed Jun 23 11:34:40 2010::EMAgent has exited due to initialization failure. —–
—– Wed Jun 23 11:34:40 2010::Stopping other components. —–
—– Wed Jun 23 11:34:40 2010::Commiting Process death. —–
—– Wed Jun 23 11:34:40 2010::Exiting watchdog loop

In order to solve this issue the following actions need to be performed:
Comment the current value of the “agentTZRegion” parameter in the file
\sysman\config\ by adding a hash at the beginning of the “agentTZRegion” line
# agentTZregion=GMT

Run the following commands from the Agent home:
cd \bin
emctl stop agent
emctl resetTZ agent

Open the file AGENT_HOME\sysman\config\ and check whether a new entry for the “agentTZRegion” parameter is added with the new timezone value. Make sure that the new value corresponds to the value set at the operating system level, for example:

Login to the Repository Database as the sysman user through sqlplus or SQL Developer and execute the SQL statement shown in the command output:

SQL> exec mgmt_target.set_agent_tzrgn(‘‘,’Europe/Paris’)
SQL> commit;

Where is : . This can be obtained from the EMD_URL in the AGENT_HOME/sysman/config/ file.

Start the agent:

emctl start agent

For further details on this topic please consult the following article on Oracle Support: Troubleshooting : Grid Agent Configuration: How to Troubleshoot Timezone Issues in Enterprise Manager Grid Agent Setup

The simplest way to patch an OEM agent

Posted on : 30-06-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager targets

Tags: , ,


Login in the OEM Grid Control Console with the a user for which you have previously setup the My Oracle Support connection details and select the Deployments tab:

In the Deployments home page, the Patching Section, click on the “Patch Agent” link:

In the “Patch: Select patch” page fill in the patch number you would like to apply (eg: the one recommended by Oracle (Support) ) and select the platform/operating system version and the language (not always necessary) :

After filling in the patch and the platform click the “Go” button. If you would like find out more details about how to apply the selected patch manually click the “ReadMe” button in the right column of the patch row.
Make sure to mark the patch “Select” Checkbox. Click the “Next” button to proceed with the following patch step.

In the “Patch: Select Destination” field you are required to select the agent that you would like to patch. Here, you are also, able to see the agents that have been already patched with the previously selected update and the ones that are not patched. To do this, one can use the “View” drop-down list, where the following options can be selected: “All Targets”, ”Unpatched Targets” ,”UP targets”.

The selected targets can be chosen for upgrade by using the “Move”/”Move all” links.

After selecting the targets click the “Next” button.
In the next step you are required to fill in the host credentials for the agents to be upgraded.
Click the “Next“ button to proceed to the next step.

In the “Patch: Stage or Apply” step you can leave the default selections and click the “Next” buton:

In the “Patch: My Oracle Support Details” page choose either to de-select the “I wish to receive security updates via My Oracle Support” checkbox or to keep it and click “Next”:

Click “Yes”/ “No”, when asked “Do you wish to remain uninformed of critical security issues in your configuration?”.

In the “Patch: Schedule” step, leave the default selections and click the “Next “ button.

In the “Patch: Summary” step you can see a review of your selections and you can start the patching by clicking the “Finish” button.

In the final “Confirmation” page one can choose to view the status of the job (s) or to “Return” to the Deployments page.

By clicking the “View job” button one can monitor the patching job(s) activity.

The job(s) should complete successfully. If not click the execution link and furthermore the step links to identify the cause of the failure.

The OEM agent patches can be applied also manually/directly on the desired server, but the procedure depends usually on each patch instructions.

PeopleTools Security: Disable automatic account creation while keeping the other attributes(User description, e-mails) in sync

Posted on : 23-05-2013 | By : Elisabeta Olteanu | In : PeopleTools

Tags: , , , ,


The application users would like to disable the option of having PS accounts automatically created upon login as this creates a lot of confusion among employees who, despite the fact that they have not been granted PeopleSoft access, are still able to log into the system using their Windows user ID and password. They would still need to keep the LDAP authentication and the User Profile Map attributes synchronization.

It is known that by disabling the LDAP_PROFILESYNCH PeopleCode function from the Main Menu > PeopleTools > Security > Signon PeopleCode one can inactivate the automatic account creation, but in the same time disabling this function prevents the already existent accounts mail information and user description (attributes) to be synced based on the User Profile Map / Optional User properties.

In order to prevent the PeopleTools accounts from being automatically created, but keep synchronizing the user e-mail and user description User profile Map attributes for the existing users, one can modify the updateUserProfile() PeopleCode method called within the LDAP_PROFILESYNCH function as follows:

If &global_DN <> “” Then
If &bConfigRead = False Then

The modification we made is to add the following check at the beginning of the updateUserProfile function:


PeopleTools 8.53 FSCM9.2: Deploy the Oracle prebuilt virtual machine – easy as 1,2,3

Posted on : 08-05-2013 | By : Elisabeta Olteanu | In : PeopleTools

Tags: , , , , ,


Remember when deploying a PeopleSoft environment could take long hours?

Now it’s no longer the case: with the new pre-defined oracle virtual appliance (.ova) technology, Oracle gives its customers the possibility of familiarizing themselves with the new PeopleSoft tools and application functionalities in the fastest and most comfortable way possible.

These oracle delivered virtual machines allow the creation of PeopleSoft 8.53 Demo Human Capital Management, Enterprise Learning Management, Customer Relationship Management or Financial and Supply Chain Management 9.2 applications in no more than an hour.

In addition, the appliances contain Secure Enterprise Search. SES gives users the ability to search for content across multiple locations, including websites, file servers and enterprise resource planning systems.

The resources prerequisites for such a virtual machine are according to the “Using Oracle VM VirtualBox Appliances for PeopleSoft Applications” documentation the following:

* The hosting system needs to have the Virtual Box utility installed, tool downloadable from here , and a 64-bit processor that can support hardware virtualization (eg: Intel VT). Also, in order to allow PeopleTools client utilities, like Application Designer, Data Mover, etc., the host operating system must be a 64-bit Microsoft Windows version.

*The hosting environment has to be a physical one due to the fact that the PeopleSoft VirtualBox machines are 64-bit and the VirtualBox instance that runs them cannot be run in another virtual appliance.

*The virtual machine requires a minimum of 4 GB available RAM to run, but if planning to configure and start Oracle SES, please consider the additional RAM needs (2GB).

*To start and initialize the virtual appliance 65–80 GB of free disk space are required

The FSCM9.2 virtual machine can downloaded from the PeopleSoft Update Manager Home Page [ID 1464619.1] Oracle Support document:

In order to create one importable appliance from the Oracle provided parts files, run the next command:

After having obtained the final virtual machine file, one can delete the individual part files to help clearing the disk space.

The FSCM9.2 delivered appliance will have the following software characteristics:

After having installed the Virtual Box utility, open it and select the “Import Appliance” option from the File menu:

In the new Import Virtual Appliance window click the “Open appliance” button and select the earlier merged, final ova file:

In the next “Appliance Settings” step choose the name you would like for your VM and select the “Reinitialize the MAC address of all network cards” checkbox.

After clicking the Import button, the operation can take from 15 to 50 minutes, depending on the condition of your hosting drive. “To address possible performance issues caused by fragmentation occurring when writing the large virtual machine disk files, consider defragmenting the Host OS’s hard drive at this point.” (Oracle documentation)

The FSCM9.2 VM disks, once deployed, can take around 54 GB of disk space.

The Virtual Box machine is created with the following configurations:

In the VirtualBox utility, select the FSCM9.2 VM and click the green-arrowed Start button to initialize the setup of the FSCM9.2 appliance. The development Linux environment is going to be deployed with the necessary configurations:

Choose y to continue the FSCM9.2 environment deployment.

During the VM installation, the implementer will be required to provide and confirm the root account password. Following that, one can choose to use a static or dynamic IP address.

Choose the virtual machine hostname you would like to access it as:

To view afterwards the PeopleSoft application, in browser, from the hosting operating system, the hosts file should be modified to reflect the VM IP and the name chosen for the FSCM9.2 environment:

For the PeopleSoft database name you can choose either to change it or keep the default naming. Once the database has been configured, the application server, PIA and Process Scheduler will be configured and started. The next step is to choose whether or not you would like Oracle Secure Enterprise search installed:

Once the SES configuration is completed, which can take a longer time taking into consideration the SES crawling process of the search index, the application can be accessed from the browser, by using the VP1 user and its corresponding VP1 password.

In the predefined FSCM9.2 virtual machine everything comes configured, from process scheduler to report nodes, integration broker and its nodes, search instance, etc.

The Secure Enterprise Search can now be used to return the desired results using the facets filtering, advanced search and get related actions.

One of the things that does not come setup by default is the Web Profile Authentication Domain and the Help URL. The Help link can be configured by setting the link on the web profile as described here (
In this case the PeopleBooks URL I setup is the one provided by Oracle:

Remember to restart your web server before performing further tests.

PeopleTools 8.53: Why upgrade?

Posted on : 08-05-2013 | By : Elisabeta Olteanu | In : PeopleTools

Tags: , , ,


PeopleTools 8.53 is the most recent version of PeopleSoft’s core engine. Oracle announced the following PeopleTools versions will be released every 12 to 18 months. In parallel, a new application version should be available every 3 years and followed by 2 application feature packs. The latest application version is 9.1 Feature Pack 2 and has been available since February 2012. The newest PeopleSoft application release – FSCM 9.2 – will include significant upgrades to both General Ledger and Treasury Management components, as well as Source to Settle (Supply Chain) upgrades.

PeopleTools 8.53 has been released 1 month ago (February 2013) and it includes two corrective patches, while the following cumulative update (8.53.03) is expected to be delivered by Oracle in April 2013.

Oracle fixed, improved or introduced 715 features between PeopleTools 8.49 and PeopleTools 8.53. This only covers technical enhancements and does not take into consideration the application/functional features brought by the newest version (FSCM 9.2).
This 8.53 release is also certified to run on the latest versions of Oracle RDBMS, Windows & Linux O/S and 3rd-party software, each of those including hundreds of security and performance enhancements for each layer of the ERP system.

Major PeopleTools enhancements are described in detail in the following sections.

  • Dashboards and WorkCenters

     Introduced with PeopleTools 8.52 the Related Actions Framework is a feature consisting in a menu of actions or options that are contextually appropriate to the user’s role and particular data presented on the application screen.
     PeopleTools 8.53 brings Related Actions to Pivot Grids, allowing users to take actions directly on data displayed in a pivot grid.
     This release gives the application developers and designers the possibility to deploy dashboard-like pagelets within WorkCenters to provide better decision support for WorkCenter transactions.
     Applications can now consume remote pagelets in WorkCenters, Homepages, and Dashboards.
     Improves the overall decision-making process by embedding more relevant business intelligence into the work centers .

  • Activity guides

     Activity Guides allow application designers to define processes that guide users through a series of predefined actions. This functionality can be used for managing process-specific tasks, such as period-end-close in Financials Management.
     With PeopleTools 8.53, the Activity Guide enables application developers to define a list of action items tied to transactional, collaborative, or manual tasks. The action item represents a task that can be tracked for assignment and completion, and is secured by roles and user lists. Activity Guides also offer the possibility of creating a hierarchical list of action items.
     A new Activity Guide WorkCenter template is available for use with building and configuring Activity Guides .This template provides features like activity progress status track and highlight of the current action item, ability to do pre-processing and post-processing for an action item, dependency rules definition and action items roles and users assignation, all of these bringing a whole new level of user experience.

  • PeopleSoft Application Search

     A search experience that functions similarly to the internet, providing a look and feel that users will find both familiar and intuitive.
     The ability to use filters and facets to narrow result sets, allowing users to navigate to the desired application content.
     Search results that display in prioritized order by relevance based on the provided search terms.
     Decreased response times and optimized query executions by running parallel requests.
     New file and web-based search definition types that enable end-user search features, such as searching documentation of business processes.
     Related Action menus that are embedded directly in the search results, allowing users to navigate straight to specific related transactions, pre-populated with the selected search results data.
     Control over how the system deals with duplicate search results.
     The framework can be configured to span multiple PeopleSoft applications.

  • Interaction Hub

    The Interaction Hub is a set of features designed to aggregate content from multiple PeopleSoft applications, and to unify the user experience of those environments. Whether supporting one PeopleSoft application or many, the hub can be used to provide users access to all PeopleSoft content through a web site based user interface.

     Easily create business focused collaborative workspaces that empower users to work closely on projects, as virtual teams.
     Ability to establish a common homepage across multiple PeopleSoft applications.
     The hub offers a common navigation interface for multiple applications.

  • Analytics and reporting

     The pivot grid feature gives users the possibility to quickly and easily pivot and filter data within PeopleSoft applications without having to export data to Microsoft Excel.
     Multi Select Filters that provide the ability to filter data on multiple values instead of a single value.
     Progressive Filtering that shows only valid values for the current filter selection when a filter value is modified.
     Enabling of Pivot Grid pagelets to interact with each other and with transaction pages. Prompt and filter value changes can be published and subscribed to in real-time.
     The Pivot Grid Administration Component provides module to clone and delete Pivot Grid Models and personalization.
     Beginning with the People Tools 8.53 release, the Reporting Console can be used to import Favorites bookmarks from another user.
     Drag-and-drop of folders and Process Bookmark as a sibling or as a child of an existing folder.
     Dynamic Context Menu option on folder and Process Bookmark row for add, edit, rename, delete options.
     PeopleTools 8.53 delivers a number of charts enhancements, including making use HTML, CSS3, and JavaScript instead of the server-based chart engine, allowing a much faster process of chart instantiation and finally improving the user experience.
     The new charts incorporate improvements in scrolling and display and more closely match the overall PeopleTools look and feel.

  • PeopleTools Documentation

     The PeopleSoft workflows’ graphical Business Process Maps (BPM) are now integrated and accessible from within the online help documentation.
     Starting with PeopleTools 8.53, the PeopleSoft help solution offers a modern, website-oriented user interface, that allows embedding media such as feature demonstration videos and audio files.

  • Integration technology

     PeopleTools 8.53 introduces an integration network node and a corresponding registration page, to facilitate the nodes identification and definition process across the remote databases network.
     The latest tools version enables the set up of automated network integration processing verification for around-the-clock monitoring and notification.
     Improved control over Integration Broker messages segmentation, through a built-in global parameter that determines the maximum number of segments that can exist in a message.
     Implements a bulk change mechanism for a faster administration of similarly configured network nodes, routings or service names.

  • Security Features

     PeopleTools 8.53 lays the foundation for a secure-by-default installation so that products install, out of the box, into a secure state.
     This feature prompts the installer for site-specific passwords for delivered user accounts during the installation process.
     PeopleTools 8.53 incorporates the SALT cryptography technology which increases the hash complexity and provides additional mitigation for brute force and denial-of-service attempts.

  • Performance features & Platform technologies

     Beginning with PeopleTools 8.53, the Application server and Process Scheduler server are now 64-bit applications, taking full advantage of the 64-bit server architecture.
     A good way to extend the usable life of production hardware is to offload work to stand-by servers whenever possible. PeopleTools 8.53 enables the use of Oracle Golden Gate to provide the ability to offload read-only processes from an Oracle production database to a stand-by Oracle database, including: PS/nVision reports, report drill downs and report books.
     A PeopleSoft Oracle Virtual Machine (OVM) template is a pre-packaged, ready-to-run PeopleSoft Middle-Tier environment which gives functional teams the possibility to assess the features and changes offered in newer releases of PeopleSoft applications or to identify new 3rd party products and other runtime requirements.
     Mozilla has introduced Extended Support Releases (ESRs) for the Mozilla Firefox browser, which Oracle fully embraces with PeopleTools 8.53.

  • PeopleSoft Update Manager

    With PeopleSoft Update manager Oracle introduces a new methodology and tool for applications maintenance. PUM gives, through the custom change package, the possibility to select and apply specific object modifications, bundles or maintenance packs, without having to worry about any prerequisite updates. This significantly reduces the time and effort for analysis and preparation, patching, and patching verification and validation.

     Oracle has implemented a mechanism of releasing full, cumulative, ready to use working PeopleSoft environments for the applications pillar with the most up to date fixes.
     Ability to extract updated objects from the most current PeopleSoft Update image.
     Provides the ability to get current on all updates at once.
     Offers the possibility of searching for specific fixes by bug ID or by specific object references.
     Can generate change packages where each distinct object is called out only one time and applied only one time in the correct sequence.
     Includes automatically all the necessary requisites and updates.

  • Optimized PeopleSoft Test Framework

     Enables testers to execute more tests with greater accuracy during a shorter time.
     The Test Details Report has been streamlined.
     Ability to select more than one and less than all tests for all reports.
     The new PTF offers context-sensitive help for construction parameters. The user can click in the recognition field of a step action and a dialog box with the parameters for the step action is displayed.
     The Check Syntax option allows a user to quickly validate the parameters provided in their steps either on save or on demand prior to execution.

  • Data Migration Workbench

    The Data Migration Workbench is a new tool that helps administrators manage the process of moving configuration data from one system to another. Using this tool will result in significant improvements to the consistency of configuration between various PeopleSoft application systems. All this is done with quality control and approval checks in place.

     The DMW tool assists with defining conditions for extraction of the data in preparation of migration, migrate or import data to one or more target systems, compare and validate source data against target data, making all this accessible and easily manageable from the PIA.
     Various control checks and a comprehensible validation report page have been implemented to allow a clear picture of all the configuration modifications prior to their migration.

  • PS Change Assistant Enhancements

     Provide the ability to add ad-hoc step filtering criteria to a template in order to improve the applicability of a job to the customer and where possible remove unnecessary manual steps.
     Users will be able to quickly and easily compare SQL and XSLT and PeopleCode objects from three different databases and create one merged version. Users can apply rules individually or in batch as they review, analyze, and modify the code before they move their code to the new database.

  • OEM PeopleTools 8.50.11 targets get unlinked in the OEM Grid Control console

    Posted on : 13-02-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager targets

    Tags: , , ,


    When adding new PeopleTools 8.50.11 targets some of the already existent, or the newly added PeopleTools 8.50.11 targets become unlinked, they appear in the Unlinked targets section in the the PeopleSoft plugin tab.
    It can be noticed that this problem cannot be solved by refreshing the OEM PeopleSoft Database target configuration and patching as it should normally function:

    Before proceeding with further investigations, one must make sure that the PeopleSoft environments GUIDs are different for all the environments discovered within the PeopleSoft plugin.
    Also, while encountering this issue in the OEM Console PeopleSoft tab, the following kind of errors will be logged in the next emoms.trc OMS log residing in the following folder /em/EMGC_OMS1/sysman/log/.

    2012-05-25 04:39:41,279 [XMLLoader0 80000020639.xml] ERROR loader.XMLLoader LoadFiles.792 – Error while processing 80000020639.xml:
    java.sql.SQLException: ORA-20801: ECM load failed: Metadata does not exist for target type ps_app_db and snapshot type GetConfig
    ORA-06512: at “SYSMAN.ECM_CT”, line 324
    ORA-06512: at line 1
    ORA-06512: at “SYSMAN.EMD_LOADER”, line 5229
    ORA-06512: at line 1
    at oracle.jdbc.driver.SQLStateMapping.newSQLException(
    at oracle.jdbc.driver.DatabaseError.newSQLException(
    at oracle.jdbc.driver.DatabaseError.throwSqlException(
    at oracle.jdbc.driver.T4CTTIoer.processError(
    at oracle.jdbc.driver.T4CTTIoer.processError(
    at oracle.jdbc.driver.T4C8Oall.receive(
    at oracle.jdbc.driver.T4CCallableStatement.doOall8(
    at oracle.jdbc.driver.T4CCallableStatement.executeForRows(
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
    at oracle.jdbc.driver.OraclePreparedStatement.execute(
    at oracle.jdbc.driver.OracleCallableStatement.execute(

    1. Remove all PeopleSoft DB & App Server targets from EM console. Stop the OMS and the agent.
    2. Take a backup of the following SQL scripts – MGMT_PSEM_ECM_PS_APP_DB.sql & MGMT_PSEM_ECM_PS_APP_PTC.sql – found under the directory – OMS_HOME/sysman/admin/emdrep/sql/psem/latest
    3. Edit the following statements in the below SQL scripts:
    a) Uncomment the below line:
    b) Change the snapshot type to “GetConfig” in the below SQL statements:
    VALUES (‘GetConfig’, ‘ps_app_db’, ‘L’, metadata_id, ‘Database Configuration’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, NULL, NULL, NULL, NULL, NULL, NULL, NULL, ‘H’);
    VALUES (‘GetConfig’, ‘ps_app_db’, ‘P’, metadata_id, ‘Database Configuration’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, NULL, NULL, NULL, NULL, NULL, NULL, NULL, ‘H’);

    a) Uncomment the below line:
    b) Change the snapshot type to “GetPatch” in the below SQL statements:
    VALUES (‘GetPatch’, ‘ps_app_db’, ‘L’, metadata_id, ‘Patch Configuration’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, NULL, NULL, NULL, NULL, NULL, NULL, NULL, ‘H’);
    VALUES (‘GetPatch’, ‘ps_app_db’, ‘P’, metadata_id, ‘Patch Configuration’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, ‘Y’, NULL, NULL, NULL, NULL, NULL, NULL, NULL, ‘H’);

    4. Connect to EM repository as sysman user and run the below SQL scripts:

    5. Restart the OMS & Agent. Try re-discovering the PeopleSoft database and application server targets.
    6. Check the Configuration tab on the PeopleSoft DB target instance to see if it has retrieved any information under the Additional Properties & Installed Patches sections.

    Oracle Enterprise Manager Grid Control metric to check how many specific processes are running on a machine at a time

    Posted on : 13-02-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager metrics

    Tags: , , , ,


    In order to define a OEM host target user defined metric, one should log into the Grid Control instance, go to the Hosts tab, select the host whose processes one would like to check and in the right- bottom area of the selected host target Homepage, click the User Defined Metrics link, and then click the Create button.

    For example, if one wants to check how many PeopleSoft Application Server processes are running at a time on a host monitored through OEM, one can create a perl script, containing the following commands:

    use Win32::OLE(‘in’);

    use constant wbemFlagReturnImmediately => 0×10;

    use constant wbemFlagForwardOnly => 0×20;

    $computer = “.”;

    $objWMIService = Win32::OLE->GetObject

    (“winmgmts:\\\\$computer\\root\\CIMV2″) or die “WMI connection failed.\n”;

    $colItems = $objWMIService->ExecQuery

    (“SELECT * FROM Win32_Process”,”WQL”,wbemFlagReturnImmediately | wbemFlagForwardOnly);

    my $a=0;

    foreach my $objItem (in $colItems)


    if (lc($objItem->{Caption}) eq “psappsrv.exe”) {



    print “em_result=$a”;and then reference the script name in the the metric definition page.

    Oracle Enterprise Manager will read the metrics’ values based on the values that the em_result variable will take. OEM will use, for the perl script execution, the perl installation that comes with the agent setup on the monitored host. In the Operating Systems credentials section remember to fill in the user and the password that oem will use to connect to the host and execute the script.

    At the bottom of the User defined metric page one can fill in the metric’s Warning and Critical Thresholds and can adapt the subject of the alert e-mail.

    After having saved the metric, one should set a grid control notification rule and subscribe the account used for notification purposes to the rule.

    Oracle Enterprise Manager Grid Control metric for PeopleSoft Integration Broker transactions in New Status

    Posted on : 12-02-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager metrics

    Tags: , , ,


    There can be times when we face various Integration Broker issues (inactive IB domains/nodes/routings,the queue was blocked by a previous transaction that had a status of RETRY, ERROR, or TIMEOUT,etc.) that could cause future IB messages/transactions to remain in “New” status.
    If the corresponding PeopleSoft database instance is monitored by a OEM Grid Control environment, one can create a database user defined metric to constantly check the IB transactions that are stuck in “New” state. To do so, log in into your Grid Control instance, go to the Database tab, select the PeopleSoft database whose IB messages you would like to monitor, and in the right- bottom area of the selected OEM database target Homepage, click the User Defined Metrics link, and then click the Create button.

    In the User Defined Metric page, in the Defintion area, SQL Query textbox, type the statement that will run as a check:

    In the Database credentials section, remember to fill in the user and password that the script/statement will use to connect to the previousy selected database target. At the bottom of the User Defined SQL metric page one can fill in the metric’s Warning and Critical Thresholds and can adapt the subject of the alert e-mail.

    After having saved the metric, one should set a grid control notification rule and subscribe the account used for notification purposes to the rule.

    Have a clearer picture of your PeopleSoft trace files with the Trace Magic Tool

    Posted on : 28-08-2012 | By : Elisabeta Olteanu | In : Other

    Tags: , , , ,


    The TraceMagic PeopleSoft tool is intended for the PeopleSoft administrators, support engineers and developers and it offers the possibility of dissociating the PeopleSoft trace information based on the following type of trace categories: SELECT Statements, DELETE Statements, INSERT Statements, UPDATE Statements, Events, External Calls and Internal/External Calls.
    Also , the SQL Statements can be analyzed in bulk samples or categorized by commands with unique WHERE clause or unique FROM Clause.

    The tool is quite easy to install, but it is limited to Windows machines that have .NET framework installed on them.
    As soon as you have downloaded the zip containing the tool from Oracle Support, de-archive it and execute the Trace Magic ClickOnce Application Deployment Manifest or the setup.exe application installer. This will create the following structure in you Start menu : Oracle Corporation > Tools & Utilities , from where you will be able to access the Trace Magic tool.

    The application provides, in addtion, a Total tab which reflects the time spent, in the analyzed trace file, per each type of operation.

    For further details, consult the following Oracle support article: TraceMagic: Utility for analyzing *.tracesql trace files [ID 1470578.1]