How to configure the WebLogic AdminServer for High Availability

Introduction

The high availability of applications in the WebLogic environment is realized by clustering. Managed servers in the cluster work together. The information about transactions is distributed cluster-wide. If a cluster member fails, another server takes over the tasks of the failed server and executes them. In this way, the applications are kept running without interruption.

The AdminServer is a single point of failure: if the server fails, the Domain is no longer administrable:

– Configuration changes cannot be performed

– The administration console is not available

The managed servers are still running and can continue to work, even if the AdminServer is not available: this requires the activation of MSI (Managed Server Independence) Mode.

How can the AdminSevrer be protected from failure? In this blogpost I will describe all the steps that are necessary to keep your server running safely.

Save the Date: DOAG 2017 IMC (Infrastruktur-Middleware) Days

Am 07.09.2017 trifft sich die Middleware Community in Berlin, um spannenden Vorträgen zu lauschen und sich über aktuelle IT-Themen auszutauschen. Bekannte Referenten teilen ihre Erfahrungen in Themen rund um Oracle Middleware Administration mit und geben einen Überblick über die aktuellen Cloud Trends

Info und Agenda hier

Wir sehen uns in Berlin!

 

How to hide passwords and account information in WLST scripts (WebLogic Server)

If you are worried about your password showing up in clear text in the startup scripts, you can use the storeUserConfig command to generate encrypted userconfigFile and a userKeyFile that you can then use in the „nmConnect“ and „connect“ command.

Place there two files on the protected place and decide to set right permissions

Create storeUserConfig for the Node Manager

Start wlst via the shell script $ORACLE_HOME/oracle_common/common/bin/wlst.sh:

/u01/app/oracle/product/FMW/Oracle_Home/oracle_common/common/bin/wlst.sh

Advanced OHS Configuration in Oracle Forms 12.2.1.2

In this blog entry I will describe two topics:

• Configuration OHS to listen on the Port 80
• Configuration access to the AdminConsole / EM via HTTP Port

Configuration OHS to listen on the Port 80

After the initial installation of Forms is the OHS configured for the listening on the Port 7777. If you would change the listening to the Port 80 execute following steps

Change Permissions for the File launch (as root!!!):

chown root ${MIDDLEWAR_HOME}/Oracle_Home/ohs/bin/launch
chmod 4750 ${MIDDLEWAR_HOME}/Oracle_Home/ohs/bin/launch

Edit the file httpd.conf

Oracle Forms & Reports 12.2.1.2.0: Create and Configure on the OEL 7.2 Server

Introduction

This post focuses on the creation, configuration and tuning of an initial Forms & Reports 12.2.1.2.0 Domain on the OEL 7.2 Server.

The WebLogic Server is a necessary requirement, and must already be installed. For instruction how to install the WebLogic Server 12.2.1.2 please refer to my previous post: WebLogic Server 12.2.1.2.0: Installation on the Linux OEL 7: step by step instruction

The following tasks will be implemented:

• Preparing the Operating System for the installation of the WebLogic Server 12.2.1.2, Installation JDK 1.8 and the WebLogic Server 12.2.1.2:
• Creating of database schemas
• Installing and Configuring a Forms & Reports Domain
• Post-Installation Tasks:
  • Configuring of components
  • Creating of Start & Stop scripts for the automatic start/stop of components
• Tuning and Troubleshooting

The Domain will be created on the one OEL 7.2 server: host03.example.com (IP 192.168.75.35)

Installation Forms & Reports 12.2.1.2

WebLogic Server 12.2.1.2.0: Installation on the Linux OEL 7: step by step instruction

Kategorie    Step by Step

Introduction

This post describes the installation of the WebLogic Server Version 12.2.1.2.0

The following tasks are performed and described:

• Preparing the Operating System for the installation of the WebLogic Server 12.2.1.2
• Installation JDK 1.8 and the WebLogic Server 12.2.1.2

The installation will be proceeding on the Oracle Enterprise Linux 7.2: host03.example.com

Pre-installation Tasks

SOA Suite 12.2.1.1.0: Create, configure and tune a SOA/OSB Domain

Introduction

This post focuses on the creation, configuration and tuning of an initial SOA Suite 12.2.1.1.0 Domain.

The WebLogic Server is a necessary requirement, and must already be installed. For instruction how to install the WebLogic Server 12.2.1.1 please refer to my previous post:  WebLogic Server 12.2.1.1.0: Installation on the Linux OS

The following tasks will be implemented:

• Preparing the Operating System for the installation of the WebLogic Server 12.2.1.1, Installation JDK 1.8 and the WebLogic Server 12.2.1.1: WebLogic Server 12.2.1.1.0: Installation on the Linux OS
• Creating of database schemas
• Creating a SOA Suite Domain
• Post-Installation Tasks:
  • Configuring of components
  • Creating of Start & Stop scripts for the automatic start/stop of components
• SOA Suite Domain Tuning and Troubleshooting

The SOA/OSB Domain will be installed without BAM (different Domain) because of:

–    Oracle Best Practices and our experience

–    In order to stabilize the system (BAM is unstable at the moment)

The Domain will be created on two servers (OS OEL 6.7):

• host01.example.com
• host02.example.com

We will configure four clusters:

• OWSM Cluster (Oracle Web Services Management)
• ESS Cluster (Enterprise Scheduler Services)
• SOA Cluster
• OSB Cluster (Oracle Service Bus)

Installation SOA / OSB 12.2.1.1

Note: All tasks described in this chapter must be running on both servers: host01 and host02

WebLogic Server 12.2.1.1.0: Create, configure and tune a Domain

Introduction

This post focuses on the creation, configuration and tuning of an initial WebLogic Server 12.2.1.1.0 Domain.

The WebLogic Server is a necessary requirement, and must already be installed. For instruction how to install the WebLogic Server 12.2.1.1 please refer to my previous post: WebLogic Server 12.2.1.1.0: Installation on the Linux OS

The following tasks will be implemented:

• Preparing the Operating System for the installation of the WebLogic Server 12.2.1.1, Installation JDK 1.8 and the WebLogic Server 12.2.1.1: please refer to WebLogic Server 12.2.1.1.0: Installation on the Linux OS
• Creating of database schemas
• Creating an initial WebLogic Domain
• Post-Installation Tasks:
  • Configuring of components
  • Creating of Start & Stop scripts for the automatic start/stop of components
• WebLogic Domain Tuning and Troubleshooting

The Domain will be reated on two servers (OS OEL 6.7):

• host01.example.com
• host02.example.com

We will configure two managed Server for Web Services in cluster:

WebLogic Server 12.2.1.1.0: Installation on the Linux OS: step by step instruction

Introduction

This post describes the installation of the WebLogic Server Version 12.2.1.1.0

The following tasks are performed and described:

• Preparing the Operating System for the installation of the WebLogic Server 12.2.1.1
• Installation JDK 1.8 and the WebLogic Server 12.2.1.1

The installation will be proceeding on two servers (OS OEL 6.7):

• host01.example.com
• host02.example.com

Pre-installation Tasks

This chapter describes some tasks of preparation for the Operating System and the Database.

For more information please refer to the document System requirements

How to customize Java Virtual Machine Settings in Oracle WebLogic Server 12 on OS Linux / UNIX

In order to achieve the best performance of the application or to avoid performance bottlenecks (and “OutOfMemory” problems) you need to tune your Java Virtual Machine. After you install the WebLogic Server and create a Domain (WebLogic or SOA or Forms or OBIEE etc.) you may set some properties such as Java “Heap size”, tune Java “Garbage Collection” and WebLogic Server start options.

Tune JVM settings

You can set the Variable USER_MEM_ARGS for the Admin Server and each Managed Server to tune the JVM Parameters. For Example:

USER_MEM_ARGS="-Xms1g -Xmx3g -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:NewSize=1g"