Thursday, February 21, 2013

EM12c: How to setup MWaaS? - Part II

Middleware as a Service Cloud Setup( requires following steps:

1. Role and Users creation
Following users are needed for MW cloud setup

Example username

Note: SSA_DEV_ROLES is a custom role. Steps to create this role are given on this link.

2. Push agent on All Target Hosts
 All hosts that participate in cloud setup should be EM targets and EM agent should be pushed on these hosts. steps are given on link

3. Privilege Delegation Settings
Privilege delegation allows a logged-in user to perform an activity with the privileges of another user. Sudo and PowerBroker are privilege delegation tools that allow a logged-in user to be assigned these privileges. These privilege delegation settings will be used for all provisioning and patching activities on these hosts.

4. Software library configuration
The Software Library is a repository that stores software patches, virtual appliance images, reference gold images, application software and their associated directive scripts. Software library is needed for loading Out of Box WLS profiles. Steps to configure Software library are given on link

5. Loading Out of Box Middleware Provisioning Profiles
Download OOB Middleware Profiles using Self Update as given on link
Note: These OOB profiles DO NOT contain any gold image. It just contains WLS domain definition, so user is expected to have MW home software only install as given in step 7.

6. Create PaaS Infrastructure Zone
Define a PaaS Infrastructure zone, include which hosts would be part of this zone and what users(roles) can access this zone.

7. Create Middleware Home
OOB 10.3.6 WLS profiles require JRF enabled WLS 10.3.6 install. It can be a software only install done via
-SOA (PS5) installer
Note: Once a Middleware Home is created, it should be discovered and promoted to be visible under All Targets.

8. Configuring and Save the Deployment Procedure
Configure and save a Middleware Provisioning deployment procedure. This configured deployment procedure will be used by the EM_SSA_ADMINISTRATOR while creating a Middleware Service Template.

9. Setting Up the MWaaS Self Service Portal
The EM_SSA_ADMINISTRATOR can configure and set up the middleware self service portal by creating middleware pools, quotas, request settings, and service templates.

10.Using the Middleware Cloud Self Service Portal
This Portal can be used to
•    Monitor resource allocation
•    Request and Provision Middleware Services
•    Monitor performance of provisioned middleware service
•    Control availability of provisioned WebLogic servers through simple STARTUP / SHUTDOWN push buttons
•    Scale Up / Scale down provisioned middleware instance
•    Deploy/Undeploy/Redeploy Java EE Applications
•    Create Data Sources
•    Monitor deployed J2EE Applications
•    Deletion of middleware service instances that will no longer be used

Monday, February 18, 2013

EM12c: How to setup MWaaS? - Part I

In next few articles, we will learn to setup MWaaS.

In this article, we will just learn about the concept of MWaaS and its pre-requisites.

Oracle Cloud Management Pack for Oracle Middleware delivers capabilities spanning the entire Middleware cloud lifecycle. 
It lets Cloud administrators identify pooled resources, configure role-based access, define the service catalog, and the related chargeback plans. 
It allows Cloud users to request middleware services, and consume them on-demand. 
It also allows for users to scale-up and down their platforms to adapt to changes in workload. 
Deploy/undeploy/redeploy applications, create data sources and monitor these applications. 
Finally, it lets both parties to understand the costs of the service delivered, and establish accountability for consumption of resources. 

Prerequisite for MWaaS:
1.       EM12cR2 along with EM repository 

2.       Plugin Requirements
-Enterprise Manager for Oracle Virtualization
-Enterprise Manager for Oracle Cloud Application
-Enterprise Manager for Oracle Fusion Middleware
-Enterprise Manager for Chargeback and Capacity Planning

3.       Target machines:One
Note: WLS Provisioning would be done using OOB WLS profile. 

4.       For WLS provisioning using OOB profile, we require Fusion Middleware (WLS 10.3.6) with JRF enabled and that can be done using following either Webcenter or SOA installers. 


5.       On target machine, we need to have Middleware Home installed. It can be installed using wls 10.3.6 generic installer and webcenter/soa installer as mentioned in step 4. This Middleware Home should be a software only install. No weblogic instance should be created on this MW home.

Wednesday, February 06, 2013

EM12c: How to fix BI Publisher report error that shows invalid username/password error?

Issue: With EM12cR2, BI Publisher is installed and integrated successfully. However, on accessing any report via BI Publisher as sysman user. It shows following error:

Parameter name: targettype weblogic.common.resourcepool.ResourceDeadException: 0: Could not connect to 'oracle.jdbc.OracleDriver'. The returned message is: ORA-01017: invalid username/password; logon denied It is likely that the login or password is not valid. It is also possible that something else is invalid in the configuration or that the database is not available.

Following error is seen in BIP managed server's log file(BIP.out):
2013-Jan-31 12:26:28EMReposAuthenticatorHelper: Following SQLException occurred.
SQLException code=28009 error msg: ORA-28009: connection as SYS should be as SYSDBA or SYSOPER

Problem verification:
When trying to connect EM repository as mgmt_view user via sqlplus. It works fine.

%$ORACLE_HOME/bin/sqlplus mgmt_view/<passwd>@<emrep>
SQL*Plus: Release Production on Fri Feb 1 10:06:48 2013
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> Disconnected from Oracle Database 11g Enterprise Edition Release - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Apparently, at some point along with other EM repos users, mgmt_view user password got modified using sqlplus. Which is the not supported way of modifying mgmt_view user passwd.

On OMS machine, execute the following command:
% $ORACLE_HOME/bin/emctl config oms -change_view_user_pwd -sysman_pwd <sysman_pwd> -user_pwd <user_pwd>
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Successfully changed password. You must restart the BI Publisher Enterprise Managed Server in order for BI Publisher to function correctly.

Restart the BIP server using weblogic console and restart oms using emctl commands:
% $ORACLE_HOME/bin/emctl stop oms

% $ORACLE_HOME/bin/emctl start oms