Using the Nodemanager / Weblogic

In certain cases you need to use the node manager to start/stop weblogic servers, the common commands:

sh startNodeManager.sh
 java weblogic.WLST
nmConnect(‘weblogic’, ‘password’, ‘localhost’, ‘5556’, ‘base_domain’ , ‘C:\\Oracle\\Middleware\\user_projects\\domains\\base_domain’ , ‘ssl’)
nmStart(‘AdminServer’)
nmServerStatus(‘AdminServer’)
connect(‘weblogic’,’weblogic123′)
start(‘Server-0′,’Server’)
start(‘mycluster’, ‘Cluster’)
nmKill(‘Server-0‘)
nmKill(‘AdminServer‘)
nmDisconnect()
exit()

To find node manager process :
For windows
netstat -ao| findstr 5556
TCP    ajit:5556              ajit:0                 LISTENING       1900

here : PID – 1900.

For Linux/unix :

netstat -an | grep -v grep | grep weblogic.NodeManager

How to change the 'weblogic' user password in OBIEE 12C environment?

Here's the procedure.

1. Login into EM(Enterprise Manager) using URL http://machinename:port/em
   • Navigate to the left hand side top corner below Oracle Logo
   • Click on a hierarchy like structure named as "Target Navigator".
   • On "Target Navigation" page, go to 'Business Intelligence' and Expand the same-->
   • Then click on "biinstance"--> biinstance page;
   • Go to "Availability" tab and click on "Stop All".
   • On the "Confirmation" window stating as "Are you sure you want to stop all BI components?", click "Yes" and wait for BIEE Components to stop.

NOTE: The above list of steps in point(1) can also be performed through command line following below command:

• • Navigate to following location from command console <ORACLE HOME>\user_projects\domains\<domain_name>\bitools\bin
  • Once in above location execute below command depending on your operating system:
• For Windows, execute the command: stop.cmd -i obips1,obis1,obiccs1,obisch1,obijh1
• For Linux, execute the command: ./stop.sh -i obips1,obis1,obiccs1,obisch1,obijh1

       2. Once the BI components are stopped from EM/Command Console, login into Weblogic Admin Console using the URL http://machinename:port/console and follow the below steps:

• • On the left hand side of the Home page, go to "Domain Structure"-->Environment-->Servers
  • On "Summary of Servers" page, go to "Control" tab and select "bi_server1" in the list
  • From the available options on top of list of servers, click on "Shutdown"-->and then click on "Force Shutdown Now"
  • Wait for the Managed Server(bi_server1) to shutdown gracefully before proceeding ahead with further steps.

               NOTE: The above list of steps in point(2) can also be performed through command line following the below command:

• • Navigate to following location from command console-        

                        <ORACLE HOME>\user_projects\domains\<domain_name>\bitools\bin

• • From the above mentioned location, execute the below command depending on your operating system:

• for Windows execute command: stop.cmd -i bi_server1
• for Linux execute command: ./stop.sh -i bi_server1 

3. Now from the WLS Admin Console, change the weblogic user password following the below steps:

1. • Navigate to the left hand side under "Domain Structure"-->Security Realms-->myrealm-->Users and Groups-->
   • Under "Users" tab, search for "weblogic" user and click on same.
   • Upon clicking the "weblogic" username, the "Settings for weblogic" page will open
   • Navigate to "Password" tab
   • Enter a new password in "New Password:" and "Confirm New Password:" tabs and click on "Save".

       4.Now from the WLS Admin Console, stop the Admin Server following the below steps:

• • In Admin Console, on left hand side under "Domain Structure"-->Environment-->Servers.
  • On "Summary of Servers" page, go to "Control" tab and select "Admin Server" in the list
  • From the available options on top of list of servers click on "Shutdown"-->and then click on "Force Shutdown Now".

       5. Navigate to the below location in OBIEE Oracle Home and carry out below actions:

• • In location \user_projects\domains\<domain_name>\servers\AdminServer\security, backup all the files present and then delete the files (as it carries old password details for weblogic user).
  • In location \user_projects\domains\<domain_name>\servers\bi_server1, backup "data" directory by renaming the directory, so that a new data directory is created in next startup of Managed Server(bi_server1).
  • In the same location as above, go to "security" directory and backup all the files if any, present there and then delete the files.

      6. Now start OBIEE 12c Stack using the below steps:

• Navigate from command console to the following location ORACLE HOME>\user_projects\domains\<domain_name>\bitools\bin
• Execute the below command depending on your environment :
  • for Windows, execute command: start.cmd
  • for Linux, execute command: ./start.sh
• When you execute command start.cmd/start.sh, it will prompt you for Admin User's username and password
• Enter the new details and move ahead with server start up.
• Once all the servers and services are up and running, verify the access of application with newly configured password.

OBIEE 12C behaves different than OBIEE 11g, the start and stop scripts have changed, so

Stopping OBIEE 12c:

Go to the directory: [ORACLE_HOME]/user_projects/domains/bi12/bitools/bin

Unix: ./stop.sh or ./stop.sh -i obis1,obips1

Command Prompt: stop.cmd or stop.cmd {-i <list of instances>} {-r}

Note: If no instances are specified as arguments in the command, 
the administration server, managed server and all system components are shutdown by default.

Starting OBIEE 12c

[ORACLE_HOME]/user_projects/domains/bi12/bitools/bin

./start.sh | start.cmd {-noprompt} {-i <list of instances>} {-r}

For example, ./start.sh -i obis1,obips1
If no instances are specified as arguments in the command,
the administration server, managed server, all system components, and local node manager are started by default.

Status of OBIEE 12c Services (All Weblogic)

./status.sh | status.cmd {-v}

where {-v} is verbose

The command displays component name, type, status, and machine name.

Credits:

http://yyadav05.blogspot.mx/

Create custom metadata profile in WCC

Once logged in WCC

Navigate to
Administration->Admin Applets->Configuration Manager
Add the new field by clicking on Add...

This will prompt for:

Field Name, Field Caption, Field Type and so on...

Also you will be able to create an option list

A lot of options you will have, for example, validated, non validated lists, multiselect lists, edit and select. dependant values etc ...

Note:

The field order field will allow you tu allocate the field on the desired location on the user interface.

You must make sure that the Enable User Interface checkbox is enabled.

Custom Checkin, Create security group in WCC

Security Group

Access this screen using a browser, choose Administration, then Admin Applets, then User Admin.

Then start the applet:

1. To create a security group and assign permissions:
   

   1. From the User Admin Screen, select Security then Permissions by Group.
      The Permissions By Group Screen is displayed.
   2. Click Add Group to display the Add New Group Screen.
   3. Enter a group name and description.
   4. Click OK.
   5. Set permissions for the security group:
   1. Select the security group.
   2. Select the role to edit.
   3. Click Edit Permissions.
   4. After enabling the permissions that you want the role to have for the group, click OK to close the Permissions by Group screen

   
   

In my next post, I will show you how to creare a custom metadata profile in WCC.

See you.

Inplace upgrade, Reuse the existing OWB Home

The following steps are used to recover an existing OWB Home.

1.- Get the OWBSYS and OWBSYS_AUDIT users

Execute the following sentences:

2.- sqlplus OWBSYS/*****@OWB_HOME/owb/rtp/sql/stop_service.sql
chmod +x ./app/oracle/product/11.2.0/dbhome_1/owb/reposasst/secHelper.pks
chmod +x ./app/oracle/product/11.2.0/dbhome_1/owb/reposasst/secHelper.plb

chmod +x ./app/oracle/product/11.2.0/dbhome_1/owb/reposasst/upg/load_java.sql OWBSYS ***

3.- Run the following SQL statement to identify the OWB_HOME for the current installation. The rtrepos.properties file is located in the path indicated by the SERVER_SIDE_HOME of the query.

1. sqlplus OWBSYS/OWBSYS_PASSWORD
2. SELECT host_name, server_side_home from wb_rt_service_nodes s, v$instance v where s.instance_number=v.instance_number;
   HOST_NAME
   SERVER_SIDE_HOME
   yourhost_machine
   OWB_HOME

4.- For an existing repository that is installed on an Oracle 11g database (not Oracle 10g), ensure that OWB_HOME and ORACLE_SID values are pointing to the database where the repository is installed. Ensure that the PATH contains OWB_HOME/bin.

If the rtrepos.properties file is not found then:

• sqlplus owbsys/*********
• @/u01/app/oracle/product/11.2.0/dbhome_1/owb/reposasst/secHelper.pks
  @/u01/app/oracle/product/11.2.0/dbhome_1/owb/reposasst/secHelper.plb
  @/u01/app/oracle/product/11.2.0/dbhome_1/owb/reposasst/upg/load_java.sql OWBSYS *********
• @/u01/app/oracle/product/11.2.0/dbhome_1/owb/rtp/sql/reset_repository.sql *********

The reset_repository forces the user to register the location again using the Control Center Manager.

When the file is created START the service.

@/u01/app/oracle/product/11.2.0/dbhome_1/owb/rtp/sql/start_service.

Ce tout!

Integration FDMEE with ERP Fusion

Recently, I was asking to integrate FDMEE with ERP Fusion using the WSDL,

using the FusionCloudAdapter.sh and FusionCloudAdapter.py.

The ODI Log throws the following exception:


2017-10-11 13:20:36,490 ERROR [AIF]: Error in initializeFsGLCloudSource.
2017-10-11 13:20:36,491 FATAL [AIF]: Error in initializeFsGLCloudSource
Traceback (most recent call last):
  File "<string>", line 451, in initializeFsGLCloudSource
  File "<string>", line 475, in executeFusionService
  File "<string>", line 557, in executeJythonScript
  File "/u01/hyp/hyperion/EPMSystem11R1/products/FinancialDataQuality/bin/FusionCloud/FusionCloudAdapter.py", line 138, in <module>
    fusionCloudAdapter.extractCubeInformation()
  File "/u01/hyp/hyperion/EPMSystem11R1/products/FinancialDataQuality/bin/FusionCloud/FusionCloudAdapter.py", line 16, in extractCubeInformation
    self.fusionCloudHelper("extractCubeInformation")
  File "/u01/hyp/hyperion/EPMSystem11R1/products/FinancialDataQuality/bin/FusionCloud/FusionCloudAdapter.py", line 112, in fusionCloudHelper
    raise RuntimeError
RuntimeError

Reviewing OS Level and Application Level I realize that the file was asking about other permissions to be executable.

Solution:

chmod +x -Rf  * in the folder there the py  adapter  and the sh file es located.

Test the wsdl service located in cloud. -> Success.

Charms !