While migrating discoverer sso-connections, ‘ssomig’ hangs

Helped a collegae who was migrating a discoverer configuration to another node with a different version (from 10.1.2 to 10.1.4) with now a 10.2 – infrastructure database in a separate home. The OID-users were already successfully migrated, with a little help of the example-script here, but one of the problems was that discoverer didn’t use the single-sign on. The other was that the private and public connection users had made, had disappeared.

By enabling Single Sign-On for Discoverer (is not default when installed) the first problem had been solved:

By |May 30th, 2010|Categories: App. Server|Tags: , , |1 Comment

Discoverer shows down in Grid Control while up.

m4s0n501

Short one this time, all in favour of getting my green ‘pie’ in Grid Control management server.

Grid Control: 10.2.0.5. Discoverer: 10.1.2.x
In Grid Control, after upgrade to 10.2.0.5, a Discoverer target shows down in the list, while it’s functioning quite well.

It seemed an old bug (Grid Ctrl 10.1.04) is still not fixed:
– Bug 4474849 / 3897834 ‘DISCOVERER INSTANCES ALWAYS SHOW DOWN’
– Note: 332363.1

Solution:

1- Remove the Application Server target which owns the Discoverer component (10.1.2) in the Grid Control

2- Stop the agent

3- Backup the file %CENTRAL_AGENT_ORACLE_HOME%/sysman/admin/metadata/oracle_discoverer.xml file.

Replace this file by:

%BI_ORACLE_HOME%/sysman/admin/metadata/oracle_discoverer.xml file

BI_ORACLE_HOME corresponds to the Oracle_Home where Discoverer 10.1.2 is installed.

4- Restart the agent

5- Rediscover the Application Server target on the host, by typing (Agent-environment)  ‘agentca -d’.

By |September 9th, 2009|Categories: grid control|Tags: , |2 Comments

Sun JRE instead of Jinitiator: Discoverer

The whole company has to move in the end to Sun Java  instead of Jinitiator (also based on Sun Java by the way), so also the Discoverer – application.

Changed the client from Jinitatior 1.3.2 to Sun 5, update 6 (5.0.6).  You can download it here by the way.

As of this release you can no longer specify the exact JRE release. Only configure the ‘Family CLSID’.

Configure Discoverer, middle-tier:
1. cd $ORACLE_HOME/discoverer/config
2. backup configuration.xml
3. edit configuration.xml
4. comment out the original Sun JRE tag using the comment tags:
For example:
<!– <jvm name=”sun” classid=”clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA” plugin_setup=”http://biserver.domain:7779/jpi/j2re.exe” version=”1.4.2″ versionie=”1,4,2,mn” type=”application/x-java-applet” plugin_page=”http://java.sun.com/products/archive/j2se/1.4.2_06/index.html” disco_archive=”disco5i.jarjar” d4o_archive=”d4o_double.jarjar”/> –>

5. Insert the new Sun JRE tag:
For example:
<jvm name=”sun” classid=”clsid:CAFEEFAC-0015-0000-FFFF-ABCDEFFEDCBA” plugin_setup=”http://biserver.domain:7779/jpi/jre5u16.exe” version=”1.5″ versionie=”1,5,0,mn” type=”application/x-java-applet” plugin_page=”http://java.sun.com/javase/downloads/index_jdk5.jsp” disco_archive=”disco5i.jarjar” d4o_archive=”d4o_double.jarjar”/>

Table of the Sun version versus the Family CLSID’s:

1.4.2     : clsid:CAFEEFAC-0014-0002-FFFF-ABCDEFFEDCBA
5.0        : clsid:CAFEEFAC-0015-0000-FFFF-ABCDEFFEDCBA
6.0        : clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA

Oracle quote ———>:

“The behavior will be as follows:

If the user does not have any JRE installed on the client PC, then the JRE installed be what you have configured with the plugin_setup parameter; therefore, we would recommend that you stage the latest minor version within the JRE family.

* For 1.5, it will be 1.5.0_16 (http://java.sun.com/javase/downloads/index_jdk5.jsp).

This would require the Discoverer Administrator to:

* Download the latest jre family Windows executable you plan to use on the Windows clients
* copy or ftp (binary) the executable to the Discoverer middle-tier server at: $ORACLE_HOME/jpi/bin/
You may name it whatever you wish, for example: jre142u18.exe or jre150u16.exe
* Update the plugin_setup=”http://biserver.domain:7779/jpi/jre5u16.exe” (in the file configuration.xml), making sure the executable names match

”   <——— end of Oracle quote.

By |September 8th, 2009|Categories: App. Server|Tags: , , |0 Comments

Discoverer Plus decreased interaction-performance with Sun JRE 1.6.0_03

User reported a very slow interacting on his new laptop with Discoverer Plus.  Changing tabs, opening workbook wizard e.g. Other laptops / workstation had no problems.

He was the only one who had a ‘modern’ Java version on his laptop : above 1.6.   So it had to be Java.  And that was right. Note  747189.1 is mentioning the following:

The problem does not exist with JInitiator or with Sun plugin 1.4 or 1.5 and earlier versions of 1.6

* JRE 1.6.0 – works correctly, runs with 1.5.0-like speed
* JRE 1.6.0_01 – works correctly
* JRE 1.6.0_02 – works correctly
* JRE 1.6.0_03 – here the problem is observed for the first time. The issue is then observed in all subsequent versions (e.g.,  _04, _05, _06, _07 and the new_10)

The problem does not exist when an entry for the Discoverer server exists in the local hosts file on the client PC (C:\WINDOWS\system32\drivers\etc\hosts).

Cause

Sun’s Java plug-in performs reverse DNS lookups when connecting to the Application Server. This can be observed with a network sniffer trace (Wire Shark).

There is a change in the DNS handling in Sun plug-in 1.6.0_03 and higher.

Solution:  Ensure the external facing IP address of the Discoverer server has a reverse DNS entry in the DNS server.

For example:

nslookup <IP address> must resolve to the <machinename.domainname>

and

nslookup <machinename.domainname> must resolve to <IP address>

An alternative or temporary solution would be to add an entry to the local PC hosts file, as described above.

–> I decided to go for the last option: local host file (one laptap for the time being). It works fine.


By |May 10th, 2009|Categories: App. Server|Tags: , |0 Comments