HOW TO: Startup bi publisher 11g from scratch

I have collected a compilation of 'how to startup bi publisher' though to also proceed with the troubleshooting process if BI publisher is unavailable.
August 6, 2013
Bi-Publisher-11g

All of the steps were highlighted within the previous post on How to startup Bi Publisher. The below are the steps that elaborate in more detail on how to startup the bi publisher but also to troubleshoot if the normal process on startup fails.


1. Database is up and running

Ensure the bi publisher with the bi database user is up and running. I have below an example of a shell script that can be used to startup the database and it's respective services.

#!/bin/sh
clear
sqlplus sys/password as sysdba <<ENDOFSQL

startup;
exit;
ENDOFSQL

emctl stop dbconsole; emctl start dbconsole; lsnrctl stop; lsnrctl start;
sleep 60s

clear
lsnrctl status;

echo 'now starting up Weblogic domains'

sleep 1s


2. BI Publisher services

Once the database has started up, the next thing is the ensure that the bi publisher listeners are up and alive.

[oracle@localhost bin]$ ./opmnctl startall
opmnctl startall: starting opmn and all managed processes...
[oracle@localhost bin]$ pwd
/home/oracle/Oracle/Middleware/instances/instance1/bin
[oracle@localhost bin]$ ./opmnctl status

Processes in Instance: instance1
---------------------------------+--------------------+---------+---------
ias-component | process-type | pid | status
---------------------------------+--------------------+---------+---------
coreapplication_obiccs1 | OracleBIClusterCo~ | 4250 | Alive
coreapplication_obisch1 | OracleBIScheduler~ | 4248 | Alive
coreapplication_obijh1 | OracleBIJavaHostC~ | 4247 | Alive
coreapplication_obips1 | OracleBIPresentat~ | 4251 | Alive
coreapplication_obis1 | OracleBIServerCom~ | 4249 | Alive


3. Startup WLS Server

The following commands within the terminal started up bi publisher

[oracle@localhost bin]$ cd /home/oracle/Oracle/Middleware/user_projects/domains/bifoundation_domain/ [oracle@localhost bifoundation_domain]$ ./startWebLogic.sh


4. Startup bi Managed Server

The following steps startup bi's managed Server

[oracle@localhost bin]$ cd /home/oracle/Oracle/Middleware/user_projects/domains/bifoundation_domain/ You have new mail in /var/spool/mail/oracle [oracle@localhost bifoundation_domain]$ ./startManagedServer bi_server1

Note: You Will notice the port number along with the hostname within the terminal console.

Channel "Default" is now listening on 172.16.101.252:9704 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.

you can use to access the following URL within your web browser

http://172.16.101.252:9704/xmlpserver

Analytics URL

http://172.16.101.252:9704/analytics/saw.dll?bieehome

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

NameID element must be present as part of the Subject in the Response message

ShibbolethSAML

August 7, 2018
Created by: Daniel Redfern
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...

HOW TO provision AD group membership from OpenIDM

OpenIDMICFAD-connector

June 15, 2018
Created by: Daniel Redfern
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...