An internal system error on ruei login screen

RUEI 6.5.1 is installed successfully without any error.
While trying to access RUEI url, login screen shows error as in following screenshot:

An internal system error is seen in /ruei/var/opt/ruei/processor/log/websensor*dbg file and this error is thrown even before showing login prompt screen.
Exception: An internal system error has occurred. Please contact the Administrator with the error details.
Code: 256
Stack trace: #0 /ruei/opt/ruei/gui/include/data/monitoring.inc.php(3566): uxQuery->Execute()
#1 /ruei/opt/ruei/gui/proxy.php(829): utGetNotificationProfile(1001)
#2 {main}

Action:
Verify the permission of $RUEI_DATA directory.
Ensure that 'apache' user has read permission for $RUEI_DATA directory so that it can read the oracle wallet.
%chmod 750 $RUEI_DATA

How to add SOA Server (any FMW) Target in EMGC 11g?

Steps for discovering SOA (any FMW) target:

1.      Log into Enterprise Manager Grid Control.

2.      Goto Targets -> Middleware tab.

3.      Select Oracle Fusion Middleware/WebLogic Domain from the Add menu on top right drop down of page, then click Go.

4.      Enter the hostname of the WLS Admin Server of SOA domain for the domain in the Admin Server Host field. e.g. host1.abc.com

5.      Enter the WebLogic Admin Server port. Default value is 7001.

6.      Enter the WebLogic Admin Server username and password.

7.      Select or specify the hostname and port of the EM Agent that will monitor the domain. For EMGC 11g,  11.1 EM Agent is needed.

8.      Specify a Unique Domain Identifier. This value is used as a prefix to ensure farm names are unique in environments with the same domain name. By default, the name "Farm", followed by a two-digit number, such as, "Farm01" appears.

9.      Optionally provide the Java Management Extensions (JMX) Service URL that will be used to establish a JMX connection to the WebLogic Admin Server. For example:

service:jmx:t3://host1.abc.com:5555/jndi/weblogic.management.mbeanservers.domainruntime

        If no value is provided, EM will use the Service URL based on the host port and protocol.

10.    Click Continue. EM will discover all FMW targets within given domain.

11.    Click Close in the Finding Targets page to automatically assign EM Agents to the discovered targets.

       The Assign Agents page lists all the discovered FMW targets and the EM Agent assigned to each of them. Agents are automatically assigned as per following rule:

          *    If a local EM Agent is found on the domain host, that EM Agent will be assigned.

          *    If a local EM Agent cannot be found, the EM Agent specified in the Targets page will be assigned.

       Note: that one can also manually assign EMAgents to specific targets, if desired.

14.    Click Add Targets to assign Management Agents as listed in the Assign Agents page.

       The Saving Target to Agent processing page appears, indicating how many total targets have been added and successfully saved. It will also indicate the numbers of targets that were unsuccessfully added.

15.    Click Close when finished. The Results page displays the discovered targets and EM Agent assignments.

16.    Click OK when finished. There might be some delay before discovered FMW targets are visible and monitored.  

Note: Pl. ensure that all the EM agents used for monitoring the targets must be up and running.

How to configure ADP (OCAMM) for Weblogic with EMGC11g on Linux platform

Note: One MLR has been released since EMGC 11g release.

It is recommended to apply the given patches in order for ADP(OCAMM) to work properly.

p9901141_111010_Generic for the OMS

p9930117_111010_Generic for the EMAgent

I'm assuming that user is configuring ADP (OCAMM) for first time in EMGC. If customer has already configured OCAMM previously then there would be additional steps to undeploy old ADP manager and agents before applying the patch and some steps would be bit different.

Though the steps for configuring ADP setup are given in http://download.oracle.com/docs/cd/E11857_01/install.111/e17558/enable.htm

Before starting one must be prepared with info that would be needed for configuring OCAMM in EM11g. Pre-requisite is:

a.     Have a database setup and its details ready. Create a database user adp that would be needed for setting up ADP.

b.     Have following details of target application servers handy:

·         admin server host

·         admin server port

·         admin user name

·         admin password

·         admin connect protocol (for example, t3 or t3s)

Setting up OCAMM would involve:

1.  Installing ADP manager

a.     Goto OMS home i.e. %cd $ORACLE_HOME/ocamm

b.     Take the ocamm.zip to machine where you want to deploy ADP manager. Then unzip %unzip ocamm.zip

c.     Run Disk1/InstData/<platform>/VM/install.bin

d.     Do not create links. (For detailed instructions follow link given above.) Install ADP manager in <ADP_HOME> location.

2. Registering the ADP Manager with EMUI

a. Start the configuration console by running <ADP_HOME>/bin/config.sh. Ignore console UI. Goto EM OMS UI.

b. Targets->Middleware->Application Dependency and Performance(link at bottom of page) Page.

c. On left Panel, click on Registration tab and then Manager. Register installed ADP Manager on default port 51099.

d. Test connection and add it.

3. Configuring Database for ADP repository

a. Click on Configuration tab, select the Database Configuration node. Edit the default database configuration MyOracle for ADP repository.

b. Provide database access credentials of user adp created earlier.

c. Test Connection to verify database connection and then click OK

4.  Shut down the configuration console by running <ADP_HOME>/bin/acshut.sh ( Wait about 30 seconds after acshut.sh exits for the shutdown to complete )
5. Deploy <ADP_HOME>/deploy/HttpDeployer.ear on Target Application Server (Admin Server)
For target WebLogic server, deploy <ADP_HOME>/deploy/HttpDeployer.ear to target application server’s Admin Server.
6. Start the ADP Manager by running <ADP_HOME>/bin/acsera.sh (for example, nohup ./acsera.sh &")

7. Configuring Target resources that would be monitored using ADP agent

a. Click on Configuration tab, enter Target application server(AdminServer) access information e.g. for Oracle WebLogic Server, the fields listed are the following:

·         Protocol: enter t3 or t3s

·         Host: DNS name or IP address of the WebLogic Admin server for the monitored domain. (Note: If a <listen-address> is specified for the admin server, the name listed here must match that parameter.

·         Port: Port which the WebLogic Admin server is listening for t3 connections.

·         Http Host: DNS name or IP address of WebLogic server where the HttpDeployer.ear is deployed (usually the admin server).

·         Http Port: Port where the Weblogic server on which HttpDeployer.ear is deployed and is listening for connections

·         Http Protocol: Either http or https depending on the configuration of the WebLogic server where the HttpDeployer.ear is deployed

·         Admin Server User ID: User name to access the WebLogic admin server

·         New Password: Password for the username used to WebLogic admin server

·         Retype New Password: Repeated password for the username used to access the WebLogic admin server

Note: Rest of the fields are not valid for 11g, hence leave them as they are

b.     Click OK to return to the previous screen

c.     Click Test Connection. Wait for the <ADP_HOME>/lib/bea/<version>_runtime directory to be created and populated with jar files. This could take a few minutes. ( If nothing happens, check log/manager-log#.csv for exceptions.)

8. Deploy ADP agent on Target Weblogic Servers

a. Click Back to return to the previous screen and then click Deploy

b. On the next screen, select Deploy from the Command menu and then select the servers/cluster where you want to deploy the ADP Agent. Ensure that the admin server is always selected.

Note: In the case of WebLogic Portal, AdminServer is always selected. Please unselect / select Nodemanager in case of weblogic based on how do configure the Weblogic manager to start.

c. Click Continue

d. Wait for deployment to complete. Verify that the UI reports Deployment Successful;( if not, check for exceptions in <ADP_HOME>log/manager-log#.csv)

e. To view the status on the same page, click Refresh. Note that you might have to click Refresh a few times as it might take a while to deploy and update the status. Depending on the number of managed servers in your domain, it could take several minutes (up to 60 seconds per managed server) for this operation to complete. Stay on this page and monitor the manager log until some status is returned.

f. Click Back to return to the previous screen and then click Save

9. Shut down the ADP Manager by running <ADP_HOME>/bin/acshut.sh

Wait about 30 seconds after acshut.sh exits for the shutdown to complete

10. Restart the application servers where ADP agent has been deployed.

11. Start the ADP Manager by running <ADP_HOME>/bin/acsera.sh (for example, nohup ./acsera.sh &")

12. Wait for a while for  discovery to occur. You can check that discovery is happening by looking to see if <ADP_HOME>/darchive/server_archive is created and growing, and then that <ADP_HOME>/darchive/app_archive is created and growing. If you think something is going wrong, you can check log/manager-log#.csv for exceptions, but this process can take several minutes.

13. To view ADP pages from the Grid Control Home page, click Targets-> Middleware-> Application Dependency and Performance-> Monitoring tab.

14. Verify that all servers to which you deployed the ADP Agent are up and running. Click the manager node in the Monitoring tab. The Agent information is available in the Main Display window.

ArrayIndexOutOfBoundsException on JVM Pools page

While configuring 11g JVM Diagnostics, following patches were applied:
9901141 for OMS and
9930117 for Agent
After applying the patch, ad4j Manager was deployed. Manager deployment
was successful. Now on clicking JVM diagnostics->Setup->JVM Pools page, exception appears as given in image:

Issue is with cache here.
Solution: In this case
1. stop the OMS
2. mv user_projects/domains/GCDomain/servers/EMGC_OMS1/tmp user_projects/domains/GCDomain/servers/EMGC_OMS1/tmp_bkp
3. delete user_projects/domains/GCDomain/generated_classes/jsp_servlet/_e2e/_ad4j directory
4. start OMS
For multiple OMSs, repeat the process on each OMS. Clearing the cache would resolve the issue.

How to view ad4j pages in enterprise manager 11g?

In EM11g, following two privileges have been added for accessing AD4J pages.

1. JVM Diagnostics Administrator and

2. JVM Diagnostics User

Any user that has above privileges can access AD4J pages. OR even Superuser can access the ad4j Pages.