Automating the OAS System

Posted on By Adrian Ward

Oracle Analytics Server Estate

If you have chosen the Analytics Server route, either installed on your kit, or on Cloud virtual machines then you will be running the install yourself, and the patching, and the upgrading, and bug fixing.

One of the key benefits of this approach is that it grants you a higher degree of stability and control. Unlike relying on the latest updates from a cloud provider, you can customize and configure your environment to meet your specific needs. This flexibility enables you to create multiple test scenarios, setting up a robust Dev => System Test => Regression Test => User Testing => Live route. Moreover, you can establish your own disaster recovery procedures to ensure business continuity.

Having six Oracle Analytics Cloud (OAC) instances and keeping them up to date could be quite expensive. However, managing your own Analytics Server can result in substantial savings. These savings come from reducing the time spent on building and updating systems, minimizing downtime, and decreasing the cost of defects being introduced. Additionally, you can reduce cloud compute costs by optimizing the performance of your on-premises or cloud-hosted analytics servers.

Furthermore, this approach allows you to fully leverage your existing hardware and infrastructure investments, avoiding the recurring costs associated with cloud services. You also gain the freedom to integrate with other on-premises systems and customize your analytics environment to better align with your organization’s requirements.

In summary, managing your own Analytics Server might initially seem daunting, but with proper planning and execution, it can be a cost-effective solution. By taking control of the installation, patching, upgrading, and bug fixing processes, you can achieve stability, flexibility, and significant cost savings. So, embrace the opportunity to create a tailored analytics environment that meets your specific needs and empowers your organization to thrive.

Automating Installation and Configuration

The install process consists of six main parts, followed by configuration, and then deployment.

  1. Install java
  2. Install Weblogic
  3. Install OAS
  4. install Patches
  5. Install Repository (rcu)
  6. Create Domain
  7. Configure OAS

All of these steps can automated, including the configuration of your installed system. That includes the activities you would normally do using the Weblogic console or Enterprise Manager (em).

Install Script

So lets get stuck into an example, using windows.

The below can be placed into a batch file.

E:\jdk-8u431-windows-x64.exe

E:\java\jdk-1.8\bin\java.exe -jar .\fmw_12.2.1.4.0_infrastructure.jar

E:\java\jdk-1.8\bin\java.exe -jar F:\6880880\opatch_generic.jar -silent oracle_home=F:\oas

E:\java\jdk-1.8\bin\java.exe -jar F:\Oracle_Analytics_Server_2024_Windows.jar

set ORACLE_HOME=F:\oas
set JAVA_HOME=E:\java\jdk-1.8
set PATH=%ORACLE_HOME%\bin;%PATH%
set PATH=%JAVA_HOME%\bin;%PATH%
set PATH=%ORACLE_HOME%\OPatch;%PATH%

#Apply the latest Patches
F:\OAS_SPB_7.6.0.0.241009\tools\spbat\generic\SPBAT\spbat.bat -phase apply -oracle_home F:\oas

set JAVA_HOME=E:\java\jdk-1.8

#Install the RCU Schema
F:\oas\oracle_common\bin\rcu -silent -responseFile F:\automate\rcuResponseFile_addidici.properties  -f F:\automate\passwords.txt

F:\oas\bi\bin\config.cmd -silent -responseFile F:\automate\addidici_domain.rsp

The above scripts uses some input files to help with the rcu and the domain creation.

The good news is that config files can be produced in a development environment. Here is one I created

The domain Response File can be edited

Configuration

The config activities will vary depending on your setup. For this we use the Weblogic Scripting tools, wlst.

The simple way to do this is run a script that will cd to the wlst folder, run wlst and include a python script. here is an example script to add a user

connect("weblogic","Password Here","t3://192.168.0.999:9500")
edit()
serverConfig()
successCount=0
usrName="Adrian"
pwd="User_Password1"
desc="Test Python script to create user"
grpName1="Administrators"

cd('/SecurityConfiguration/Addidici/Realms/myrealm/AuthenticationProviders/DefaultAuthenticator')
cmo.createUser(usrName,pwd,desc)
print usrName,'- been created' 
cmo.addMemberToGroup(grpName1,usrName)
print grpName1, '- been assigned to ',usrName
successCount=successCount+1
print str(successCount)+" users successfully created"

There are dozens of config options, and updates that can be done, for example to logging. ALl of these can be done using wlst. Its not easy to find what scripts you can use. The basic outline of the file is:

edit()
startEdit()
cd('into a folder)
dosomething()
save()
activate()
exit()

References

Here are some links that explain how to use the Oracle Repository Creation Utility (RCU) in silent mode:

  1. Running Repository Creation Utility from the Command Line
  2. Running Repository Creation Utility from the Command Line (Oracle Documentation)
  3. Running Repository Creation Utility from the Command Line (Oracle Documentation)

Here are some links that explain how to use the WebLogic Scripting Tool (WLST) to update your realm:

  1. Using the WebLogic Scripting Tool – Oracle
  2. Using the WebLogic Scripting Tool – Oracle Documentation
  3. WebLogic Server 12c (12.2.1): Using the WebLogic Scripting Tool

Oracle Analytics