This is the thirteenth in a series of posts regarding installing BI Apps 188.8.131.52.2 on Oracle Linux 7.2. For your reference, here is a list of URLs for each of the posts that make up this series:
In this post, I will be discussing how to run the configuration script (configApps.sh) for OBIA silently (i.e. without a GUI).
General Assumptions and Conventions Used
I will assume that readers of this blog have read the prior blog entries in this series before continuing.
Configuring a response file
In order to configure OBIA from the command line without a GUI, you will need a response file (similar to OBIEE). I have generated a response file called configureOBIA.rsp and have posted it on my GitHub account. For the purposes of this blog series, we will download this file and store it in /u01/sw/scripts. This particular response file has already been altered to suite the installation detailed by this blog series. If you want to choose different installation paths or enter different values, the response file does contain documentation to help you do that. However, please note that this blog series will assume that the file is used as is.
There are many parameters in this response file that you may want to change and tweak. Here are some of the more important parameters and the values that I have set them to:
DOMAIN_HOSTNAME=ol72bia1111102 DOMAIN_PORT=7001 ADMIN_USER_NAME=weblogic ADMIN_PASSWORD=welcome1 MW_HOME=/u01/app/obia11g/product/11.1.1/mwhome_1 WEBLOGIC_HOME=/u01/app/obia11g/product/11.1.1/mwhome_1/wlserver_10.3 RPD_ENCRYPTION_PASSWORD=welcome1 RPD_CONFIRM_PASSWORD=welcome1 ODI_USER_NAME=biappadmin ODI_USER_PASSWORD=welcome1 ODI_USER_CONFIRM_PASSWORD=welcome1 DATABASE_CONNECTION_STRING_MDS=192.168.186.6:1521:obaw DATABASE_SCHEMA_USER_NAME_MDS=FMW_MDS DATABASE_SCHEMA_PASSWORD_MDS=fmw4DB DATABASE_TYPE_MDS=Oracle Database BIACOMP_DATABASE_CONNECTION_STRING=192.168.186.6:1521:obaw BIACOMP_DATABASE_SCHEMA_USER_NAME=FMW_BIACOMP BIACOMP_DATABASE_SCHEMA_PASSWORD=fmw4DB BIACOMP_DATABASE_TYPE=Oracle Database DW_DATABASE_CONNECTION_STRING=192.168.186.6:1521:obaw DW_DATABASE_SCHEMA_USER_NAME=FMW_DW DW_DATABASE_SCHEMA_PASSWORD=fmw4DB DW_DATABASE_TYPE=Oracle Database ODI_REPOSITORY_DATABASE_CONNECTION_STRING=192.168.186.6:1521:obaw ODI_REPOSITORY_DATABASE_SCHEMA_USER_NAME=FMW_BIA_ODIREPO ODI_REPOSITORY_DATABASE_SCHEMA_PASSWORD=fmw4DB ODI_REPOSITORY_DATABASE_TYPE=Oracle Database
Also, here is a screenshot of a portion of the response file:
Again, like with the OBIEE Configuration, I would caution you against using special characters (specifically '$' but there may be others) for use as passwords.
Running the OBIA configuration script (configApps.sh)
Now that we have created/downloaded the response file to /u01/sw/scripts, we can proceed with the execution of the OBIEE configuration script. In order to do so, issue the following commands from the terminal:
$ cd $MW_HOME/Oracle_BI1/bin $ ./configApps.sh -silent -invPtrLoc /u01/app/oraInventory/oraInst.loc -response /u01/sw/scripts/configureOBIA.rsp -jreLoc $JAVA_HOME -logLevel finest -debug -printdiskusage -printmemory -printtime
Here is a screenshot of a portion of the output of this command:
If the configuration is successful, you will see a line towards the end of the output that says that the configuration of Oracle Business Intelligence Shiphome, Oracle Business Intelligence Applications Shiphome has been completed successfully.
Furthermore, you will now be able to browse to the various OBIA URLs. For example, here's a screenshot of WebLogic Enterprise Manager (EM):
Here's a screenshot of the OBIEE login screen:
And here's a screenshot of the Business Intelligence Applications Configuration Manager (BIACM):
More details will be provided in my next and final blog entry in this blog series.
In this blog entry, we ran the configuration script (configApps.sh) silently (i.e. from the command line without a GUI) for OBIA 184.108.40.206.2. In addition, when the configuration process finished, we browsed to a few of the URLs that are now up and running in our OBIA environment.
In my next and final blog entry, I will show how to perform several post-installation tasks, plus I will provide an overall summary of the environment that we have created in this blog series.