Namaste!! Welcome back to My Oracle Fusion Middleware Experiments blog. This post is for Novice OAS domain users, who just started working on the OAS domain. You might face this issue when you have an OAS domain running which was configured by someone and you have newly joined the team, and due to some reason the Linux box rebooted!
Contents
- Introduction
- Prerequisites/Assumptions
- Control Flow
- Start, Stop, and Status of BI server
- Alternate Options
- Checking Status
- Troubleshooting: status STARTING forever
- Check WebLogic Server PID, JAVA_OPTION
- Summary
Introduction
OAS (Oracle Analytics Services) Domain is a WebLogic domain, that consists of AdminServer and bi_server as managed server which associated with five Business Intelligence (BI) components (OBIPS, OBIJH, OBICCS, OBISCH, OBIS). Arrangement of the components are shown in the image below.
Prerequisites/Assumptions
- Oracle Analytics Server installed or OBIEE (legacy)
- Connected database up and running
Control Flow
Starting and stopping of services follows the order as shown in the image below. The process started first will be stopped last.
Control is managed using the bash scripts start.sh (used for starting the servers), stop.sh (used for stopping the servers) and status.sh (used to find the status at any point of time) which internally call WLST script.
Start, Stop, and Status of BI server
- ./start.sh, ./stop.sh, ./status.sh
- Navigate to the OAS domain usually this will be in your Oracle Middleware Infrastructure installed path, then you have the 'user_projects/domains/oas_domain'
- Navigate to the bitools/bin directory from the oas_domain directory.
- -i <list of instances>, -r <restartIntervalSeconds>, -m <restartMaxValue>, -c <flush the cached credentials>
Alternate Options
- FMW (Fusion Middleware) is an alternative for starting and stopping BI server.
- Oracle Fusion Middleware offers complete support for development, deployment, and management.
- It provides Oracle WebLogic Server, an enterprise-ready Java application server that supports the deployment of mission-critical applications in a robust, secure, highly available, and scalable environment.
- Login to http://host_name:port/em for FMW control.
- FMW provides multiple options compared to cmd as shown in the image below.
Checking Status
Troubleshooting
1. Status STARTING forever
2. If ./stop.sh doesn't stop the server: failed to connect to Node manager
Check WebLogic Server PID, JAVA_OPTIONS
- Use the Linux ps command: ps –ef|grep oas_domain
- Java Utility to get Java process state with jps command: jps –lv |grep oas_domain
