Oracle Database 19c (19.3.0.0.0) Installation in Window Server

 

https://www.oracle.com/in/database/technologies/oracle19c-windows-downloads.html

How to Audit and Monitor BI Publisher Reports Access

Enable Auditing related properties in BI Publisher configuration file

1.     Open xmlp-server-config.xml file, which is located under $BI_HOME/ user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Configuration directory.

2.    Set the following three properties values to ‘true’.

·  AUDIT_ENABLED

·  MONITORING_ENABLED

·  AUDIT_JPS_INTEGRATION

The ‘AUDIT_JPS_INTEGRATION’ is not in the file as default, so you need to add this. Here is an example of how it looks for the xmlp-server-config.xml file after the modification.

 <?xml version="1.0" encoding="UTF-8" standalone="no"?><xmlpConfigxmlns="http://xmlns.oracle.com/oxp/xmlp">

<property name="SAW_SERVER" value="adc6160510"/>

<property name="SAW_SESSION_TIMEOUT" value="90"/>

<property name="DEBUG_LEVEL" value="exception"/>

<property name="SAW_PORT" value="7001"/>

<property name="SAW_PASSWORD" value=""/>

<property name="SAW_PROTOCOL" value="http"/>

<property name="SAW_VERSION" value="v6"/>

<property name="SAW_USERNAME" value=""/>

<property name="SAW_URL_SUFFIX" value="analytics/saw.dll"/>

<property name="MONITORING_ENABLED" value="true"/>

<property name="MONITORING_DEFAULT_HISTORY_SIZE" value="30"/>

<property name="AUDIT_ENABLED" value="true"/>

<property name="JSESSION_RESET_DISABLED" value="true"/>

<property name="SECURITY_MODEL" value="ORACLE_AS_JPS"/>

<property name="AUDIT_JPS_INTEGRATION" value="true"/>

</xmlpConfig>

 

Copy component_events.xml file to Audit Framework’s location

There is a Audit related configuration file provided by BI Publisher that needs to be copied to the Audit Framework location.

1.     Go to the following directory.

$BI_HOME /oracle_common/modules/oracle.iau_11.1.1/components

Create a directory called ‘xmlpserver’

Copy component_events.xml file from

/user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Audit

To

the newly created ‘xmlpserver’ directory.

Enable Auditing Policy with Fusion Middleware Control (EM)

Now you can set a level of the auditing for each BI Publisher’s auditing type by using Fusion Middleware Control (a.k.a. Enterprise Manager).

1.     Login to Fusion Middleware Control UI

http://hostname:port/em (e.g. reporting.oracle.com:7001/em)

2.     Access to Audit Policy configuration UI from the menu

Under WebLogic Domain, right-click bifoundation_domain, select Security and then click Audit Policy.

 

3.     Set Audit Level for BI Publisher.

While you can select ‘Custom’ to set a customized level of Auditing for each component, I’m selecting ‘Medium’ for this exercise.

Restart WebLogic Server

After all the above settings, now you need to restart the WebLogic Server instance in order to take those changes in effect. If you’re on Windows you can simply do this by selecting ‘Stop BI Servers’ and ‘Start BI Servers’ from the Start menu.

If you’re on Linux then you can run ‘stopWebLogic.sh’ and ‘startWebLogic.sh’, which can be found under $BI_HOME/user_projects/domains/bifoundation_domain/bin

Start Auditing!

Now assuming that you have completed the above steps successfully, then from this point on any reporting activity should be audited and stored in the auditing log file, which can be found at $BI_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/auditlogs/xmlpserver/audit.log

or 

$BI_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/auditlogs/xmlpserver/audit.log

Oracle database 11.2.0.4 download link

 Login to support.oracle.com

Go to Patches & updates tab 

Enter Patch Number 13390677 and select Platform

Click search

Download

File 1&2 is db, 3 is grid, 4 is client, 5 is gateway, 6 is example, 7 is deinstall

The selected Oracle database is not configured to use the AL32UTF8 character set

 While running the RCU, below error comes if the database is not configured to use the AL32UTF8 character set -

In order to change the character set in the database, follow the next steps.

1. Open SQLplus and login using a sysdba role

2. One by one, execute the next statements.

shutdown immediate;
startup restrict;
alter database character set internal_use AL32UTF8;
alter database character set AL32UTF8;
shutdown immediate;
startup;

3. Exit SQL Plus

How to connect to Sales Force (SFDC) From Informatica

 

In order to connect to Sales Force.com. Power Exchange SFDC  needs to be installed and  sfdc plug-in needs to be registered in Informatica Repository.Below are the steps for the same.

1. Log on to server as Informatica functional account.
2. Change directory to Informatica PowerCenter install binaries directory.
3. Ftp/Sftp sfdc_81102_sol32.tar from either local workstation or Informatica server to server where install is taking place
4. Decompress install binaries  (tar xvf sfdc_81102_sol32.tar).
5. At this point, stop integration service and repository service in the environment using admin console.
6. Execute installSFDCserver.
7. Enter Informatica home directory absolute path ($INFA_HOME).
8. Once installation has completed, return to admin console.
9. Add license key to environment using admin console.
10. Select the respective Unicode integration service, modify the HTTP Proxy Properties as follows: HttpProxyServer  ,HttpProxyPort , HttpProxyUser, HttpProxyPassword, HttpProxyDomain.

• Start repository service.
• Start integration service.
• Log into repository using Workflow manager.
• Validate that salesforce.com connection is now an option under application type connections in workflow manager.
• Log into repository using Designer.
• Validate that you can import a source from salesforce.com, and that it is now an option in source analyzer.
• If both workflow manager and designer allow these options, installation is complete.

 Below Is the Installation Output :

$INFA_HOME/server/tomcat/bin/SFDC_81102_Sol32

Stop all the Powercenter processes/Services before running this script ....

Enter absolute path of Powercenter server installation directory{/home/powercenter8.1.1}

$INFA_HOME

server location:$INFA_HOME

backing up $INFA_HOMEserver/bin/native/pmsfdc.xml as $INFA_HOME/server/bin/native/pmsfdc.xml.bak

copying files to $INFA_HOMEserver/bin/native folder

backing up $INFA_HOMEserver/bin/libpmsfdccmn.so as $INFA_HOME/server/bin/libpmsfdccmn.so.bak

backing up $INFA_HOMEserver/bin/libpmsfdclkp.so as $INFA_HOME/server/bin/libpmsfdclkp.so.bak

backing up $INFA_HOMEserver/bin/libpmsfdcrdr.so as $INFA_HOME/server/bin/libpmsfdcrdr.so.bak

backing up $INFA_HOMEserver/bin/libpmsfdcwrt.so as $INFA_HOME/server/bin/libpmsfdcwrt.so.bak

backing up $INFA_HOMEserver/bin/pmsfdc_EN.cat as $INFA_HOME/server/bin/pmsfdc_EN.cat.bak

backing up $INFA_HOMEserver/bin/pmsfdc_JA.cat as $INFA_HOME/server/bin/pmsfdc_JA.cat.bak

copying files to $INFA_HOMEserver/bin folder

cp: server/bin/native: is a directory

Installation completed successfully.

IMPORTANT: If you are upgrading from 8.1.1 please re-register the Salesforce.com plug-in pmsfdc.xml for changes to take effect.

 

 Below are the steps to register the sfdc plugin to Repository :

• Get the pmsfdc.xml from Informatica Vendor.

• FTP the pmsfdc.xml file in binary mode and place it to Informatica server $INFA_HOME/server/bin/native/ path. (Make sure to FTP the sfdc plug in binary mode).

• Bring down the Integration Service.

• Bring the repository service to Exclusive mode from Normal mode. 

• Connect to the repository using the pmrep connect command.

              pmrep>connect -r "LAB_INFA_REP" -d "LAB_INFA_DOMAIN" -n Administrator -x password

• Now register the plugin using the registerplugin command.

             pmrep>registerplugin -i $INFA_HOME\server\bin\native\pmsfdc.xml -e -N 

(Note : Give the fully qualified path otherwise will get the above error Failed to execute registerplugin )

Register Plug-in operation on repository [LAB_INFA_REP] started at **/**/**** 00:00:00.

Importing plugin: SalesforcePlugin ...
Importing dbtype: Salesforce ...
Importing keytype: SOURCEID ...
Importing keytype: TARGETID ...
Importing keytype: SOURCEREFERENCE ...
Importing keytype: TARGETREFERENCE ...
Importing datatype: id ...
Importing datatype: id ...
Importing datatype: id ...
Importing datatype: id ...
Importing datatype: id ...
Importing datatype: id ...
Importing datatype: id ...

Post validation on imported plug-ins...
The number of plug-ins that registered successfully is 1.
The number of plug-ins that failed to register is 0.
Register Plug-in operation on repository [LAB_INFA_REP] ended at **/**/**** 00:00:00. Elapsed time is 0:00:03.
registerplugin completed successfully.
pmrep>exit

Authentication denied: Boot identity not valid (OBIEE service startup issue)

 

If getting any of the below error in log–

<Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid.

Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied

<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid.

Authentication denied: Boot identity not valid

Then check the boot.properties file under security folder and data/nodemanager folder if they have been changed recently, edit boot.properties and change the password.

Boot.properties location –

/<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/AdminServer/security/boot.properties

/<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/security/boot.properties

/<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/data/nodemanager/boot.properties 

Backup and remove ldap folder from -

 /<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/data/

OBIEE services Start/Stop script

=========================================================================

                                                            Stop services

=========================================================================

---------------------------------Step 1 Stop OPMN Components-----------

If its a clustered environment then stop opmnctl in all nodes.

cd /<MiddlewareHome>/instances/instance1/bin

./opmnctl stopall

(wait until the prompt is back)

--------------------------------Step 2 Stop Node Manager---------------

If its a clustered environment then kill the process in all nodes.

ps -ef |grep NodeManager

kill -9 <number of process above>

--------------------------------Step 3 Stop Managed Server---------------

cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

./stopManagedWebLogic.sh <bi server name>

eg.- ./stopManagedWebLogic.sh bi_server1

If its a clustered environment -

./stopManagedWebLogic.sh bi_server1 t3://weblogic.hostServerNname:7001

./stopManagedWebLogic.sh bi_server2 t3://weblogic.hostServerName:7001

If boot.properties are not set then provide user and password in the argument -

./stopManagedWebLogic.sh bi_server1 t3://obieenode1.com:7001 weblogic password

./stopManagedWebLogic.sh bi_server2 t3://obieenode1.com:7001 weblogic password

Verify that the Managed Server has shutdown completely in both nodes with -

ps -ef | grep bi_server1

ps -ef | grep bi_server2

-------------------------Step 4 Stop Admin Server------------------

Only in node1-

cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

./stopWebLogic.sh

If boot.properties are not set then provide user and password in the argument -

./stopWebLogic.sh weblogic password t3://obieenode1.com:7001

(wait until the prompt is back)

------------------------Kill any running processes----------------------------

Check if any process is running in all nodes. 

ps -ef | grep -v grep | grep -i weblogic.NodeManager

ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15

ps -ef | grep AdminServer

=========================================================================

                                                              Start Services

=========================================================================

-------------------------Step 1 Start Admin Server------------------

only on node1 -

cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

nohup ./startWebLogic.sh &

tail -1000f nohup.out

or - log path can be provided -

nohup ./startWebLogic.sh > /service_logs_path/startWeblogic.log 2>&1 &

tail -1000f /service_logs_path/startWeblogic.log

or - if boot.properties are not set then provide user and password in the argument -

nohup ./startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startWeblogic.log 2>&1 &

tail -1000f /service_logs_path/startWeblogic.log

Output -

<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

--------------------------------Step 2 StartNode Manager---------------

If its a clustered environment then run on all nodes.

cd /<MiddlewareHome>/wlserver_10.3/server/bin/

nohup ./startNodeManager.sh &

tail -1000f nohup.out

or - log path can be provided -

nohup ./startNodeManager.sh > /service_logs_path/startNodeManager.log 2>&1 &

tail -1000f /service_logs_path/startNodeManager.log

Output -

<Info> <Secure socket listener started on port ####>

-----------------------------------Step 3 Start Managed Server------------

cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

nohup ./startManagedWebLogic.sh bi_server1 &

tail -1000f nohup.out

or - log path can be provided -

nohup ./startManagedWebLogic.sh bi_server1 > /service_logs_path/startManagedWebLogic.log 2>&1 &

tail -1000f /service_logs_path/startManagedWebLogic.log

If its a clustered environment then (obieenode1 is node1_hostname) -

nohup ./startManagedWebLogic.sh bi_server1 t3://obieenode1:7001 &

nohup ./startManagedWebLogic.sh bi_server2 t3://obieenode1:7001 &

nohup -1000f nohup.out

or - if boot.properties are not set then provide user and password in the argument -

nohup ./startManagedWebLogic.sh bi_server1 t3://obieenode1:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startManagedWebLogic.log 2>&1 &

nohup ./startManagedWebLogic.sh bi_server2 t3://obieenode1:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startManagedWebLogic.log 2>&1 &

nohup -1000f /service_logs_path/startManagedWebLogic.log

Output-

Server started in RUNNING mode

---------------------------------Step 4 Startup OPMN Components-----------

If its a clustered environment then run on all nodes.

cd /<MiddlewareHome>/instances/instance1/bin

./opmnctl startall

Check status -

./opmnctl status

Output -

------------------------------------+-------------------------+----------+---------

ias-component                         | process-type              |    pid      | status

------------------------------------+-------------------------+----------+---------

coreapplication_obisch1          | OracleBIScheduler~  |    xxxx | Alive

coreapplication_obiccs1          | OracleBIClusterCo~  |    xxxx | Alive

coreapplication_obips1            | OracleBIPresentat~   |    xxxx | Alive

coreapplication_obijh1            | OracleBIJavaHostC~ |    xxxx | Alive

coreapplication_obis1             | OracleBIServerCom~ |    xxxx | Alive

Start any particular opmnctl component -

./opmnctl startproc ias-component=coreapplication_obisch1

or stop -

./opmnctl stopproc ias-component=coreapplication_obisch1