[SOLVED] Node manager is down after configuring SSL in weblogic [Cannot convert identity certificate]

Error:  <SEVERE>  <Fatal error in node manager server>
java.lang.RuntimeException: Cannot convert identity certificate

Cause:Reason for this issue is we configured SSL.enableJSSE=true  in weblogic console only. We need to set this option in startNodeManager.sh file also

Solution: Edit your startNodeManager.sh file and add the below tag in the following location

Tag to add : "-Dweblogic.security.SSL.enableJSSE=true"

Solved[BEA-000386]: Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied In OBIEE

Error: While starting BI_Server, server state changed to force shutting down with the following error.

" <Critical> <WebLogicServer> <OPQA007> <bi_server1> <main> <<WLS Kernel>> <> <> <1467614089016> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied "


Cause: boot.properties file is not properly set.

Solution: check whether boot.properties file is present in the below mentioned location

"/home/oracle/MWHome/user_projects/domains/bifoundation_domain/servers/AdminServer/security/"

If it is not there create a boot.properties file

Entries in the file

#Mon Jul 04 02:53:28 EDT 2016
password=
username=

Provide proper username and password then save the file in the

"/home/oracle/MWHome/user_projects/domains/bifoundation_domain/servers/AdminServer/security/"
 location.

Do the same for bi_server1

Then restart Admin and bi_server1

Then bi server can load the credentials from boot.properties file.

[Solved][Error INST-08058]: A lookup of the address for this machine returned an IP address rather than a hostname.]

Error: Got the following error while scaling the BI server in weblogic in step scale  Outt BI system.
         
error:INST-08058: A lookup of the address for this machine returned an IP address rather than a hostname.

Cause: The machine is not able to identify the host name while configuring BI Server.

Solution: Edit /etc/hosts file in both machines the one we are extending the domain and the one we installed our weblogic server

And added the following entries in the file.

ip hostname hostname.domainname(of the working machine)
ip hostname hostname.domainname(of the machine taht we want to connect)

Then proceed with the installation.

Patching OBIEE 11g in 4 steps.

Step 1: Download the required patch from oracle.

Backup OBIEE Installation
Backup the current OBIEE installation. In particular, the "Read Me" highlights the following:

FMW_HOME\Oracle_BI1\bifoundation\server directory

 FMW_HOME\instances\instance1\bifoundation\ OracleBIServerComponent\coreapplication_obis1\repository

FMW_HOME\Oracle_BI1\bifoundation\jee\mapviewer.ear\ web.war\WEB_INF\conf\mapViewerConfig.xml

Step 2: extract the patch and you can see more compressed files.Extract each zip files and put the files in some folder inside Oracle_BI1,(Please gave folder name without spaces)

Step 3: Down BI Services(Admin and managed server) and Open cmd in admin mode and navigate to oracle_BI1

 then set the environment variables as shown in below screen shot

For Linux environment

For Windows environment

Step 4: Navigate to the folder where you copied the patches and from inside the patch folder run opatch apply command

separately navigate to each patch folder and run opatch apply command.

You can see Opatch succeeded after each patch.


After applying all patch verify patches using the command

opatch lsinventory|grep applied

Now start BI services and verify the version of OBIEE from administrator.

Thank you.

[SOLVED] [BEA-090174] :The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml. in Linux

Error : After enabling SSL in OBIEE the SSL enabled URL is not working. In the admin and bi server start up log we got the following error

 "<BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>"

Cause: The keystore that specified in the Admin server is not matching with the one in boot.properties file, In our case admin server is configured to use Custom Identity and Custom Trust file but boot.properties file pointing to Demo certificates. 

Solution: Edit the boot.properties file in Admin and BI server. 

boot.properties file location: /home/oracle/MWHome/user_projects/domains/bifoundation_domain/servers/(select your server)/security/

Remove the tag TrustKeyStore=DemoTrust

Do the change in admin and bi_server after save the file and restart the services.

After restarting you can see Admin server can load the certificates from the mentioned locations as shown below.

Hope this will solve your issue.

Linux Commands to stop and start OBIEE11g and Managed servers.

------------Opmnctl stop--------------------------------

$ cd /home/oracle/MWHome/instances/instance1/bin/
$ ./opmnctl stopall


-----------Stop Managed weblogic---------------------

----bi_server1---------
$ cd /home/oracle/MWHome/user_projects/domains/bifoundation_domain/bin/
$ ./stopManagedWebLogic.sh bi_server1 t3://host name:7001 user_name Password

----odi_server1---------
$ ./stopManagedWebLogic.sh odi_server1 t3://host name:7001 user_name Password


------------Stop Admin server-------------------------
$ ./stopWebLogic.sh user_name Password t3://hostname:7001

-----------Stop Node Manager---------------------
$ ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15
$ kill -9 ****

------------Start Node Manager----------------------

$ cd /home/oracle/MWHome/wlserver_10.3/server/bin/

$ nohup ./startNodeManager.sh > Node_manager.out &

------------Start Admin server----------------------
$ cd /home/oracle/MWHome/user_projects/domains/bifoundation_domain/bin/
nohup sh startWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=Password > admin_server.log &

[Start up logs will be written to admin_server.log in the same directory]


to check the log :tail -f admin_server.log

ctrl-z or ctrl-c to exit log window


-----------Start Managed Server-------------

-----bi_server1----------------
$ nohup sh ./startManagedWebLogic.sh bi_server1 t3://localhost:7001 > managed_server_bi.log &

----odi_server1----------------
$ nohup sh ./startManagedWebLogic.sh odi_server1 t3://localhost:7001 > managed_server_odi.log &


---------Start Opmnctl----------------
$ cd /home/oracle/MWHome/instances/instance1/bin/
$ ./opmnctl startall



courtesy:http://hareeobiee.blogspot.in/2013/10/stop-and-start-obiee-11g-linux.html

[SOLVED] ODI-17517: Error during task integration in ODI 11g

Error: ODI-17517: Error during task integration in ODI 11g.

Cause: No physical schema is mapped as default for the data server in physical architecture.

Solution : From topology select Physical Architecture and select the data server corresponding to your technology.

There can be multiple physical schema. Select the one that you are working and check the tick box Default.