WebLogic Application Server

Application Version and Upgrade Details

Introduction

WebLogic Server allows you to quickly develop and deploy reliable, secure, scalable and manageable applications. It manages system-level details so you can concentrate on business logic and presentation.

WebLogic domain is a fundamental administrative unit for WebLogic Server. It comprises one or more WebLogic Server instances with their resources, which are collectively managed and configured using a single Administration Server.

The WebLogic domain infrastructure consists of three parts:

• Administration Server: Guides the actions of managed servers.
• Managed Servers: Stand-alone servers ruled by the Administration Server.
• Clusters: Clusters are groups of managed servers managed by the Administration Server.

WebLogic Server Domains are referred to as Managed Servers, in which Java Enterprise Solutions are deployed. These Managed Servers are grouped into clusters for load balancing and failover, especially for critical applications. Multiple WebLogic domains are also set up according to application boundaries, system administrator responsibilities and server’s geographical location. Alternatively you can set up a single domain to manage all WebLogic Server administration activities.

The most common WebLogic Server user types are:

• Evaluator: Users who performs product evaluations
• Installer: Users who installs and sets up the WebLogic Server environment
• System Administrator: Users who administers WebLogic Server after it is installed
• Developer/Engineer: Users who develop applications to run in the WebLogic Server environment.

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.
• OpsRamp NextGen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.
• To access WebLogic Enterprise Server API’s the user should Enable RESTful Management Services in WebLogic Admin Console Configurations.

Key Use cases

Discovery Use cases

• It discovers the Oracle WebLogic application server components like WebLogic domain, clusters, servers and its related applications and data sources. the following are the resource structure.

→ WebLogic Enterprise Server
     → WebLogic Clusters
     → WebLogic Servers
     → WebLogic Server Applications
     → WebLogic Server Datasources

• Publishes relationships between resources to have a topological view and ease of maintenance.

Monitoring Use cases

• Provides metrics related to job scheduling time and status etc,.
• Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource.

Default Monitoring Configurations

WebLogic application has a default Global Device Management Policies, Global Templates, Global Monitors, and Global Metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates, and Global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of WebLogic Server. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: weblogic-server WebLogic Servers- 1 (i.e, appName = weblogic-server, nativeType = WebLogic Servers, version = 1)

2. Default Global Templates

   OpsRamp has a Global Template for each Native Type of WebLogic Server. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: weblogic-server WebLogic Servers Template - 1 (i.e, appName = weblogic-server, nativeType = WebLogic Servers, version = 1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: WebLogic Servers Monitor weblogic-server WebLogic Servers 1 (i.e, monitorKey = WebLogic Servers Monitor, appName = weblogic-server, nativeType = WebLogic Servers, version = 1)

Configure and Install the WebLogic Application Server Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed. Note: If there are no installed applications, it will navigate to the Available Integrations and Apps page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
   
6. Search for WebLogic Application Server using the search option available.
   Note: Alternatively, you can use the All Categories option to search.
7. Click ADD on the WebLogic Application Server tile and select the version.

8. In the Configurations page, click + ADD. The Add Configuration window appears.
9. Enter the below mentioned BASIC INFORMATION:

Notes:

• By default the isSecure checkbox is selected.
• WebLogic IP Address / Host Name and Port should be accessible from Gateway.
• Select App Failure Notifications; if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

10. Select the below mentioned CUSTOM ATTRIBUTES:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

11. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
12. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
      
13. Click ADD.

The configuration is saved and displayed on the configurations page.
Note: From the same page, you may Edit and Remove the created configuration.

14. Below are the optional steps you can perform on the page.

• Under the ADVANCED SETTINGS, select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

  Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

15. Click NEXT.

16. You can either add a new collector profile or select an existing one.

    • Click +ADD to create a new collector by providing a name or use the pre-populated name.

    

    • Select an existing registered profile.

    

17. Click FINISH.

The integration is now installed and displayed on the Installed Integration page. Use the search field to find the installed application.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the WebLogic Application Server application.

View the WebLogic Server details

The WebLogic Server integration is displayed in the Infrastructure > Resources > Server, select the relationship. You can navigate to the Attributes tab to view the discovery details, and the Metrics tab to view the metric details for WebLogic Server.

Resource Type Filter Keys

WebLogic Enterprise Server application Resources are filtered and discovered based on below keys:

Supported Alert Custom Macros

Supported Metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
• Application cannot control monitoring pause/resume actions based on above alerts.
• No support of showing activity log and applied time.
• This application supports both Classic Gateway and NextGen Gateway.