Aller au contenu principal

Installation of webMethods ESB

webmethods Installation
Blog types
Tutorial
Type
Technologies / Informatique

Le but de cet article est d'expliquer les étapes et actions à entreprendre pour installer une plateforme ESB (Enterprise System Bus) basée sur la suite webMethods ESB de Software AG en utilisant l'option lignes de commande. 

 

The purpose of this post is helping beginners and intermediates at how to install an ESB plateforme (Enterprise System Bus) based on Software AG's webMethods ESB suite and using command lines.

We will present the installation of the different webMethods components:

  • Physical prerequisites and database required for component installation
  • The principles of creating database schemas
  • The component installation procedure

--------------------------------------------------------------------------------------------------------------------

Presentation of the approach

Overall, the installation of a webMethods platform uses the following four main steps, the realization of each of them being necessary for the initialization of the following:

--------------------------------------------------------------------------------------------------------------------

Components webMethods

The following components will be installed and configured in the development environment:

  • Integration Server
  • JDBC Adapter
  • Command Central
  • Universal Messaging
  • Platform Manager
  • My webMethods Server
  • Database Configuration
  • Broker
  • Update Manager

--------------------------------------------------------------------------------------------------------------------

Prerequisites

Below is a reminder of the prerequisites:

  • Server or Virtual machine with installed OS Linux or AIX
  • A user system is created to install the solution
  • Software and licenses are available on the server
  • Data bases :
    • Data base installed.
    • DBA rights to create schemas and tables

--------------------------------------------------------------------------------------------------------------------

Creating database schemas

The webMethods components used require the creation of a number of database schemas. The traditionally recommended division, for example, implemented as part of the development platform, is as follows:

Database Component Type Oracle User
Integration server product webm
MywebMethodsServer product mws
Archive archive

This is can of course be adapted according to the customer constraints, depending on the type of environment to be installed and the expected volumetry.

The following sections describe the steps to take to create the schemas in the database.

Prerequisites

The creation of the database schemas is done via the DBConfigurator module. To install the DBConfigurator, follow these steps:

Start Software AG Installer :

Java –jar SoftwareAGInstallerXXXXXX.zip -readImage  /wM98_AIX.zip –console

In the list of products available for installation choose the DBConfigurator element.

Creating users with tablespaces

cd /webmethods/softwareag/common/db/bin

Creating user WEBM:

./dbConfigurator.sh -a create -d oracle -c storage -v latest -l « jdbc:wm:oracle://SRV_NAME:1521;serviceName=orcl; » -au SYSTEM -ap orcl -u webm -p webm -t /webmethods/base

Creating user MWS:

./dbConfigurator.sh -a create -d oracle -c storage -v latest -l "jdbc:wm:oracle://SRV_NAME:1521;serviceName=orcl;" -au SYSTEM -ap orcl -u mws -p mws -t /webmethods/base

Creating user ARCHIVE:

./dbConfigurator.sh -a create -d oracle -c storage -v latest -d oracle -l "jdbc:wm:oracle://SRV_NAME:1521;serviceName=orcl;sysLoginRole=sysdba" -au SYS -ap orcl -u archive -p archive -t /base/esb

Creating components in the database

WEBM the schema that will contain the Integration Server component tables

./dbConfigurator.sh -a create -d oracle -c all -v latest -l "jdbc:wm:oracle://SRV_NAME:1521;serviceName=orcl;" -u webm -p web

MWS is the schema that will contain tables for the components My webMethods Server

./dbConfigurator.sh -a create -d oracle -c mws -v latest -l "jdbc:wm:oracle://SRV_NAME:1521;serviceName=orcl;" -u mws -p mws

ARCHIVE schema for achiving

./dbConfigurator.sh -a create -d oracle -c archive -v latest -l "jdbc:wm:oracle://SRV_NAME:1521;serviceName=orcl;" -u archive -p archive

Give the table access rights to the user "ARCHIVE" using the following SQL script:

grant all on WEBM.WMCONTROL to ARCHIVE;
grant all on WEBM.WMCUSTOMFIELDDEFINITION to ARCHIVE;
grant all on WEBM.WMCUSTOMPROCESSDATA to ARCHIVE;
grant all on WEBM.WMDOCUMENT to ARCHIVE;
grant all on WEBM.WMERROR to ARCHIVE;
grant all on WEBM.WMPROCESS to ARCHIVE;
grant all on WEBM.WMPROCESSASSOC to ARCHIVE;
grant all on WEBM.WMPROCESSDEFINITION to ARCHIVE;
grant all on WEBM.WMPROCESSIMAGE to ARCHIVE;
grant all on WEBM.WMPROCESSRECENT to ARCHIVE;
grant all on WEBM.WMPROCESSSTEP to ARCHIVE;
grant all on WEBM.WMPROCESSTASK to ARCHIVE;
grant all on WEBM.WMPROCESSTASKSTEP to ARCHIVE;
grant all on WEBM.WMPROCESSTASKUSER to ARCHIVE;
grant all on WEBM.WMPROCESSTRANSITION to ARCHIVE;
grant all on WEBM.WMSECURITY to ARCHIVE;
grant all on WEBM.WMSERVICE to ARCHIVE;
grant all on WEBM.WMSERVICEACTIVITYLOG to ARCHIVE;
grant all on WEBM.WMSERVICEASSOC to ARCHIVE;
grant all on WEBM.WMSERVICE_MIN_MAX to ARCHIVE;
grant all on WEBM.WMSESSION to ARCHIVE;
grant all on WEBM.WMSTEPDEFINITION to ARCHIVE;
grant all on WEBM.WMSTEPTRANSITIONDEFINITION to ARCHIVE;
grant all on WEBM.WMTXIN to ARCHIVE;
grant all on WEBM.WMTXOUT to ARCHIVE;

--------------------------------------------------------------------------------------------------------------------

Principes of installation

The installation of a webMethods platform is done via console. As part of the installation of the platform the components to be installed will be as follows :

  • Integration Server
  • JDBC Adapter
  • Asset Build Environment
  • Universal Messaging
  • Broker
  • Command Central
  • My webMthods Server
  • Platform Manager
  • Database Configuration
  • Infrastructure
  • Composants transverse

--------------------------------------------------------------------------------------------------------------------

Execution of Installation

In a command line window, move to the directory where the Installer is located and start the command :

java -jar SoftwareAGInstallerXXXXXX.jar -readImage /sources/wM98_AIX.zip  -writeScript   /home/scriptwm -console

The options :

[-writeScript fileName] is to be used when creating an installation script.

[-console] option, when indicated, allows the console installation to proceed in a Shell window.

If this option is not set, the installation proceeds in graphical mode in a silent manner.

For the installation of the Update Manager of webMethods in a separate folder / softwareag_um only the choice of components is different. So follow the same steps in this chapter by checking only "Update Manager" in the list of components to install. The other components will be added automatically.

--------------------------------------------------------------------------------------------------------------------

Complete installation

Run post-installation script as « root »

On a UNIX system were prompted to use sudo, but you did not use it. The installer could not register on the "daemons" and set file permissions for the affected products. Perform this task now by running the SoftwareAG_directory/bin /afterInstallAsRoot.sh script as the root user.

JDBC driver Installation

The Oracle JDBC driver (used by the JDBC Adapter) must be installed on the Integration Server.

The .jar file is to be copied to the Integration Server lib directory.

webmethods jdbc driver

--------------------------------------------------------------------------------------------------------------------

Starting webMethods servers

Starting Universal Messaging

To run the server realm of Universal Massaging:

cd "/webmethods/softwareag/UniversalMessaging/links/Start Servers/Start Universal Messaging Realm Server 9.8"
nohup ./"Start umserver" &

Starting Integration  Server

To start the Integration Server from the console use the following command:

cd "/webmethods/softwareag/IntegrationServer/instances/default/bin/"
nohup ./startup.sh &

Monitor the contents of the following file in order to know the progress of the startup.

/webmethods/softwareag/IntegrationServer/instances/default/logs

The instance is started when the following message appears :

Initialization completed in XX seconds.

integration server console

The administration console can be accessed at the following address :

http://serveur:port/

The port to use is the one chosen during installation (5555 by default).

Starting My webMethods Server

To start My webMethods Server from the console :

cd "/webmethods/softwareag /MWS/server/default/bin"
/webmethods/softwareag/server/default/bin> ./startup.sh

The first start of My webMethods Server can, depending on the technical environment, require about 10 minutes to about an hour.

Consult the following file to know the progress of the start :

/webmethods/softwareag /MWS/server/default/logs/_full_.log

The server is started when the following message appears in the log :

My webMethods Server "default" Node "nom du node" took XX seconds to initialize.

When first started, My webMethods will be automatically restarted to finalize the installation. The message will appear twice.

my webmethods server console

The portal is then accessible via the following address, with the default administrator account namely "Administrator", password "manage":

http://server_mws:8585

Starting System Management Hub

To run SMH from console:

cd "/webmethods/softwareag /InstanceManager/bin/"
/webmethods/softwareag/InstanceManager/bin/> ./startup.sh
System management hub console

The portal is then accessible via the following address, with the default administrator account namely "Administrator", password "manage": 

http://server_smh:10010/PluggableUI
Comodo SSL