Thursday, March 20, 2014

EM12c: EMSYSTEMEXCEPTION ON UI WHILE CREATING JAVA EE APPLICATION IN SW LIBRARY

In EM 12.1.0.3, when trying to upload a J2ee Application Component to software library, it shows status as incomplete and oracle.sysman.emSDK.app.exception.EMSystemException can be seen on UI.

emoms.log shows following associated exception:
Caused by: java.sql.SQLException: ORA-20406: The following targets are invalid: em-oms.example.com
ORA-06512: at "SYSMAN.EM_JOB_OPS", line 290
ORA-06512: at "SYSMAN.GC_JOB", line 29
ORA-06512: at line 1
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)  
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)

---
---

Cause: It turns out that if the OMS virtual host name is different from physical host name, that caused this issue.

Solution: This is a product bug, there is no fix AS OF NOW. But there is a workaround, not the best solution but to proceed further, it helps.

To workaround the issue, one can push another agent on oms host with same physical name. This will resolve the virtual host vs physical host conflict.
Now upload the J2ee Application Component to software library, it will be successful.

Once the J2ee App has been uploaded. One may stop the agent and bring it up only when its needed again. Else it can add some overhead to existing resources.

Tuesday, February 11, 2014

EM12c: Weblogic host is up, but EM doesn't show metric data (ORA-01882)

Issue: On EM12c, Weblogic Server is discovered successfully. On EM12c UI, one can see various middleware targets and their respective availbility status. But when one wants to see the details metrics like Servlets and JSPs metrics or Work Manager etc. It shows 'Unavailable' as shown in screenshot below:



Also  when one looks at emoms.log with DEBUG level on, one see following error:

2014-01-25 18:53:04,015 [53::[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG as.ServerHomeDeploymentsModel logp.251 - Error getting metrics for the application deployments table
oracle.sysman.emSDK.app.exception.EMSystemException
at oracle.sysman.emas.sdk.model.metric.ReposMetricProvider12.queryMultiMetricsByAssocOneQuery(ReposMetricProvider12.java:529)
at oracle.sysman.emas.model.as.ServerHomeDeploymentsModel.setupMetricBatchProvider(ServerHomeDeploymentsModel.java:198)at oracle.sysman.emas.model.as.ServerHomeDeploymentsModel.setDeployments(ServerHomeDeploymentsModel.java:517)

Caused by:
java.sql.SQLDataException: ORA-01882: timezone region not found
ORA-06512: at "SYSMAN.MGMT_GLOBAL", line 8

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)



In this case, agent is working fine and collecting all data, passign to OMS. Where entire metric data is getting collected in EM repository. However, this is an OMS UI side issue, where due to difference in Timezone of agent and host, OMS is not showing the metric data.

Solution: Set the TimeZone before starting OMS server.
One can set timezone at OMS host at host/user level .At host level would be ideal.
Use following example to start the timezone:

%$OMS_HOME/bin/emctl stop oms
 

%export TZ=PST8PDT
 

%$OMS_HOME/bin/emctl start oms

Friday, January 31, 2014

EM12c: How to deploy JVMD agent on EBiz 12.1 (oc4j based instance) ?

E-Business 12.1 has Oracle iAS based tech stack. It has oc4j as its application server.
EM12c doesn't have any automated UI flow for deploying JVMD agent on oc4j server.
That deployment has to be manual.

Manual JVMD deployment is referred in this doc

Download JVMD agent file from EM12c UI as given here

1. In EM Cloud Control, Select Setup menu-> Middleware Management-> Application Performance Management.

2. On the Application Performance Management page, select JVM Diagnostics Engine.

3. Click Configure. The 'JVM Diagnostics Setup' page appears.

4. On the 'JVM Diagnostics Setup' page, click JVMs and Pools, then click Download.

5. From the JVMD Component menu, to download jamagent.war. From the JVMD Component menu, select JVMD Agent, then click OK. The JVM Diagnostics Agent web.xml parameters dialog box appears.

6. From the Available Engines menu, select a JVMD engine from the list, then click Download.
  
7. Click Download to download jamagent.war.


Due to some changes in EBiz 12.1 iAS, it requires some additional steps for JVMD agent deployment. EBiz12.1 oc4j doesn't have its own admin web console, so one needs to deploy JVMD agent using command line utility like admin_client.jar.  That requires resetting oc4jadmin password for oafm and oacore  etc.

Given steps can be used as workaround for JVMD agent deployment on oc4j. Not sure if one would like to use these steps in a Production env. Take your call.

a. To reset oc4jadmin password for oafm and oacore
edit the following files:
/oracle/r12/VIS12/apps/tech_st/10.1.3/j2ee/oafm/config/system-jazn-data.xml
/oracle/r12/VIS12/apps/tech_st/10.1.3/j2ee/oacore/config/system-jazn-data.xml

look for the <credentials> section under OC4J Administrator
replace the encrypted password e.g. {903}xxxxxxxxxx with a new plaintext e.g. !welcome1
(new plaintext must begin with a !)

Also modify the opmn config file, to disable SSL and allow remote connections
edit:
/oracle/r12/VIS12/apps/tech_st/10.1.3/opmn/conf/opmn.xml
change the <notification-server> section so it looks something like this
   <notification-server interface="ipv4">
      <ipaddr remote="0.0.0.0" request="0.0.0.0"/>
      <port local="17006" remote="17007" request="17005"/>
      <ssl enabled="false" wallet-file="$ORACLE_HOME/opmn/conf/ssl.wlt/default"/>
   </notification-server>
(add the line with <ipaddr...> and change <ssl enabled="true"...> to false)


b.  Use following command to deploy JVMD agent
java  -jar /oracle/r12/VIS12/apps/tech_st/10.1.3/j2ee/home/admin_client.jar
 deployer:oc4j:opmn://linux-ebs-r12-pc.us.oracle.com:6501/oafm oc4jadmin welcome1
-deploy -file /tmp/jamagent.war -deploymentName jamagent -bindAllWebApps


or
 
java  -Djava.util.logging.config.file=logging.properties   -jar
/oracle/r12/VIS12/apps/tech_st/10.1.3/j2ee/home/admin_client.jar
 deployer:oc4j:opmn://linux-ebs-r12-pc.us.oracle.com:6501/oafm oc4jadmin welcome1 -deploy -file /tmp/jamagent.war -deploymentName jamagent -bindAllWebApps

Friday, October 18, 2013

EM12c: Service Management (Synthetic Monitoring) White Paper

Oracle EM12c cloud control provides a comprehensive monitoring solution for IT organizations to achieve high availability, performance and optimized service levels for their business services. EM's service management solution allows you to actively monitor and report on the availability and performance of a wide variety of services, including end users business functions (mail infrastructure, network and database services), web applications, Oracle Apps etc.. Using synthetic transactions one can monitor services from end users perspective.

To understand Service management, Service Definition, Service Test (using ATS), System, Service Level Agreement, Service Dashboard etc., pl refer the Service Management White Paper

http://www.oracle.com/technetwork/oem/soa-mgmt/wp-servicemanagment-em12c-2028666.pdf

Monday, July 29, 2013

EM12c: What's new in Fusion Middleware Plug-in 12.1.0.4?

With EM PS2 (12.1.0.3) release, FMW plugin 12.1.0.4 has been released.
Main features of this plugin are listed below:

SOA Management Features

Enhancements to SOA Fault Management
SOA administrators can now perform comprehensive fault management directly from Enterprise Manager Cloud Control, including search and single and bulk fault recovery. This new feature replaces all of the previous faults and reject messages tabs and regions at the composite level with the top-level search and resubmit.

RAC support for SOA Dehydration Monitoring
SOA Dehydration store monitoring in Enterprise Manager Cloud Control now supports RAC databases.

Monitoring and Diagnostics Features
Enhancements to Auto Discovery for Oracle Fusion Middleware and WebLogic DomainsManagement Agent-based auto discovery for Oracle Fusion Middleware is now enabled automatically with Oracle Enterprise Manager Cloud Control 12c. In addition, administrators who use agent-based auto discovery for Oracle Fusion Middleware are no longer required to specify the Oracle Middleware home for each host that the discovery module runs on.

Enhancements to Fusion Middleware and WebLogic Domain Discovery
When adding Fusion Middleware and WebLogic Domain targets to Enterprise Manager Cloud Control, administrators can now choose whether to discover all versions of deployed Java EE applications or just the active version of deployed applications. This provides more flexibility and control in terms of what to centrally manage and monitor from the Cloud Control console.

For each Java EE application that is discovered, a new domain application deployment target is also added. This domain application deployment target provides a single view of the application across the entire domain, rather than a more granular view at the server or cluster levels.

WebLogic Server 12.1.2 ManagementBeginning with this release, administrators are able to discover and centrally manage their WebLogic Server version 12.1.2 deployments. All existing management features continue
to be supported with WebLogic Server version 12.1.2, including:
  •     Performance management
  •     Business Transaction Management
  •     Process control
  •     Configuration management
  •     Cloning middleware and scaling up/out domain
  •     Patching

Support for Managing Oracle GlassFish Domains
Administrators can now discover and centrally manage their open source as well as commercial versions of Oracle GlassFish domains in the Oracle Enterprise Manager Cloud Control console. Management features for Oracle GlassFish include:
  •     Performance management – monitor Oracle GlassFish availability and performance out-of-box, track such data historically, and receive notifications of potential problems.
  •     Process control – submit predefined job to start, restart, or stop Oracle GlassFish components.
  •     Configuration management – perform extensive analysis (for example, search, compare, track change) against automatic, daily collections of Oracle GlassFish data.

Having a single interface for managing Oracle GlassFish software along side other data center environments such as databases and operating systems is critical to ensuring
applications are available and performing at an optimal level.
Exalytics ManagementWith the introduction of the Exalytics target, Exalytics management is now consistent with other engineered systems. Both virtual and physical deployments will be supported for
this target. The feature includes guided discovery, a personalizable software dashboard, routing topology, and vCPU usage reporting.

These features align Exalytics management with the Engineered Systems Management story and show a tighter integration between Exalytics and Enterprise Manager Cloud Control 12c.

The new features improve the user's management experience and productivity. The vCPU reporting supports the reporting and auditing requirement for virtualized environments using vCPU licensing.
JVMD/ADP Installation and UpgradeYou can now automate the deletion of JVMD/ADP engines and agents. This feature is available from the Enterprise Manager Cloud Control user interface. Previously deletion or
undeployment required manual steps.
Updates to the Middleware Summary PageThe Middleware Summary page (accessible by selecting Middleware from the Targets menu) has traditionally displayed a table with the status and health of middleware software
managed by Enterprise Manager Cloud Control.

Beginning with this release, administrators can now choose to display a graphical view of the same data. This graphical view is similar to a heat map where targets are represented as boxes and the size and color of each box depicts a potential problem areas. Such a view enables administrators to quickly analyze a large amount of data, customize filtering, and pinpoint problems more efficiently.

The Middleware Summary page also provides predefined searches that filter the target types shown in both of the table as well as graph views. The searches available are based on what middleware targets have been discovered by Enterprise Manager Cloud Control. The most recent search selected is saved as the default search to display when returning to the Middleware Summary page. Saved searches enable administrators to find what they are looking for faster.

Monitor Oracle Jolt Performance Metrics
Administrators can now monitor Oracle Jolt performance metrics including maximum capacity, pending requests, pool state, request errors (per minute), and requests (per minute).

Such metrics are available from the WebLogic Server target when Oracle Tuxedo and WebLogic are configured to use Oracle Jolt.
WebLogic Cluster Performance Summary Page Supported for Non-Oracle JRF Enabled Clusters
The WebLogic Cluster Performance Summary page no longer requires you to enable Oracle Java Required Files (JRF) on the cluster. Performance metric data appears on the summary page regardless of whether or not the cluster is Oracle JRF enabled.
Oracle Exalogic Management Enhancements
The following new features related to Exalogic Management help provide enhanced operational visibility:
  • Control Stack monitoring for virtualized Exalogic systems enables administrators to view the status of the software infrastructure.
  • It is now possible to send Enterprise Manager Ops Center hardware alarms and alerts to Enterprise Manager Cloud Control's incident management system and manage hardware and software incidents from a single pane of glass.
  • Exacheck target now appears in the Exalogic Navigation Tree providing in-context navigation to Exacheck results.
  • Additional performance and filtering optimizations has been made to the Exalogic Software Dashboard.
  • Exalogic BI Publisher Reporting has been enhanced.

Diagnostic Snapshot EnhancementsAdministrators have traditionally been able to create a diagnostic snapshot from the Enterprise Manager Cloud Control console whenever a middleware-related issue occurs, and then analyze the diagnostic snapshot in offline mode either from the same Enterprise Manager Cloud Control instance that generated the snapshot or from a completely different Enterprise Manager Cloud Control instance (for example, when the snapshot is sent to Oracle Support for analysis). This release includes the following enhancements to the Diagnostic Snapshot feature:
  • Archived logs for WebLogic Server and JVM targets can be included in a new diagnostic snapshot.
  • You can create a diagnostic snapshot through the EMCLI.
  • You can include diagnostic snapshots in a Support Workbench incident.
These additional Diagnostic Snapshot capabilities reduce the resolution time of external bugs related to Fusion Middleware software.
Archived Log Files Supported in Log Viewer
Administrators can now use Log Viewer to view and correlate messages across archived log files for Fusion Middleware components. In the past, Log Viewer supported viewing and correlating messages from active log files only. Including archived log files in Log Viewer helps administrators to diagnose and resolve performance problems that may have
occurred in the past.
Lifecycle Management Features
Enhancements to Cloning and Scaling Up/Out MiddlewareAdministrators can now use the Provision Middleware or Scale Up/Scale Out Middleware deployment procedures to clone or scale up/out a WebLogic Domain that has its administration port enabled or a domain that accepts only secure SSL traffic. Prior versions of the deployment procedures did not support cloning or scaling up/out of such a configured domain.

In addition, these same procedures now support entering credentials for each host destination individually (applicable in situations where preferred credentials are not used).
Administration Features
Enhancements to Fusion Middleware Process Control Job
The out-of-box job for Fusion Middleware Process Control now offers options for how to start, restart, or stop WebLogic Server targets. Administrators can configure the job to
use. Node Manager, the default script in the domain home, or a custom script. These same options are also available when you initiate a start, stop, or restart operation from target home pages or target menus. This feature gives administrators maximum flexibility in managing and maintaining WebLogic environments.

Perform Administration Operations Against Fusion Middleware
Key administration operations previously available from the Fusion Middleware Control console and WebLogic Server Administration Console are now available from the Cloud Control console. These operations include:
  • Locking a domain configuration through the Change Center before making changes to prevent other administrators from making changes during your edit session. You can also
  • view all changes that have been saved, view the server instances that must be restarted for configuration changes to take effect, release a lock, and activate or undo changes.
  • Viewing, configuring, and using MBeans for a specific Oracle WebLogic Server or Application Deployment target through the System MBean browser.
  • Managing JDBC data sources - including the ability to create, edit, delete, control and test JDBC data sources.
  • Recording configuration actions performed as a series of WebLogic Scripting Tool (WLST) commands. You can use WLST to replay the commands to help automate the task of configuring a domain. You can start, stop, or view a recording.
Having a single tool for both monitoring and administering Fusion Middleware components simplifies an administrator's job and increases productivity.
Selective Tracing for Oracle Fusion Middleware
Administrators can now perform selective tracing from the Cloud Control console. Selective tracing enables administrators to gain more fine-grained logging data but limit the
data so that it applies to a specific application name as well as other specific attributes of a request (for example, user name, client host, or web service port). Having such detailed yet focused log data assists administrators while diagnosing problems with applications and their underlying infrastructure.

Privilege Propagating Support for Oracle WebLogic Server and Oracle Application Server Related TargetsBeginning with this release, the following Oracle Fusion Middleware related target types support privilege propagation:
  • Oracle WebLogic Domain
  • Oracle WebLogic Cluster
  • Oracle WebLogic Server
  • Domain Application Deployment
  • Clustered Application Deployment
  • Oracle Application Server
  • Oracle Containers for Java (OC4J)
This support enables administrators to have privileges automatically propagate to members of a target, rather than requiring the administrator to manually grant other administrators privileges to each target individually. You can grant to an administrator or a role a privilege on one of the listed targets once and have that same privilege automatically propagate to any new member of that target.

For example, granting operator privilege on a WebLogic Domain target to an administrator grants the administrator the operator privilege on the domain's member targets (for example, clusters, servers, deployed applications) and also to any members that will be added to the domain in the future. Automation of privilege propagation across these additional Fusion Middleware targets enables administrators to be more effective and efficient in managing their middleware software.
Log Configuration for Oracle Fusion Middleware Components
Beginning with this release, administrators can configure log file settings for Oracle WebLogic Server, Application Deployment, SOA Infrastructure, Essbase Server, Directory
Integration Platform Server, Oracle Virtual Directory, Oracle Reports Application, Oracle Reports Bridge, Oracle Reports Server, and Oracle Reports Tools targets. Configuration
settings exposed in the Cloud Control console user interface include:
  • Location of the log file
  • Format of the log messages in the log file (For example, Oracle Diagnostic Logging – Text, Oracle Diagnostic Logging – XML)
  • Log level for both persistent loggers and active runtime loggers
  • Rotation policies – either size based or time based – used for the log file

User Interface Updates for Site Guard Operations
You can use the new Site Guard user interface to create, execute, and monitor operation plans for switchover, failover, start, and stop.
RUEI Metric Page
The RUEI Metric page uses the same search mechanism as the Session Diagnostics page but here the result set is displayed in the Metric Correlation Chart where RUEI metrics can
be compared against all other system metrics and be displayed in time. This means that End User Page Load times can be presented in time compared with Java active threads or
system CPU usage to discover possible connections. Any view can be stored in the correlation chart. This page can also be directly opened from any RUEI event from the Events and Incidents console. All RUEI events have a link to the metrics page and when selected, the Metric page opens in context of the right metric filters and time period immediately.

JVM Real-Time Thread State
This regions displays a list of all of the JVMs that are associate with the Business Application. It provides a per JVM view of real-time status based on the JVM thread
activities. You are presented with thread counts of specific activities and states including DB Wait, IO Wait, Runnable, and Idle. The number of threads counted in a specific
state reflects how much work a JVM is performing on that area. For example, a larger than normal thread count in DB Wait state suggests a slower than normal DB response time.

The region also provides direct access to the JVM Diagnostic pages for more detailed investigation. This region is updated with real-time data every 30 seconds.
JVM Active Threads

This region provides an overtime view of the data presented by the JVM real-time Thread State region. The data is summarized across all of the JVM and presented for the last 24
hours.
Application Replay
Application Replay enables you to perform realistic production scale testing of your web and packaged Oracle applications. It provides the most efficient and highest quality
testing through zero overhead workload capture and without any need for script development and maintenance. The captured workload can then be replayed with production characteristics on a test system to validate application infrastructure changes from the middle tier to the disk.

Application Replay Enhancements

Note:
These enhancements are new in the 12.1.0.3 release.

After a successful replay, users were able to view reports to analyze, capture, and replay results. The reporting mainly focused on application page names and addressed questions such as what was the performance of the page and which pages diverged compared to capture.

Now users have the ability to not only look at page level diagnostics but also session level diagnostics. With this new ability, you can answer questions such as which sessions
showed poor performance and then quickly identify the pages where the session was experiencing poor performance.

Additionally, to ensure that a page's poor performance is not caused by setup issues, a divergence report showing differences between the capture and replay of pages is provided. Similarly, when ensuring that a session's performance is not due to a divergence between capture and replay, users were required to view the raw HTTP requests and
response contents manually and compare the difference. Now users can simply export a packaged zip file containing capture and replay content and diagnostics and import that into Oracle Application Testing Suite's OpenScript. Doing this enables an automated and visual comparison of capture and replay of a specific session, drastically reducing the time
to identify any divergence or potential performance issues.

These diagnostics improvements enable deeper analysis of replay results quickly and reduce the time to isolate potential issues in a replay environment with perspective of end
user sessions.

For more details, pls refer http://docs.oracle.com/cd/E24628_01/doc.121/e25353/whats_new.htm#CJAGBIEC

Thursday, July 25, 2013

EM12c: What's new in EM 12.1.0.3 (PS2) Middleware Management?


Recently Oracle Enterprise Manager has done PS2 (12.1.0.3) release.
With this EM release, Fusion Middleware Plug-in 12.1.0.4 has been released. Next post will talk about new features with FMW plugin 12.1.0.4.
This post will limit to new features introduced in Middleware management.
Along with specific Middleware management features, it would be nice to know about new features introduced at framework/monitoring level  etc.

Monitoring and Diagnostics Features 
WebLogic Cluster Performance Summary PageA new customizable performance summary page is available for Oracle WebLogic Cluster target types. Administrators can now modify the default performance metrics that are displayed when metric annotations are enabled on the middleware Routing Topology page. 

Log File Monitoring
This release of Oracle Enterprise Manager Cloud Control introduces log file monitoring for the WebLogic Server as well as Application Deployment target types. Middleware
administrators can configure the new log monitoring metric to send alert notifications to on-call administrators when specific patterns are found in the middleware-related log
files.

WebLogic and Fusion Middleware Log Viewer Enhancements
Beginning with this release, two significant enhancements have been made to the log viewing capabilities within Oracle Enterprise Manager Cloud Control. First, instead of being able to group log messages only by Message Type or Message ID, administrators now have the flexibility of grouping messages by several other possible fields - including Execution Context ID (ECID)/Relationship ID, Host, Host IP Address, Incident ID, Module, Target, Thread ID, or User. Second, the search criteria for log messages that an administrator defines can be saved for future usage and accessed through the Favorites menu.

New Home Pages for Oracle Service Bus Target
New management pages for the Oracle Service Bus target replace the previous pages. The new pages improve the look-and-feel of the OSB monitoring pages and enable the OSB targets to appear in the standard Fusion Middleware Farm/Domain navigation tree.

Business Application Target Features

The Business Application (BA) Target is a monitored functional application. It combines the user's perspective (RUEI), transaction visibility between application components (BTM), application component monitoring (JVMD) and Application and Dependency Performance (ADP)) and system monitoring.

The BA Target provides a consolidated overview that enables BA owners to see and understand the health of their applications. The following pages are an integral part of the BA Target:

Business Application List PageThis page provides a list of all BA Targets for which you have at least read permission, including significant status indicators. You can use it to navigate to a specific BA dashboard. This page enables you to see at a glance which BAs require attention.

Business Application Home PageHome page for the BA target. The dashboard displays following regions:
        RUEI KPIs
        BTM Transaction List
        System Status
        Incidents
        Service Test Status

It also provides problem triage capabilities and a starting point to drill down to more detailed system related views (including JVMD, composite application, and WLS monitoring home page,).

Business Transaction Drill-Down Page
The Business Transaction region on the Business Application Home page displays the transactions mapped by the administrator of the BA, one transaction for each row. Click a
transaction link to view the dedicated business transaction page.This page contains the following regions and features:
        Transaction Summary
        Business Transaction Aggregate Flow
        Operations
 
Real User Experience Insight Session Diagnostics PageWith this feature it is possible to correlate the Request Instance trace that is reported in Request Instance Diagnostics to a user session reported in RUEI Session Diagnostics. It also provides a contextual drill-down to review the request within the complete user session.This feature is created from the following pages:
        Session Search
        Session Diagnostics

Registering RUEI Engine and BTM Engine in Enterprise Manager Cloud ControlYou can register a Real User Experience insight deployment and a BTM engine as a system in Enterprise Manager Cloud Control. Only one RUEI and one BTM system can be created in Enterprise Manager Cloud Control. 

Lifecycle Management Features

Synchronization of WebLogic Server Configuration FilesIf differences are detected between WebLogic Domains or WebLogic Servers during a configuration comparison operation, you can now synchronize WebLogic Server related
configuration files (for example config.xml) from the Cloud Control console to make the configurations the same.

Oracle Fusion Middleware Provisioning Enhancement
The Provision Middleware Deployment Procedure and Scale up/out Middleware Deployment Procedure now support the lock down feature. This feature enables administrators with designer privileges to launch the procedure, enter values for certain fields, and lock them so that the fields cannot be edited when accessed by other administrators. Creating these deployment procedure templates helps administrators to enforce standardization and consistency across the enterprise.
While cloning or scaling out a WebLogic Domain, you can now modify the default names for the administration server, managed servers, clusters, and systems for the destination
domain.
While cloning a WebLogic Domain, you can now specify the applications directory and Node Manager home directory locations.
 
Patchability Report for Fusion MiddlewareTo ensure that WebLogic Server and SOA Infrastructure components are suitable for patching operations, administrators are encouraged to review the new Fusion Middleware Target Patchability Report available from Information Publisher before creating patch plans. This report analyzes WebLogic Domains as well as SOA Infrastructure and identifies whether the targets have missing properties or unsupported configurations and provides recommendations for resolving the issues found.
 
Apply Patches Across WebLogic DomainsBeginning with Fusion Middleware Plug-in release 12.1.0.4, administrators can apply WebLogic Server patches to several WebLogic Domains in a single operation. Such support increases efficiency because administrators can create and track a single patch plan across domains instead of creating multiple patch plans.
 
EMCLI Support for Creating Java EE Application ComponentAdministrators can now create a Java EE Application component in the software library through the EMCLI thereby automating application deployment end-to-end.
 
Oracle Site Guard Features

This section provides an overview of the new features available in Oracle Site Guard 12c Release 1 (12.1.0.3) plug-in releases.
User Interface for Site Guard ConfigurationIn 12c Release 1 (12.1.0.3), you can use the Enterprise Manager Cloud Control Console user interface to perform the following task:
    Creating Oracle Site Guard Configuration
    Associating Credentials for Site
    Associating Pre-Scripts and Post-Scripts
    Associating Storage Scripts

For more information, see "Setting Up Oracle Site Guard" in the Oracle Enterprise Manager Lifecycle Management Administrator's Guide.


Identity Management Features

Configuration Collection for Oracle Access Manager and Oracle Identity Manager
Configuration collection for Oracle Access Manager and Oracle Identity Manager is now available, enabling users to view and keep track of configurations in oim-config.xml,
entries in the property (PTY) table, and oam-config.xml. 

The feature provides automated configuration management to accelerate problem resolution and to find root causes of problems that could potentially slow performance or create outages.
 
Out-of-Box Compliance Rules and Change Detection for Oracle Identity Manager
A set of 12 out-of-box compliance rules have been defined for Oracle Identity Manager based on best practices around plug-in and adapter reloading, caching configuration, and
recommended database settings such as cursor sharing, block size, maximum number of blocks read in one I/O operation, buffer pool, initial number of database writer processes,
log buffer, maximum number of open cursors, query rewrite integrity, and session cursors to cache. Users can perform rules based analysis and change detection, and get access to
a compliance scorecard for each of the monitored Oracle Identity Manager deployments.

This feature provides compliance monitoring and change detection that can help customers meet compliance and reporting requirements, and accelerate problem resolution.
Oracle Identity Manager Database Performance

Out-of-Box Reports for Oracle Internet Directory, Oracle Access Manager, and Oracle Identity Manager
Out-of-box BI Publisher reports are now available for Oracle Internet Directory, Oracle Access Manager, and Oracle Identity Manager. These reports summarize monthly LDAP
Operations and Replication Jobs for OID, Provisioning, Self-Service and Role-Grant Requests for OIM, and Authentications & Authorizations Metrics for OAM - including
Authentications/Authorizations Per Second and Failed Authentication/Authorization Ratio.

The out-of-box reports can be used to track the overall health of the monitored Identity Management environment enabling administrators to share these reports with the line-of-
business or application owners to align IT and business demands.
 
Other Features

Oracle Traffic Director Target Correlation
This feature correlates the new Oracle Traffic Director (OTD) target monitoring with the WebLogic and OHS targets ensuring that administrators can easily understand relationships via the middleware topology and analyze problems across tiers.

OTD is available from the Exalogic dashboard as well.
 
Performance & Health Monitoring of Oracle BI 11g Instances & EssbaseThe discovery of BI 11g Instance is now included as part of the Oracle Fusion Middleware/WebLogic Domain discovery wizard, enabling you to quickly set up your monitoring environment. The discovery includes all key Oracle BI components as well as Essbase. The BI components discovered include Oracle BI Server, Oracle BI Presentation Server, Oracle BI Scheduler, Oracle BI Cluster Controller, and Oracle BI Java Host. After the BI Instances are discovered, you can proactively monitor your Oracle BI environment from both systems and end-user perspectives. A wide range of out-of-box performance metrics are collected for monitored Oracle BI targets enabling you to set up alerts based on warning and critical thresholds, view current and historical performance information using customizable charts in the Metric Palette and reports, and diagnose performance problems by identifying bottlenecks in any of the monitored Oracle BI targets.

For the Essbase Server, you can now monitor running applications, view any unaccessed applications as well as other useful metrics and information such as the number of connected users, configuration changes, and potential incidents.
 
Coherence Elastic Data and QL SupportWith the new capabilities of Coherence on engineered systems introducing the new Elastic Data and QL capabilities, Enterprise Manager now provides complete visibility into these
key Coherence platform features to ensure these optimizations are fully used to their maximum potential.
 
Exalogic Topology ViewThe new Exalogic Topology View ensures that administrators can immediately identify cross-tier relationships between components, middle-tier platforms, and the underlying hosts and hardware that make up an Exalogic Elastic Cloud system.
 
Middleware as a Service Features

Resource PoolSupport is provided for guided flow to create middleware resource pools on a self-service zone. This feature enables SSA administrators to carve out resources for a middleware
cloud.
 
MWaaS QuotasSupport is provided for the creation of middleware cloud quotas by an SSA administrator. This feature enables administrators to allocate resources between different users and
ensure that no one user can usurp all resources.
 
MWaaS Request SettingsSupport is provided for the creation of middleware request quotas by SSA administrators. This feature offers SSA users the ability to schedule resources requests in advance.
 
Service TemplatesSSA administrators can create Service Templates and map them to resource pools and Zones. This feature enables SSA administrators to build a self-service catalog tailored to
enterprise needs.
 
Provision and De-provision Service InstanceA guided flow is available that enables SSA users to request a new service instance from a given set of service templates, resulting in creation of a new service instance and its appropriate placement in the resource pool. You can later delete a service instance as well, thereby returning resources to the underlying pool.

This feature enables SSA users to self-service provision and manage resources on the cloud.
 
Manage Application LifecycleSSA users can deploy, redeploy, and delete a Java application from the self-service portal, enabling SSA users to manage the application lifecycle.
 
Service Instance ScalingSSA users can scale up or scale down a service instance from the self-service portal, enabling SSA users to manage scalability of a service instance.
 
Manage Data SourcesSSA users can create data sources, add data sources to, or delete data sources from the service instance as required by an application. This feature enables SSA users to add
data sources required by an application to the service instance.
 
Oracle Exalogic Management Enhancements

This release provides the following Exalogic dashboard enhancements:
    Integrated hardware and software schematics
    Hardware-software topology views
    Hardware targets monitoring (Compute, ZFA appliance, Infiniband Fabric, ILOM)
    OTD monitoring
    Support for virtual and non-virtual configurations
    Monitoring of Exalogic vServer guest virtual machines (VMs)
    Health checks
    Trusted partition/Virtual Central Processing Unit (vCPU) licensing report


For more details, pl refer http://docs.oracle.com/cd/E24628_01/doc.121/e25353/whats_new.htm#CEGGGJEC

Tuesday, April 23, 2013

EM12c: MWaaS instance provision request Failed - Error evaluating expression ${ora:getEntityURN('MwaaS/Directives/Find Free Ports')} for parameter directive_urn

Error: After setting up MWaaS, user always gets error at step “Find Free Ports” when try to request a service from self service portal:

------emoms.log contains----------
2013-04-18 13:40:15,317 [PAFDaemon] ERROR procedure.engine logp.251 - Unable to resolve URN for Software Library Entity with internal path: MwaaS/Directives/Find Free Ports
oracle.sysman.emSDK.core.job.procedure.exception.ProcedureException: Unable to resolve URN for Software Library Entity with internal path: MwaaS/Directives/Find Free Ports
at oracle.sysman.emdrep.jobs.procedure.func.GetURNFromInternalPath.execute(GetURNFromInternalPath.java:146)
at oracle.sysman.emdrep.jobs.procedure.engine.el.parser.FunctionExpression.eval(FunctionExpression.java:214)
at oracle.sysman.emdrep.jobs.procedure.engine.el.parser.Expression.eval(Expression.java:38)
at oracle.sysman.emdrep.jobs.procedure.engine.el.ExpressionManager.eval(ExpressionManager.java:111)
at oracle.sysman.emdrep.jobs.procedure.engine.el.ExpressionManager.eval(ExpressionManager.java:83)
at oracle.sysman.emdrep.jobs.procedure.impl.BindingStepImpl.resolveVariable(BindingStepImpl.java:300)…

------emoms.trc contains------
2013-04-18 13:29:03,211 [PAFDaemon] ERROR procedure.engine logp.251 - Error getting URN for path: MwaaS/Directives/Find Free Ports
2013-04-18 13:29:03,244 [PAFDaemon] ERROR diagnosability.DiagnosabilityService logp.251 - [EM-03654] Problems with job submission during procedure execution.
oracle.sysman.emdrep.jobs.procedure.impl.JobSubmissionException: Error evaluating parameters.
         at oracle.sysman.emdrep.jobs.procedure.impl.JobProducerImpl.submitJob(JobProducerImpl.java:337)
         at oracle.sysman.emdrep.jobs.procedure.engine.impl.JobProducerStateImpl.execute(JobProducerStateImpl.java:686)
         at oracle.sysman.emdrep.jobs.procedure.engine.impl.JobProducerStateImpl.execute(JobProducerStateImpl.java:642)


Action: Re-import the metadata of software lib, after re-import, Pl. ensure that it should look like as given below:




Now retry request provisioning.