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

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

Advertisements

Servicebus 12c: Using configuration files for customizing service deployments

My colleague @sbernhardt wrote very nice article about Servicebus 12c: Using configuration files for customizing service deployments

The Cattle Crew Blog

Introduction

In my last projects I faced different challenges in the area of how to manage environment-specific artefact configurations that need to be adjusted during rollout of a particular service component. As a result from that, I decided to write down my experiences and solution approaches regarding the corresponding topics. This article is the starting point for a short blog series dealing with different challenges in this area, where the following topics will be covered:

  • General: Using configuration files for customizing service deployments
  • Adjust environment-specific configurations at deployment time
  • Evaluating environment-specific configurations at runtime
  • Security: Approaches for credentials management

Configuration files in Servicebus

During its lifecycle a specific service component needs to pass different quality gates to ensure quality, correctness and stability before it will be approved for production rollout. For that reason deployments to different environments have to be done. This usually means changes in configurations like service endpoints or timeout parameters, which must be possible without changing a components implementation and rebuilding the component. In Oracle Servicebus…

Ursprünglichen Post anzeigen 788 weitere Wörter