v1.1.0 | Released on 2018.11.10

0. Introduction


WL-OPC (WLSDM OPERATION CENTER) is the central Operation and Notification system which enables to manage Application Server infrastructure;

You are going to able to manage, organize and visualize;

  • WebLogic Domains Asset Management
  • WebLogic AdminServer Monitoring
  • Central WLSDM Notification Broadcasting
  • Report WebLogic Domain Performance and Availability
  • Compare WebLogic JVM Arguments
  • and more...

1. Key Feature List

One console to rule all your Oracle FMW Infrastructure! One console to find all notifications; One console to bring all FMW WebLogic domains together

...in the WL-OPC console bind and manage:

2. Prerequisites

  1. Arrange one server/machine with below configuration:
    1. Server/Machine OS (64-bit): Supports Linux, Unix, Windows and macOS platforms. Linux (64-bit Oracle Linux, Red Hat VM) OS is recommended.
    2. Minimum 4 CPU Core. 8 CPU Core is recommended.
    3. Minimum 8 GB Memory/RAM. 12 GB Memory is recommended.
    4. Minimum 40 GB disk. 80 GB /u01 disk is recommended. (External i.e. /u01 or /data mount point)
  2. Create OS user/group. (opc:opc with /u01/opc home path is recommended.)
  3. Download latest compatible JDK 1.8.X with your OS platform.
  4. Give network access and server firewall access to server's WL-OPC port (8080) or proxy webserver port (80,443) in your local network. (Default WL-OPC application server port is 8080, recommended webserver port is 80 if applicable)
  5. OPTIONAL: Download OS compatible proxy webserver (i.e. NGINX, Apache HTTP Server...) to install and configure in front of WL-OPC application server. (NGINX proxy webserver is recommended)
  6. IMPORTANT: Give below network access in between WL-OPC server and WebLogic AdminServer(s).
    FROM:WL-OPC Server IP Address
    TO: WebLogic AdminServer IP Addresses : PORT (Multiple IP:PORT | Apply to all WebLogic domains which are going to be added to WL-OPC)
    FROM:WebLogic AdminServer IP Address (Multiple IP:PORT | Apply to all WebLogic domains which are going to be added to WL-OPC)
    TO:WL-OPC Server IP Address : PORT
    Note: Assign WL-OPC's server IP address subnet which is able to mostly access WebLogic AdminServer IP:PORT addresses and vice versa.
  7. OPTIONAL: If you are not preferring to install proxy webserver then define local "Load Balancer IP: 80" serving to only one node which is WL-OPC server IP and PORT.
  8. Register local intranet DNS record according to the preferred proxy configuration as below (choose one):

3. Installation

JDK Installation Path/u01/opc/jdk/jdk1.8.0_172
WL-OPC Extract Path/u01/opc/wl-opc
OS User/Groupopc:opc
  1. Download latest JDK 1.8.X and upload to server
  2. Install JDK to folder and test the JDK installation (OS User: opc:opc)
    							$ mkdir -p /u01/opc/jdk
    $ tar xzvf /tmp/jdk-8u172-linux-x64.tar.gz -C /u01/opc/jdk/
    $ /u01/opc/jdk/jdk1.8.0_172/bin/java -d64 -version
    java version "1.8.0_172"
    Java(TM) SE Runtime Environment (build 1.8.0_172-b11)
    Java HotSpot(TM) 64-Bit Server VM (build 25.172-b11, mixed mode)
  3. Extract (=Unzip) WL-OPC zip package to path
    							$ unzip -d /u01/opc /tmp/wl-opc.v1.0.4.zip
  4. Edit bash_profile of "opc" OS user
    							###Reference/Sample Linux PATH Configuration:
    vi ~/.bash_profile
    export JAVA_HOME
    export WLOPC_HOME
    export PATH
  5. Load new bash profile and test OS user PATH settings
    							[[email protected] ~]$ cd
    [[email protected] ~]$ . .bash_profile
    [[email protected] ~]$ echo $JAVA_HOME $WLOPC_HOME
    /u01/opc/jdk/jdk1.8.0_172 /u01/opc/wl-opc
    [[email protected] ~]$ which java 
    [[email protected] ~]$ which opc
  6. Go to $WLOPC_HOME/bin folder and edit "opc" command executable file. JAVA_HOME, WLOPC_HOME and SERVER_ADDRESS environment variables are empty for the first installation. This variables has to be applied according to the OS environment. Set below environment variables with the proper values.
    							[[email protected] ~]$ vi $WLOPC_HOME/bin/opc
    ###### Set WL-OPC Environment Variables
    export JAVA_HOME="/u01/opc/jdk/jdk1.8.0_172"   #set JDK installation full path
    export WLOPC_HOME="/u01/opc/wl-opc"            #set zip file's extracted full path
    export SERVER_ADDRESS=""           #set server IP address
    Note: Initial JVM -Xms and -Xmx memory arguments has been already configured as 4 GB initial/max heap size. This initial JVM memory setting is also recommended. According to your traffic and WebLogic domain stack, you can increase heap size of WL-OPC.

    In the "opc" executable file you are able to change below environment variables;
  7. Start WL-OPC application via opc command.
    							[[email protected] ~]$ opc start
  8. Note: NOHUP command is already used in the opc executable file. Do not start the opc script with the additional NOHUP command. "opc start" tails OUT log file by default; you can freely use "CTRL+C" to exit tail console. The OPC background daemon process will continue to work. Check opc process: ps -ef | grep wl-opc
    							opc command usage: /u01/opc/wl-opc/bin/opc {start|stop|backup|upgrade|tlogs}
    START_____: [[email protected] ~]$ opc start
    STOP______: [[email protected] ~]$ opc stop
    BACKUP____: [[email protected] ~]$ opc backup
    UPGRADE___: [[email protected] ~]$ opc upgrade
    TAILLOGS__: [[email protected] ~]$ opc tlogs
  9. After starting WL-OPC application server. Open web browser and go to: http:// $SERVER_ADDRESS : $SERVER_PORT / $SERVER_CONTEXTPATH (i.e.
  10. Login to WL-OPC Console with the default super user:
    							Username: admin
    Password: wl-opc
  11. In the first login WL-OPC wizard is available. Complete WL-OPC configuration wizard to setup WL-OPC infrastructure.
  12. Network Access: Check below network access on the related servers.
    							On WL-OPC Server: telnet $WebLogic_AdminServer_IP $AdminServer_PORT 
    On WebLogic Admin Server(s): telnet $WL-OPC_Server_IP $WL-OPC_PORT
  13. Finally follow instructions in the WL-OPC console to register WebLogic domains if network access is given for the related network IP routes.

4. NGINX WL-OPC Configuration

  1. Install NGINX on the WL-OPC server.
  2. Configure WL-OPC virtual host as below and apply your environment settings.
    							server {
            listen 80;
            root /var/www/wlopc;
            index index.html index.htm;
            # Make site accessible from http://localhost/
            server_name opc.company.com;
            location / {
                    # First attempt to serve request as file, then
                    # as directory, then fall back to displaying a 404.
                    # try_files $uri $uri/ =404;
                    # Uncomment to enable naxsi on this location
                    # include /etc/nginx/naxsi.rules
    		proxy_set_header X-Real-IP $remote_addr;
    		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    		proxy_set_header Host $http_host;
    		proxy_set_header X-NginX-Proxy true;
    		proxy_pass http://$WL-OPC_Server_IP:8080/;
    		proxy_redirect off;
    		# Socket.IO Support
    		proxy_http_version 1.1;
    		proxy_set_header Upgrade $http_upgrade;
    		proxy_set_header Connection "upgrade";
    		rewrite ^/(.*)$ http://opc.company.com/opc redirect;

5. Upgrade

  1. Run "opc stop" command to STOP WL-OPC.
  2. Run "opc backup" command to take full WL-OPC backup.
    Note: Existing opc executable file's backup will be available in backups/backup.$dateTime folder.
  3. Extract or copy new WL-OPC package root folder to existing $WLOPC_HOME folder.
    Example: cp -fR /source-new-package/wl-opc /path/to/wl-opc(=$WLOPC_HOME)
    Note: Accept all file overwrite warnings or simply use: "cp -fR /source-new-package/wl-opc /path/to/wl-opc"
  4. Edit opc executable file by adding below parameter values.
    • Important Note: Remember to set your previous changes again in the opc file before starting new upgraded WL-OPC.
      i.e. Additional $JAVA_OPTIONS, $SERVER_CONTEXTPATH... etc.
  5. Run "opc start" command to START new upgraded WL-OPC version.

6. HOW TOs

1. Registering a WebLogic Domain

  1. Login to WL-OPC Console
  2. If there is no registered WebLogic domain; console will redirects to the "Administration > WL Domains"
  4. Enter WebLogic AdminServer's Hostname/IP, Port and Credentials (Make sure WL-OPC able to network access to the AdminServer IP:PORT)
  5. View registration details on "WLSDM Console > System Settings (wl-opc.system tab)" page

2. Generating WebLogic Performance Reports

  1. Go to "Stats and Reports" page
  2. Click "Total Alert Notifications" chart
  3. Click pie chart to see notification detail
  4. Go to "Generate Report" tab, select "Time Precision", "Domain", "Notification Type" and "Select Report Range" from "Get Report" panel then click "Generate Report"

3. Monitor and View WebLogic Notifications (WL-OPC all-in-one Notification Dashboard)

  1. Login to WL-OPC console. Go to "Notifications > Dashboard (All)" page
  2. Select notification type then view all kind of notifications in one dashboard