Materials 1370577882

8/13/2019 Materials 1370577882

1/50

webMethods, Inc.

3930 Pender Drive

Fairfax, VA 22030

USA

703.460.2500

http://www.webmethods.com

webMethods Administrat

Users Gu

VERSION

8/13/2019 Materials 1370577882

2/50

8/13/2019 Materials 1370577882

3/50

Con

webMethods Administrator Users Guide Version 6.1

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1. Overview of webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Role of webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

webMethods Administrator Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

webMethods Administrator and Integration Server Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Tools that Work Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Accessing Other webMethods HTML-based Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2. Getting Started with webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . What Are the webMethods Administrator Packages? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

WmAdmin and WmAdminResource Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting to the webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging On to webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging Off webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Portal to IS Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Returning to webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting Other webMethods HTML-based Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

webMethods Broker Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .webMethods Manager Server Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

webMethods Mainframe Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Predefined Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Removing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Predefined Groups and User-Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3. Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8/13/2019 Materials 1370577882

4/50

C o n t e n t s

4 webMethods Administrator Users Guide Version 6.1

Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Mapping Logical Servers to Physical Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Managing Logical Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

8/13/2019 Materials 1370577882

5/50

About This G


About This Guide

webMethods Administrator is an HTML-based graphical user interface (GUI) that ena

users to administer multiple server resources in a webMethods integration solution. Tguide is for the administrator of the webMethods Integration Platform.

Document Conventions

Addit ional Information

The webMethods Advantage Web site at http://advantage.webmethods.comprovides with important sources of information about the webMethods Integration Platform:

Troubleshooting Information.webMethods provides troubleshooting information formany webMethods components in the webMethods Knowledge Base.

Documentation Feedback.To provide documentation feedback to webMethods, go toDocumentation Feedback Formon the webMethods Bookshelf.

Additional Documentation.All webMethods documentation is available on thewebMethods Bookshelf.

Convention Description

Bold Identifies elements on a screen.

Italic Identifies variable information that you must supply orchange based on your specific situation or environment.Identifies terms the first time they are defined in text. Alsoidentifies service input and output variables.

Narrow font Identifies storage locations for services on the webMethodsIntegration Server using the convention folder.subfolder:service.

Typewriter

font

Identifies characters and values that you must type exactly ormessages that the system displays on the console.

UPPERCASE Identifies keyboard keys. Keys that you must presssimultaneously are joined with the + symbol.

\ Directory paths use the \ directory delimiter unless thesubject is UNIX-specific.

[ ] Optional keywords or values are enclosed in [ ]. Do not typethe [ ] symbols in your own code.
http://advantage.webmethods.com/http://advantage.webmethods.com/troubleshootinghttp://advantage.webmethods.com/troubleshootinghttp://advantage.webmethods.com/docfeedbackhttp://advantage.webmethods.com/Bookshelfhttp://advantage.webmethods.com/Bookshelfhttp://advantage.webmethods.com/Bookshelfhttp://advantage.webmethods.com/Bookshelfhttp://advantage.webmethods.com/Bookshelfhttp://advantage.webmethods.com/Bookshelfhttp://advantage.webmethods.com/docfeedbackhttp://advantage.webmethods.com/troubleshootinghttp://advantage.webmethods.com/

8/13/2019 Materials 1370577882

6/50

A b o u t T h i s G u i d e


8/13/2019 Materials 1370577882

7/50


C H A P T E R

1Overview of webMethods Administrator

Role of webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

webMethods Administrator and Integration Server Administrator . . . . . . . . . . . . . . . . . . .

Accessing Other webMethods HTML-based Components . . . . . . . . . . . . . . . . . . . . . . . . .

8/13/2019 Materials 1370577882

8/50

C H A P T E R 1 O v e r v i e w o f w e b M e t h o d s A d m i n i s t r a t o r


Role of webMethods Administrator

The webMethods Administrator tool is an HTML-based graphical user interface thatallows you to manage various resources on multiple servers from a central location. The

webMethods Administrator tool allows you to quickly and securely configure anywebMethods resource on an integration platform. Think of webMethods Administrator asa portal to the resources on your integration platform. The webMethods Administratorruns as a package on one of the Integration Servers in your integration platform. ThewebMethods Administrator resources include Broker Servers, Integration Servers,Workflow Servers, Mainframe Servers, and Manager Servers. In webMethodsAdministrator, your view consists of folders and resources. Each folder contains a list ofmanaged servers and their packages.

From an Integration Server (IS) Administrator, you can manage resources such asadapters, Brokers, Repository Servers and Proxy Servers.

The following illustration shows how webMethods Administrator is connected to

Integration Servers, a Broker Server, and a Mainframe Server.

webMethodsAdministrator

IntegrationServer B

MainframeServer

IntegrationServer A

IntegrationServer C

BrokerServer

IntegrationServer

ResourcesResources

Resources

ResourcesResources

8/13/2019 Materials 1370577882

9/50

Role of webMethods Administ


You can perform the following tasks using webMethods Administrator. Each task isdescribed in detail in the following sections of this guide.

To perform this task... See...

Add and remove folders and availableservers to and from each folder

Adding Resources on page 42

Organize resources by grouping servicesinto folders

Creating a Folder on page 40

Add and remove webMethodsAdministrator users and defineprivileges for users

Defining Users on page 30

Change user passwords and controlability of users to change their ownpasswords

Changing Passwords on page 36

Map logical servers to physical serversto create business processes for thewebMethods Modeler tool

Managing Logical Servers on page 48

8/13/2019 Materials 1370577882

10/50



webMethods Administrator Main Screen

The webMethods Administrator main screen displays top-level details about each serverand the resources defined for the user who is logged on. The main parts of this screen,which are part of every screen in webMethods Administrator, are shown in the

illustration below.

In the navigation area, there are five menu choices that allow you to do the following:

Home. Lists resources, descriptions of resources, and status of the resources in yourview.

Resources. Allows you to add and remove resources and register servers. You can alsoadd and remove folders and rename folders and resources. Resources include BrokerServers, Integration Servers, Workflow Servers, Mainframe Servers, and ManagerServers.

Logical Servers. Allows you to add logical servers and map them to physical servers.

Users.Lists the webMethods Administrator users in your view, and allows you tochange your own password. If you are the administrator, you can control the abilityof users to change their own passwords and you change the password for other users

Password. Allows you to change the password associated with a particular user name.

The Homescreen has four columns that are described below. For each Integration Serverresource, there is an expandable and collapsible tree view that lists installedadministration resources, such as Integration Servers, Workflow Servers, Broker Servers,Mainframe Servers, and Manager Servers.

Click to logoff session

Navigationarea

Screen

8/13/2019 Materials 1370577882

11/50

Role of webMethods Administ


Column Description

Resources Lists all registered servers and the packages installed on eachserver.

Description Gives the description of the folders contents.

Status Indicates whether or not the registered server is up and running.

indicates that a server is up and running and whetheror not the user is connected to that server.

indicates that the server is unavailable and a usercannot connect to it.

Version Indicates the version of the webMethods Integration Serversoftware.

8/13/2019 Materials 1370577882

12/50



webMethods Administrator and Integration Server

Administrator

The webMethods Administrator serves as a portal to administer multiple remote

Integration Servers, whereas the IS Administrator is the utility that manages one specificIntegration Server and its resources, such as adapters, Brokers, Repository Servers, andProxy Servers. The webMethods Administrator is installed on one Integration Server andis used to view other servers and their packages. With webMethods Administrator, youcan perform simple administrative tasks, as listed on page 12.

The IS Administrator allows you to perform more complicated administrator tasks on anindividual Integration Server, such as: monitoring server activity, examining loginformation, enabling/disabling services, and adjusting the servers performance features.

Tools that Work Together

While using webMethods Administrator, you may need to administer one IntegrationServer, and perform tasks that are not possible with webMethods Administrator, such aschange the privileges for a user account. You can quickly access the IS Administratorthrough webMethods Administrator. See the Portal to IS Administrator on page 24forinstructions on how to access IS Administrator from webMethods Administrator.

webMethods Administrator allows you to survey and organize your view of servers andresources and see the tasks you need to perform, if any. For example, in webMethodsAdministrator you can see that all the servers in the integration platform are up andrunning. However, if you need to stop and restart one server, you will perform that taskfrom the IS Administrator, then return to webMethods Administrator. See Portal to

IS Administrator on page 24for information about returning to webMethodsAdministrator.

8/13/2019 Materials 1370577882

13/50

Accessing Other webMethods HTML-based Compon


Accessing Other webMethods HTML-based Components

In addition to the Integration Server, there are three other webMethods components thave HTML-based administration graphical user interfaces that are accessed through

browser. Each component serves a unique administrative function.To access each component, see Chapter 2, Getting Started with webMethodsAdministrator.

Component Description

webMethods BrokerAdministrator

webMethods Broker Administrator is an HTML-baseutility that allows you to monitor webMethods BrokServers, territories, adapters, Brokers, and clients froany browser-equipped workstation in yourwebMethods Integration Platform.

webMethods ManagerServer Administrator

The Manager Server Administrator is an extension othe IS Administrator. It is a browser-based applicatiothat uses Web services to administer the webMethodManager Server. You can run the Manager ServerAdministrator from any browser-equippedworkstation in your integration platform.

Use Manager Server Administrator to:

Monitor Manager Server activity

Discover and enable the management ofintegration platform resources

webMethods MainframeAdministrator

webMethods Mainframe Administrator is an HTMLbased utility that allows you to see and manageMainframe activities.

You can use webMethods Mainframe Administratorto:

View statistics on webMethods Mainframeconfiguration and status

View the type and number of host connectionpools

View details of host transactions

Manage host connections, including stopping,starting, and tracing host sessions

Manage journals of transaction failures and evenyou want to audit

8/13/2019 Materials 1370577882

14/50



8/13/2019 Materials 1370577882

15/50


C H A P T E R

2Gett ing Started with webMethods Administrator

What Are the webMethods Administrator Packages? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting to the webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Portal to IS Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting Other webMethods HTML-based Components . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8/13/2019 Materials 1370577882

16/50

C H A P T E R 2 G e t t i n g S t a r t e d wi t h w e b M e t h o d s A d m i n i s t r a t o r


What Are the webMethods Administrator Packages?

The webMethods Administrator consists of two packages: WmAdmin andWmAdminResource. Using the webMethods installer, webMethods Administrator is

installed as an optional component in its own directory called webMethodsAdministration. If you select these packages, both are installed in thewebMethods6\IntegrationServer\packages\ directory. For installation instructions,see webMethods Integration Platform Installation Guide.

You can install both packages on any Integration Server in the network to make it functionin any of three ways:

The webMethods Administrator

A server that can be administered by the webMethods Administrator

As both

After the WmAdminandWmAdminResourcepackages are installed on a local andremote server, respectively, the following users and groups are created on the local andremote servers.

Central users

Central administrators

CentralAdministrators group

CentralUsers group

The server uses user and group information to authenticate clients and determine theserver resources that a client is allowed to access. Access to the servers resources is

controlled at the group level. With these users and groups, you can control what servicesand tasks each user performs. For information on group levels, see Predefined Groupsand User-Access Levels on page 33.

WmAdmin and WmAdminResource Packages

The WmAdmin package installs on the Integration Server and acts as the webMethodsAdministrator, and provides the administrative services and Dynamic Server Pages(DSPs). The WmAdminResource package, or client, provides services that thewebMethods Administrator invokes remotely to retrieve resource information fromremote servers. Any server with the WmAdmin package installed has webMethods

Administrator capability. There is no limit to the number of webMethods Administratorsthat you can install on an integration platform. Any server with the WmAdminResourcepackage installed can respond to resource queries from webMethods Administrator.

When installed, the WmAdmin and WmAdminResource packages establish all thenecessary users, groups, and Access Control Lists (ACLs) required for the IntegrationServer to provide administrative and client functionalities. In addition, each

8/13/2019 Materials 1370577882

17/50

What Are the webMethods Administrator Packa


IS Administrator screen contains the following link to the webMethods Administratomain screen to allow users quick access to the central functionality, as shown in theexample below.

http://localhost:5555/WmAdmin

The webMethods Administrator does not provide preconfigured resources to beadministered. However, it provides an easy way to allow the user to register anIntegration Server with the webMethods Administrator. Once registered, thewebMethods Administrator pulls resource information back from the remote server tviewed in the webMethods Administrator GUI.

Example

The WmAdmin package resides on the local Integration Server. This Integration Servethe server from which you will administer remote servers. The WmAdminResourcepackage resides on each remote Integration Server. The local Integration Server (using

webMethods Administrator) connects to the remote server and gathers information.For example, you have three Integration Servers with the following names:

Sales

Production

Manufacturing

The WmAdmin package is installed on the Production server and theWmAdminResource package is installed on both the Sales and Manufacturing. TheProduction server is local to you, so you want to administer the remote servers from th(See the illustration below.)

WmAdmin

Production

WmAdminResource

Sales

WmAdminResource

Manufacturing

8/13/2019 Materials 1370577882

18/50



Connecting to the webMethods Administrator

After you have installed both webMethods Administrator packages, you can log on to thetool and begin setting up the view to your network.

To use webMethods Administrator, simply open your browser and point it to the port onthe host machine where the webMethods Administrator is running.

Logging On to webMethods Administrator

To use the webMethods Administrator, simply open your browser and point it to the porton the host machine where the webMethods Administrator is running on the IntegrationServer.

1 Start your Integration Server.

For Windows: From the Start menu, choose ProgramswebMethodsServerswebMethods Integration Server.

For UNIX: Locate the server.sh script file that you modified for your environment

when you installed the server. Execute this script.

2 Start your browser.

3 Point your browser to the host and port where the webMethods Administrator isrunning.

Important! The Integration Server must be running in order to use this tool. If the server isnot running, your browser will issue an error similar to the following:

Cannot open the Internet site http://localhost:5555.

A connection with the server could not be established.

To log on to webMethods Administrator

Note: Run this script when logged on as a non-root user. Running the script as rootmight reduce the security of your system.

8/13/2019 Materials 1370577882

19/50

Connecting to the webMethods Administ


Examples

If webMethods Administrator is running on the default port on the same machinewhere you are running, type:

http://localhost:5555/WmAdmin

If webMethods Administrator is running on port 4040 on a machine called THOTtype:

http://THOTH:4040/WmAdmin

4 Log on to the webMethods Administrator with a user name and password that haadministrator privileges.

If you just installed webMethods Administrator, you can use the following defaulvalues:

User Name: Central

Password: manage

When you change the password, be sure to select one that is difficult to guess. Forexample, use a mixture of upper- and lower-case letters, numbers, and special charactDo not use a name, phone number, social security number, license plate, or othergenerally available information.

When you start webMethods Administrator, your browser displays the webMethodsAdministrator main screen, as shown on page 14.

Even if you are already logged on, you will be prompted to log on again if the sessiontime-out period has been reached.

Important! Use theexact combinationof upper- and lower-case characters shown abouser names and passwords are case sensitive. After installation, webMethods stronrecommends that you change the password immediately to avoid anyone tamperwith your system.

8/13/2019 Materials 1370577882

20/50



Logging Off webMethods Administrator

Log off of webMethods Administrator when you no longer need to continue your currentsession.

If you are going to be away from your machine, log off of the webMethods Administratorto prevent someone from accessing webMethods Administrator with your user namefrom your machine.

1 Click Log Offin the upper right corner of any webMethods Administrator screen.

You will be prompted for the password. Enter the password.

2 To resume use of the webMethods Administrator, click here, as shown above.

Porta l to IS Admin ist ra tor

You can access the IS Administrator from webMethods Administrator.

1 Log on to the webMethods Administrator if you are not already logged on.

2 In the webMethods Resource area of the screen, under the Resourcescolumn, locate

the name of the Integration Server you want to administer. Click the name next to the

icon.

Make sure the server is up and running by checking the status of a server in theStatuscolumn. When prompted, enter the user name and password for that remote server.The IS Administratoruser must have privileges to access the remote server. For more

To log off of webMethods Administrator

Accessing the IS Administrator

8/13/2019 Materials 1370577882

21/50

Portal to IS Administ


information on users and groups, see Predefined Users on page 31and PredefiGroups and User-Access Levels on page 33.

You are immediately launched to the IS Administrator main screen for that IntegratioServer. Using the IS Administrator, you can perform tasks such as starting and stoppithe server, administering server security, and managing packages and services. Refer webMethods Integration Server Administrators Guidefor more information.

Returning to webMethods Administrator

From the IS Administrator, you can return to webMethods Administrator in either of ways:

Click PackagesManagement and click the WmAdmin icon to return towebMethods Administrator main screen.

Use the Backbutton on your browser to return to webMethods Administrator mascreen.

Click to accessIS Administrator

8/13/2019 Materials 1370577882

22/50



Start ing Other webMethods HTML-based Components

Unlike the IS Administrator, which can be launched within webMethods Administrator,you must access the following three administrative tools directly from a browser only.

webMethods Broker Administrator

webMethods Manager Server Administrator

webMethods Mainframe Administrator


The webMethods Broker Administrator is used to configure and monitor the webMethodsBroker Server.


For Windows: From the Start menu, choose Programs, webMethods, Servers,webMethods Integration Server to start your Integration Server.

For UNIX: Locate the server.sh script file that you modified for your environmentwhen you installed the server. Execute this script.


Point your browser to the host and port where the webMethods Broker Administratoris running.

Examples

If webMethods Broker Administrator is running on the default port on the samemachine where you are running, type:

http://localhost:5555/WmBrokerAdmin

If the Integration Server is running on port 4040 on a machine called ATLAS, type:

http://ATLAS:4040/WmBrokerAdmin

3 Log on to the webMethods Broker Administrator with a user name and password thathas administrator privileges.

Starting the webMethods Broker Administrator

Note: Run this script when logged on as a non-root user. Running the script as rootmight reduce the security of your system.

8/13/2019 Materials 1370577882

23/50

Starting Other webMethods HTML-based Compon


If you just installed webMethods Broker Administrator, you can use the followingdefault values:

User Name: Administrator

Password: manage

Use the exact combination of upper- and lower-case characters shown above. Usenames and passwords are case sensitive.

Broker Administrator may take a few minutes to load.

When you start webMethods Broker Administrator, your browser displays thewebMethods Broker Administrator main screen. For more information, see webMethodBroker Administrators Guide.


The webMethods Manager Server Administrator is used to monitor webMethodsManager Server.


For Windows: From the Start menu, choose Programs, webMethods, Servers,webMethods Integration Server to start your Integration Server.

For UNIX: Locate the server.sh script file that you modified for your environm

when you installed the server. Execute this script.


Point your browser to the host and port where the Manager Server Administratorrunning.

Important! After installation, webMethods recommends that you change the passwimmediately to avoid anyone tampering with your system.

Important! The Server Administrator requires that JavaScript to be turned on in yourbrowser.

Important! The Integration Server must be running in order to use this tool. If the servenot running, your browser will issue an error similar to the following:

Cannot open the Internet site http://localhost:5555.

A connection with the server could not be established.

Starting the Manager Server Administrator

8/13/2019 Materials 1370577882

24/50



Examples

If Manager Server Administrator is running on the default port on the same machinewhere you are running, type:

http://localhost:5555/

If Manager Server Administrator is running on port 4040 on a machine calledQUICKSILVER, type:

http://QUICKSILVER:4040/

3 Log on to the Manager Server Administrator with a user name and password that hasadministrator privileges for the host Integration Server.

If you just installed Manager Server Administrator, you can use the following defaultvalues:

User Name: Administrator

Password: manage

Use the exact combination of upper- and lower-case characters shown above. Usernames and passwords are case sensitive.

The Server Statisticsscreen of the IS Administrator is the main screen for the ManagerServer. After you install the Manager Server, this page will become the default pagedisplayed when accessing the IS Administrator.For more information about the ManagerServer Administrator, see webMethods Manager Server Guide.

Important! After installation, webMethods recommends that you change the passwordimmediately to avoid anyone tampering with your system.

8/13/2019 Materials 1370577882

25/50

Starting Other webMethods HTML-based Compon



The webMethods Mainframe Administrator is used to monitor and control webMethoMainframe.


2 Point your browser to the host and port where the webMethods Integration Servestores configurations for one or more instances of webMethods Administrator. Usthe following syntax:

http://hostname:port_number/WmMainframe

For example, if the webMethods Integration Server is running on the default port omachine named myhost, type:

http://myhost:5555/WmMainframe

If the webMethods Integration Server is running, you are prompted for a user namand password.

3 Log on with a user name that has administrator privileges.

For information on maintaining administrator privileges, see webMethods IntegratiServer Administrators Guide.

In the Choose Connectionscreen, connect to an instance of webMethods Administrator,described in webMethods Mainframe Administrators Guide.

Starting webMethods Mainframe Administrator and connect to webMethods Administrator

8/13/2019 Materials 1370577882

26/50



Defining Users

Defining different users allows the server to identify who is currently accessing theresources on the server through the user name. For example, if there are several

applications accessing resources in the Integration Server, then the administrator candefine different users to represent these different applications.

Predefined users are used to invoke different services from different applications. Forexample, only users that are members of the Developers group can connect to the serverfrom the webMethods Developer to create, modify, and delete services.

When you add a user to webMethods Administrator, you specify a user name andpassword. The user is initially assigned to the Everybody group. When adding a user tothe webMethods Administrator, you are adding a user to the local Integration Server. SeePredefined Groups and User-Access Levels on page 33.

Click the Usersmenu in the navigation area to add a user, or view a list of predefinedusers.

I

8/13/2019 Materials 1370577882

27/50

Defining U


Predefined Users

The webMethods Administrator has four predefined users.

Creating a User Account

To create a user account from webMethods Administrator, you must have administraprivileges. If you are the administrator of the server, you need to access theIS Administrator to change the privileges. See webMethods Integration Server

Administrators Guidefor information about changing user privileges.

If you are not the administrator to the Integration Server to which you want access, yoneed to ask the administrator of the Integration Server to grant you the privileges.

1 Open the webMethods Administrator if it is not already open.

2 In the navigation area, click Users.

3 Click Add and Remove Users.

User Description

Administrator A user account that has administrator privileges. You can use theAdministrator user account to access the IS Administrator toconfigure and manage an Integration Server.

You can have more than one administrator per server. In this caseall administrators belong to the Administrator s group and havethe same privileges.

Central The default administrator user for webMethods Administratorwith full access to webMethods Administrator.

Developer A user that can connect to the server from the webMethodsDeveloper to create, modify, and delete services that reside on th

server.

Replicator The user account that the server uses during package replicationFor more information about package replication, see webMethodsIntegration Server Administrators Guide.

To create a user

8/13/2019 Materials 1370577882

28/50



4 In the Create Usersarea of the screen, specify the following information:

5 Click Create Users.

A new user is automatically added to the Everybody group without any access. Theadministrator must change the access level to either limited access or full access. Tochange access levels, see Changing user-access levels on page 36.

For this parameter Specify

User Names A unique user name made up of a combination of letters,

numbers, or symbols. You can specify one user name or oneuser name;passwordcombination per line. Press Enter toseparate the lines.

Important! User names are case sensitive. When you create auser account, type it exactly as you want the client to enter it.

Password A password made up of a combination of letters, numbers, orsymbols. You can specify the password in the User Namesfield by entering user name;passwordor you can enter thepassword in this field. If there is no password in the User

Names field, the server uses the password specified in thisfield. If you specify multiple users without passwords in theUser Namesfield, the server uses the password in the Passwordfield as the password for those users.

A password is required.

Important! Passwords are case sensitive. Type these valuesexactly as you want the client to enter it.

Be sure to select passwords that are difficult to guess. Forexample, use a mixture of upper- and lower-case letters,

numbers, and special characters. Do not use a name, phonenumber, social security number, license plate or othergenerally available information.

Re-Enter Password The same password again to make sure you typed itcorrectly.

8/13/2019 Materials 1370577882

29/50

Defining U


Removing Users

Use the following procedure to delete a user account when it is no longer needed from

server on which the account was created.



3 Click Add and Remove Users.

4 In the Remove Usersarea of the screen, select the user names for the user accounts

want to delete.

5 Click Remove Users. You are prompted to verify that you want to delete the useraccount. Click OKto remove the user account.

Predefined Groups and User-Access Levels

Access to the servers resources is controlled at the group level. A group membershipidentifies the groups to which a user belongs. The webMethods Administrator is instawith the following predefined groups.

The Everybodygroup is predefined by IS Administrator.

The CentralUsersand CentralAdministratorsgroups are predefined by webMethodsAdministrator.

A group is a named collection of users that share privileges. The following table showspredefined group name, member, access level, and a description for each group. Eachuser has a level of access associated with his or her user account, and a group to whichthat user belongs. The webMethods Administrator users belonging to the Everybody,CentralUsers,or CentralAdministratorgroups are automatically added to the IntegrationServer on which the webMethods Administrator, where the user accounts were createresides.

The administrator can add or remove a user to or from any of the groups identified in

following table. To perform this task, you must be in the IS Administrator withadministrator privileges. For more information about group membership, see webMethIntegration Server Administrators Guide.

Note: The server will not allow you to remove the following built-in user accounts:Administrator, Central, Developer, and Replicator.

To remove a user

8/13/2019 Materials 1370577882

30/50



Group Name Members Access

Level

Description

CentralAdministrators Centraladministrator

FullAccess

Users can configure and managean Integration Server using thewebMethods Administrator.

Important! Membership in thisgroup gives authority to changethe configuration of thewebMethods Administrator. Usecaution in assigning membershipin this group.

CentralUsers Central user LimitedAccess

If a user only has limited access,the user can do the following tasks:

Add folders/resources

Register servers

Change his or her ownpassword

With limited access, the usercannot perform the followingtasks:

Change or define access levelfor other users

Change other users' passwords

Add or remove users from thesystem

Cannot access other user shome pages

8/13/2019 Materials 1370577882

31/50

Defining U


Everybody AdministratorCentral

DeveloperReplicator

NoAccess

All users are a member of thisgroup. Every new user is

automatically added to theEverybody group. Tasks cannot bperformed by a user who does nhave an access level specified.

When a new user is created inwebMethods Administrator, thedefault access level is no access. order for this user to perform somtasks, the administrator (who hafull access) will need to change thuser's access level to either limite

access or full access. That is, if thadministrator wants the new useto be an administrator too.

Group Name Members Access

Level

Description

8/13/2019 Materials 1370577882

32/50



An Administrator can change the access level of a user in the Everybody group from noaccess to limited access.

1 Open the webMethods Administrator if it is not already logged on.


A list of currently defined users is displayed.

3 In the webMethods Administrator Users area of the screen, select either the No Access,Limited, or FullAccessbutton.

4 Click Save Changes.

Changing Passwords

After you have been assigned a user account on webMethods Administrator, you canchange the password for your user account. If you have limited access, you can onlychange your user account password. As an administrator with full access, you can controlwhether users are allowed to change their passwords through the webMethodsAdministrator.


2 In the navigation area, click Password.

3 In the ChangePasswordarea of the screen, select the user name for the user whosepassword you want to change, then click change password.

4 Enter the following information:

Changing user-access levels

Changing a users password

8/13/2019 Materials 1370577882

33/50

Defining U


5 Click Save Password.

For this parameter Specify

New Password The new password, made up of any combination of letters,numbers, or symbols.

Important! Passwords are case sensitive. Type this valueexactly as you want the client to enter it.

Be sure to select passwords that are difficult to guess. Forexample, use a mixture of upper- and lower-case letters,numbers, and special characters. Do not use a name, phonenumber, social security number, license plate or othergenerally available information.

Confirm Password The same password again to make sure you typed itcorrectly.

8/13/2019 Materials 1370577882

34/50



8/13/2019 Materials 1370577882

35/50


C H A P T E R

3Managing Resources

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mapping Logical Servers to Physical Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8/13/2019 Materials 1370577882

36/50

C H A P T E R 3 M a n a g i n g R e s o u r c e s


Overview

The webMethods Administrator is capable of administering multiple tasks on remoteservers. This chapter provides information about tasks that are commonly performed and

the users that can perform them from webMethods Administrator.

For information about CentralUsers and CentralAdministrator groups, see PredefinedGroups and User-Access Levels on page 33.

Creating a Folder

To group the managed servers in your network, webMethods Administrator allows youto organize your view of resources in folders; for example, Production, Staging, QualityAssurance, and Development. The webMethods Administrator main screen contains a listof folders in your view, which is an area where you can customize folders with resourcesto which you have administration access. Each folder contains a list of managed serversand their resources. You can add and remove folders and add and remove availableservers to and from each folder. You can group the servers into folders based on any givennaming scheme, and allocate a server to more than one folder. The individual folders are

displayed in your view upon logging on to webMethods Administrator.

In order to view and administer a remote server, you need to create a folder and add yourresources to it. All resources are listed in a tree view in the Add and Remove Foldersscreenaccessible from the Resourcesmenu.

User Can perform these tasks

Any user belonging toCentralUsers group orCentralAdministrators group

Creating a folder

Removing a folder

Registering a server

Adding a resource to a folder

Editing a registered server

Removing a server from a folder

Renaming resources

Administering a resource or server in a folder

Any user belonging to thepackage access group

Accessing packages

Note: You must perform some of the more complex tasks using the IS Administrator.

8/13/2019 Materials 1370577882

37/50

Creating a Fo


Any resources you add to your folders do not reside on webMethods Administrator, breside on the remote server to which those resources belong.


2 In the navigation area, click Resources.

3 In the blank field to the right of the folder icon, enter the name of the folder you wto create.

4 In the Descriptionfield, enter a description of the new folder.

5 Click Create Folder.

A new folder is created in the existing view and is displayed in the tree view.



3 On the Add and Remove Foldersscreen, locate the folder you want to remove from y

tree view. Click from the Removecolumn to remove the folder.

4 You are prompted whether you want to remove the selected folder or not. ClickO

The folder and its contents, server aliases, are removed from your view. Howeverserver aliases are not removed from your webMethods Administrator view.

Note: Make sure the Integration Server with webMethods Administrator installed on irunning before logging on to webMethods Administrator. To start the Integration Ser

see Logging On to webMethods Administrator on page 22.

Creating a folder

Folder DescriptionName of Folder

Removing a Folder

8/13/2019 Materials 1370577882

38/50



Adding Resources

After you have created a folder, you need to add resources to that folder and to otherfolders. These resources appear in your webMethods Administrator tree view, but are

actually on the remote server you are administering.



3 On the Add and Remove Foldersscreen, locate the folder to which you want to register aserver.

Your registered server will reside in this folder.

4 Click Add Resources.

The next screen lists all the registered servers, if any.

5 At the top of the screen, click Registered Servers.

6 In the Server Registrationscreen, enter the host, port, and valid account information forthe server.

Registering a Server

For this parameter... Specify...

Alias The name of the alias. There is no restriction on thecharacters you can specify, or limit to the length of thealias name.

The alias name is what appears in webMethodsAdministrator.

Hostname or IP Address The domain name or numeric IP address of the remoteserver.

Port The port number on the remote server to whichrequests will be sent when this alias is used.The default port number is 5555.

RMI Port Remote Methods Invocation port. This is the port that aJava program uses to invoke a remote service from anRMI Server.

Specify this port for Workflow Servers only.

8/13/2019 Materials 1370577882

39/50

Adding Resou


7 Once you have completed the Server Registrationscreen, click Register Server.

The IS Administrator updates and registers the server by creating a remote serveralias and querying the alias for its resource information.

User Name The user name that webMethods Administrator willuse when it submits requests using this alias. Specifyuser name that has access to the resources that

webMethods Administrator will need to use on theremote server.

Password The password for the user account specified in UserName.

Use SSL Whether you want your server to connect to the remoserver using Secure Sockets Layer (SSL). To ensure thdata is transmitted privately and that the content of tdata is not altered during transit, see webMethodsIntegration Server Administrators Guide.

Private Key The name of the file containing the key associated wi

your servers digital certificate; for example,d:\certs\privkey.der.

Certificates The names of files that make up the certificate chain fyour server. Specify the entire certificate chain usingthis format: Subject, Intermediate1, Intermediate2,..., Roo

Subjectis your servers certificate (the certificateyou want to present to the remote server).

Intermediate1and Intemediate2are certificates ofintermediate CAs (if the chain has intermediateCAs).

Rootis the certificate of the root-level CA.

Specify an absolute, fully qualified file name for eachelement of the chain, separated with commas; forexample,d:\certs\cert.der,d:\certs\intermedcert.der,

d:\certs\cacert.der


8/13/2019 Materials 1370577882

40/50




2 In the navigation area, click Resources.3 Choose the folder to which you want to add resources, then click Add Resources.

The Registered Serversscreen displays a list of aliases to the remote servers defined onthe IS Administrator.

4 Select the Addcheckboxes next to the remote alias servers you would like to add toyour folder.

5 Click the Add Serversbutton.

Each server is added to your folder.



3 In the Add and Remove Folderscreen, locate the registered server you want to modify,then under the Add Resources column, click Edit.

4 In the Server Registrationscreen, make your changes and click Save Changes.



3 From the Add and Remove Foldersscreen, locate the server from the appropriate folderin the tree view.

4 In the Remove column, click to remove the selected server. Click OKto thepromptthat asks if you are sure you want to remove the server.

The server reference is removed from the folder. However, it is not removed as aresource in the webMethods Administrator view.

Adding Resources to a Folder

Editing a Registered Server

Removing a Server from a Folder

Important! You can remove a remote server alias from webMethods Administrator orIS Administrator.

8/13/2019 Materials 1370577882

41/50

Adding Resou



2 Click Resources.A list of registered server aliases is displayed.

3 In the Removecolumn, click to remove the selected server alias.

The server alias is removed from the system and your view.


To access a package, you must belong to the package access group. To check whet

you belong to a packages access group, see webMethods Integration ServerAdministrators Guide.

2 In the webMethods Resourcesarea of the screen, locate the server from which you wto view and access packages. To expose the packages of the remote server, expandtree view for that remote server. Then click the name of the package you want toaccess.

You are launched to the package main screen. The Default package is the onlypackage that will launch you to IS Administrator.



3 Click Rename Resources.

The Foldersand Resourcesscreens display.

4 Type in the new names of the folders or resources. Click Save New Names.

Removing a Server from the System

Accessing Packages

Renaming Resources

8/13/2019 Materials 1370577882

42/50




2 In the navigation area, click Resources.3 Click the name of the server or resource to administer in the appropriate folder.

You are prompted for the user name and password for the administrator user on thatremote server or resource. You are redirected to the administrative URL for thatserver or resource.

4 Click OKto gain access to the remote server or resource in IS Administrator.

5 Complete your administrative tasks in the IS Administrator.

6 Click the Backbutton on the browser, or from IS Administrator, click

PackagesManagementand click the WmAdmin icon to return to webMethods

Administrator.

Clustering

Clusteringis an advanced feature of the webMethods Integration Platform thatsubstantially extends the reliability, availability, and scalability of the Integration Server.The clustering feature uses a repository to share cluster information and thereby linkmultiple Integration Servers into a virtual server cluster. For more information aboutclustering, see webMethods Integration Server Clustering Guide.

Because the webMethods Administrator is similar in capabilities to the IS Administrator,

the webMethods Administrator can be clustered like any other Integration Server. ThewebMethods Administrator makes no distinction between resources that are members ofa cluster versus standalone resources. You can organize members of a cluster any wayyou like. For example, you can add all members of a cluster into a folder that representsthat cluster, or you can separate them in different folders.

Administering a Server or Resource in a Folder

Important! Make sure that the WmAdmin package runs on all servers in a cluster so thatany one of them can take over the function of webMethods Administrator.

8/13/2019 Materials 1370577882

43/50

Mapping Logical Servers to Physical Ser


Mapping Logical Servers to Physical Servers

The purpose of mapping logical servers to physical servers is to allow you the flexibilto map different processes to servers, and to change that mapping easily.

The webMethods Modeler is a graphical modeling tool for specifying business proceswhich includes the ability to generate skeleton code to implement the modeled procesThe Modeler creates a business process step that is mapped to a logical server, which

becomes a unit of deployment when a process is deployed.

A logical serveris a simple token to identify a server for use in modeling from anarchitectural viewpoint. It lacks physical parameters such as a host or port. The logicaserver is comprised of high-level functionality with a logical name. Aphysical serverisactual Integration Server to which the logical server is mapped. Once a logical server mapped to a physical server, you can change the mapping without affecting the high-lusage.

As you draw the model in the webMethods Modeler, you identify where each step is tcompleted; that is, you assign steps to servers. However, when assigning the steps, younot specify a specific physical server (for example, acct45.company.com:5555). Rather, assign steps to a logical server (for example, Accounting). Each logical server is mappea physical server. By assigning the steps to logical servers, you assign steps based onfunctionality and can easily change the underlying physical servers.

Mapping logical servers to physical servers serves two purposes:

Creates a business process that can be used by the webMethods Modeler tool

Shares processes between environments where physical infrastructure differs

When a logical and physical server are mapped, that information is available to the

Modeler. This map is imported every time you create the new process through Modelor every time you start the Modeler. The location where the logical and physical mappresides is not on the Modeler tool, but on the Integration Server, which you access throwebMethods Administrator. The logical server is mapped to a physical server throughmapping that you manage through the webMethods Administrator.

8/13/2019 Materials 1370577882

44/50



After you finish mapping, the Modeler queries the mapping to determine which physicalservers should generate packages. For more information about the Modeler, refer towebMethods Modeler Users Guide.

Managing Logical Servers

Mapping logical servers to physical servers enables you to:

Maintain a list of logical servers

Leverage this information in other tools, such as Modeler

The webMethods Administrator allows you to manage (add, delete, and edit) new logicalservers and associate them with, that is, add or remove them from the physical servers

Assigns established logical servers to

process model steps

Logical and physical server mappingsreside

Mapping is managed

ISwebMethodsAdministrator

Modeler

IntegrationServers

8/13/2019 Materials 1370577882

45/50



To add a logical server, you do not need to fill in the Physical Serverfield. You can simpadd the logical server, and map a physical server to the logical server at a later time.


2 In the navigation area, click Logical Servers.

3 Click Add Logical Servers.

4 Specify the following information:

Adding a logical server


Name The server name you give the logical server. The name ismanaged by the system; you cannot change it after youhave assigned it.

Type The type of physical server: Integration Server orWorkflow. The type is used to constrain which types ofphysical servers can be mapped to which logical servers.

8/13/2019 Materials 1370577882

46/50



5 Click Add Logical Server.



3 Locate the logical server you need to map and click Editin theEditcolumn.4 In the Edit Logical Server screen, specify the physical server, then click Save Changes.

The physical server list is comprised of the IS Administrators registered servers.

Description(optional)

Describes the functionality of the logical server.

Physical Server The name of the selected physical server to map to thelogical server. The physical server list is comprised of theregistered servers in webMethods Administrator.

You do not have to choose a physical server to be mappedto the logical server at this time. If you prefer, you can addthe physical server mapping at a later time.

However, if you want to associate a logical server with aphysical server, make sure you have registered a physicalserver. To do so, see Adding Resources to a Folder onpage 44.


To map a logical server to a physical server

8/13/2019 Materials 1370577882

47/50




2 In the navigation area, click Logical Servers.3 Locate the server you want to modify and click Editin the Editcolumn.

4 In the Edit Logical Server screen, make your changes, then click Save Changes.

You can change the type of logical server, the description, or the associated physicserver. You cannot change the name of the logical server.

To view the list of logical servers mapped to a physical server, you need to have at leaone folder created.



3 From the Add and Remove Folderspage, locate the folder that contains the physicalserver you want to view, then click Editin the Add Resourcescolumn.

The attributes for that physical server are displayed as well as a table calledAssociLogical Serversthat shows the logical servers mapped to that physical server.



3 Locate the server you want to delete. Click in the Removecolumn to remove thelogical server.

4 A prompt asks if you are sure you want to remove the logical server. Click OK.

The server is deleted from your view.

Editing a logical server

Viewing the list of logical servers mapped to a selected physical server

Deleting a logical server

8/13/2019 Materials 1370577882

48/50



Securi ty

The security for webMethods Administrator closely models that of the IS Administrator.It is the responsibility of the underlying servers being administered to provide a basic

security model for communication between servers. For products that are hosted on theIntegration Server, this will not be a problem because the underlying Integration Serversecurity model will be used. For products not hosted on the Integration Server, it will bethe responsibility of that servers administrator to institute acceptable security for theunderlying servers.

For all products, appropriate ACLs need to be set on the services contained in the HTML-based Admin packages such as WmAdmin, WmBrokerAdmin, WmMainframeAdmin toprevent unauthorized users from accessing administrative functions of the underlyingserver products. For example, in the WmAdmin package, all services and DSP files haveassociated ACLs. As a result, users without privileges are denied access.

The webMethods Administrator tool provides the following security options:

Uses the existing Integration Server authentication model that uses the browser-basedlogon to the server. The browser caches all security credentials and resends theauthentication information on every HTTP request to the Integration Server. With thisapproach, all sessions established on the remote Integration Server will remain activeuntil timed out (as a result of the lack of activity), or until the webMethodsAdministrator user exits the browser session. At this point, the user is promptedagain for credential information to access that resource again. The security advantageis that webMethods Administrator stores no remote server credential information

locally.

Uses user account and group information retrieved from Lightweight DirectoryAccess Protocol (LDAP). LDAP is used for the user accounts and groups defined onthe Integration Server. This security option is provided through existing IntegrationServer LDAP capability.

For information about the IS Administrator security, see webMethods Integration ServerAdministrators Guideand the webMethods Integration Server Security Best Practices.

Note: Creating and managing ACLs is a task performed in IS Administrator. To create,update, and delete ACLs, see webMethods Integration Server Administrators Guide.

8/13/2019 Materials 1370577882

49/50

I


Index

Aaccessing packages 45

ACL settings 20, 52

adding a logical server 49

adding a user account 31

adding resources to folders 42

administering a local server 46

administering resources 46

Administrative tools

Integration Server Administrator 16, 24, 31, 33, 44, 46, 52

webMethods Broker Administrator 17, 26

webMethods Mainframe Administrator 17, 29webMethods Manager Server Administrator 17, 27

C

CentralAdministrators group 33, 34, 40

CentralUsers group 33, 34, 40

changing a password 23, 36

changing user-access levels 36

clustering 46

conventions used in this document 5

creating folders 40

D

deleting a logical server 51

documentation

additional 5

conventions used 5

feedback 5

E

editing a local server 44

editing a logical server 51Everybody group 30, 33, 35

Ffolders

adding resources 42, 44

allocating resources 40

creating 40

removing 41

removing a server from 44

full-access privileges 34

G

groups, predefined 33

I

IS Administrator

accessing from webMethods Administrator 24

returning to webMethods Administrator 25

working with webMethods Administrator 16

L

limited-access privileges 34

list of logical to physical server mappings 51

local serveradministering 46

editing 44

registering 42

removing from a folder 44

removing from the system 45

status 15

tasks 40

logical server

adding 49

defined 14, 47

deleting 51editing 51

mapping list 51

mapping to physical server 50

8/13/2019 Materials 1370577882

50/50

I n d e x

M

mapping a logical server to a physical server

example 47

purpose 47, 48

N

no-access privileges 35

O

overview of webMethods Administrator 12, 40

P

packages

accessing 45

WmAdmin 20WmAdminResource 20

physical server 47, 50

predefined groups 33

predefined users 30, 31

program code conventions in this document 5

R

registering local servers 42

remote server, clustering 46

removing a server from a folder 44

removing a server from the system 45removing a user account 33

removing folders 41

resources

administering 46

defined 12

renaming 45

S

Secure Sockets Layer (SSL) 43

security 52

T

troubleshooting information 5

typographical conventions in this document 5

Uuser accounts

adding 30

purpose 20

removing 33

user password, changing 23, 36

user-access levels

changing 36

full acess 34

limited access 34

no access 35

W

webMethods Administrator

connecting 22

example 21

logging off 24

logging on 22

overview 12, 40

security 52

WmAdmin package 20

WmAdminResource package 20


description 17

starting 26


description 17

starting 29


description 17

starting 27

Documents

Materials 1370577882