webMethods Administrator

Users Guide

VERSION 6.1

webMethods, Inc. 3930 Pender Drive Fairfax, VA 22030 USA 703.460.2500 http://www.webmethods.com

webMethods Administrator, webMethods Broker, webMethods Dashboard, webMethods Developer, webMethods Glue, webMethods Fabric, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Mobile, webMethods Modeler, webMethods Monitor, webMethods Optimize, webMethods Trading Networks, webMethods Workflow, and the webMethods logo are trademarks of webMethods, Inc. "webMethods" is a registered trademark of webMethods, Inc. Acrobat, Adobe, and Reader are registered trademarks of Adobe Systems Incorporated. Amdocs and ClarifyCRM are registered trademarks of Amdocs Ltd. Ariba is a registered trademark of Ariba Inc. BEA is a registered trademark, and BEA WebLogic Platform and BEA WebLogic Server are trademarks of BEA Systems, Inc. BMC Software and PATROL are registered trademarks of BMC Software, Inc. BroadVision is a registered trademark of BroadVision, Inc. Chem eStandards and CIDX are trademarks of Chemical Industry Data Exchange. Unicenter is a registered trademark of Computer Associates International, Inc. Kenan and Arbor are registered trademarks of CSG Systems, Incorporated. SNAP-IX is a registered trademark, and Data Connection is a trademark of Data Connection Ltd. DataDirect, DataDirect Connect, and SequeLink are registered trademarks of DataDirect Technologies. D&B and D-U-N-S are registered trademarks of D&B, Inc. Entrust is a registered trademark of Entrust. Hewlett-Packard, HP, HP-UX, and OpenView are trademarks of Hewlett-Packard Company. i2 is a registered trademark of i2 Technologies, Inc. AIX, AS/400, CICS, DB2, IBM, Infoprint, Informix, MQSeries, OS/390, OS/400, RACF, RS/6000, SQL/400, S/390, System/390, VTAM, and WebSphere are registered trademarks; and Communications System for Windows NT, IMS, MVS, SQL/DS, Universal Database, and z/OS are trademarks of IBM Corporation. JBoss and JBoss Group are trademarks of Marc Fleury under operation by JBoss Group, LLC. J.D. Edwards and OneWorld are registered trademarks, and WorldSoftware is a trademark of J.D. Edwards. Linux is a registered trademark of Linus Torvalds and others. X Window System is a trademark of Massachusetts Institute of Technology. MetaSolv is a registered trademark of Metasolv Software, Inc. ActiveX, Microsoft, Outlook, Visual Basic, Windows, and Windows NT are registered trademarks; and SQL Server is a trademark of Microsoft Corporation. Teradata is a registered trademark of NCR. Netscape is a registered trademark of Netscape Communications Corporation. New Atlanta and ServletExec are trademarks of New Atlanta Communications, LLC. CORBA is a registered trademark of Object Management Group, Inc. UNIX is a registered trademark of Open Group. Oracle is a registered trademark of Oracle Corporation. PeopleSoft and Vantive are registered trademarks, and PeopleSoft Pure Internet Architecture is a trademark of PeopleSoft, Inc. Infranet and Portal are trademarks of Portal Software, Inc. RosettaNet is a trademark of RosettaNet, a non-profit organization. SAP and R/3 are trademarks or registered trademarks of SAP AG. Siebel is a trademark of Siebel Systems, Inc. SPARC and SPARCStation are trademarks of SPARC International, Inc. SSA Global is a trademark and SSA Baan is a registered trademark of SSA Global Technologies, Inc. EJB, Enterprise JavaBeans, Java, Java Naming and Directory Interface, JavaServer Pages, JDBC, JSP, J2EE, Solaris, Sun Microsystems, and SunSoft are trademarks of Sun Microsystems, Inc. SWIFT and SWIFTNet are trademarks of S.W.I.F.T. SCRL. Sybase is a registered trademark of Sybase, Inc. UCCnet is a trademark of UCCnet. eBusinessReady is a trademark of Uniform Code Council, Inc. (UCC) and Drummond Group, Inc. (DGI). Verisign is a registered trademark of Verisign. VERITAS, VERITAS SOFTWARE, and VERITAS Cluster Server are trademarks of VERITAS Software. W3C is a registered trademark of World Wide Web Consortium. All other marks are the property of their respective owners.

Copyright 2004 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form. Document ID: ADMIN-UG-61-20040116

Contents

Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5 5

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11
12 14 16 16 17

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19
20 20 21 22 22 24 24 25 26 26 27 29 30 31 31 33 33 36

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

39

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Adding Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

webMethods Administrator Users Guide Version 6.1

Contents

Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Logical Servers to Physical Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Logical Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46 47 48 52

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

webMethods Administrator Users Guide Version 6.1

About This Guide

About This Guide

webMethods Administrator is an HTML-based graphical user interface (GUI) that enables users to administer multiple server resources in a webMethods integration solution. This guide is for the administrator of the webMethods Integration Platform.

Document Conventions
Convention Bold Italic Description Identifies elements on a screen. Identifies variable information that you must supply or change based on your specific situation or environment. Identifies terms the first time they are defined in text. Also identifies service input and output variables. Identifies storage locations for services on the webMethods Integration Server using the convention folder.subfolder:service. Identifies characters and values that you must type exactly or messages that the system displays on the console. Identifies keyboard keys. Keys that you must press simultaneously are joined with the + symbol. Directory paths use the \ directory delimiter unless the subject is UNIX-specific. Optional keywords or values are enclosed in [ ]. Do not type the [ ] symbols in your own code.

Narrow font
Typewriter font

UPPERCASE \ []

Additional Information
The webMethods Advantage Web site at http://advantage.webmethods.com provides you with important sources of information about the webMethods Integration Platform: Troubleshooting Information. webMethods provides troubleshooting information for many webMethods components in the webMethods Knowledge Base. Documentation Feedback. To provide documentation feedback to webMethods, go to the Documentation Feedback Form on the webMethods Bookshelf. Additional Documentation. All webMethods documentation is available on the webMethods Bookshelf.

webMethods Administrator Users Guide Version 6.1

About This Guide

webMethods Administrator Users Guide Version 6.1

CHAPTER

Overview of webMethods Administrator

Role of webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 webMethods Administrator and Integration Server Administrator . . . . . . . . . . . . . . . . . . . . . 16 Accessing Other webMethods HTML-based Components . . . . . . . . . . . . . . . . . . . . . . . . . . 17

webMethods Administrator Users Guide Version 6.1

11

CHAPTER 1 Overview of webMethods Administrator

Role of webMethods Administrator

The webMethods Administrator tool is an HTML-based graphical user interface that allows you to manage various resources on multiple servers from a central location. The webMethods Administrator tool allows you to quickly and securely configure any webMethods resource on an integration platform. Think of webMethods Administrator as a portal to the resources on your integration platform. The webMethods Administrator runs as a package on one of the Integration Servers in your integration platform. The webMethods Administrator resources include Broker Servers, Integration Servers, Workflow Servers, Mainframe Servers, and Manager Servers. In webMethods Administrator, your view consists of folders and resources. Each folder contains a list of managed servers and their packages. From an Integration Server (IS) Administrator, you can manage resources such as adapters, 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.

webMethods Administrator
Mainframe Server Integration Server Broker Server

Resources

Integration Server B

Resources

Integration Server A

Resources

Integration Server C

Resources

Resources

12

webMethods Administrator Users Guide Version 6.1

Role of webMethods Administrator

You can perform the following tasks using webMethods Administrator. Each task is described in detail in the following sections of this guide. To perform this task... Add and remove folders and available servers to and from each folder Organize resources by grouping services into folders Add and remove webMethods Administrator users and define privileges for users Change user passwords and control ability of users to change their own passwords Map logical servers to physical servers to create business processes for the webMethods Modeler tool See... Adding Resources on page 42 Creating a Folder on page 40 Defining Users on page 30

Changing Passwords on page 36

Managing Logical Servers on page 48

webMethods Administrator Users Guide Version 6.1

13

CHAPTER 1 Overview of webMethods Administrator

webMethods Administrator Main Screen

The webMethods Administrator main screen displays top-level details about each server and 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.

Navigation area

Click to log off session

Screen

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 your view. Resources. Allows you to add and remove resources and register servers. You can also add and remove folders and rename folders and resources. Resources include Broker Servers, Integration Servers, Workflow Servers, Mainframe Servers, and Manager Servers. 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 to change your own password. If you are the administrator, you can control the ability of 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 Home screen has four columns that are described below. For each Integration Server resource, there is an expandable and collapsible tree view that lists installed administration resources, such as Integration Servers, Workflow Servers, Broker Servers, Mainframe Servers, and Manager Servers.

14

webMethods Administrator Users Guide Version 6.1

Role of webMethods Administrator

Column Resources Description Status

Description Lists all registered servers and the packages installed on each server. Gives the description of the folders contents. Indicates whether or not the registered server is up and running. indicates that a server is up and running and whether or not the user is connected to that server. indicates that the server is unavailable and a user cannot connect to it.

Version

Indicates the version of the webMethods Integration Server software.

webMethods Administrator Users Guide Version 6.1

15

CHAPTER 1 Overview of webMethods Administrator

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 specific Integration Server and its resources, such as adapters, Brokers, Repository Servers, and Proxy Servers. The webMethods Administrator is installed on one Integration Server and is used to view other servers and their packages. With webMethods Administrator, you can perform simple administrative tasks, as listed on page 12. The IS Administrator allows you to perform more complicated administrator tasks on an individual Integration Server, such as: monitoring server activity, examining log information, enabling/disabling services, and adjusting the servers performance features.

Tools that Work Together

While using webMethods Administrator, you may need to administer one Integration Server, and perform tasks that are not possible with webMethods Administrator, such as change the privileges for a user account. You can quickly access the IS Administrator through webMethods Administrator. See the Portal to IS Administrator on page 24 for instructions on how to access IS Administrator from webMethods Administrator. webMethods Administrator allows you to survey and organize your view of servers and resources and see the tasks you need to perform, if any. For example, in webMethods Administrator you can see that all the servers in the integration platform are up and running. However, if you need to stop and restart one server, you will perform that task from the IS Administrator, then return to webMethods Administrator. See Portal to IS Administrator on page 24 for information about returning to webMethods Administrator.

16

webMethods Administrator Users Guide Version 6.1

Accessing Other webMethods HTML-based Components

Accessing Other webMethods HTML-based Components

In addition to the Integration Server, there are three other webMethods components that have HTML-based administration graphical user interfaces that are accessed through a browser. Each component serves a unique administrative function. To access each component, see Chapter 2, Getting Started with webMethods Administrator. Component webMethods Broker Administrator Description webMethods Broker Administrator is an HTML-based utility that allows you to monitor webMethods Broker Servers, territories, adapters, Brokers, and clients from any browser-equipped workstation in your webMethods Integration Platform. The Manager Server Administrator is an extension of the IS Administrator. It is a browser-based application that uses Web services to administer the webMethods Manager Server. You can run the Manager Server Administrator from any browser-equipped workstation in your integration platform. Use Manager Server Administrator to: Monitor Manager Server activity Discover and enable the management of integration platform resources webMethods Mainframe Administrator webMethods Mainframe Administrator is an HTMLbased utility that allows you to see and manage Mainframe activities. You can use webMethods Mainframe Administrator to: View statistics on webMethods Mainframe configuration and status View the type and number of host connection pools View details of host transactions Manage host connections, including stopping, starting, and tracing host sessions Manage journals of transaction failures and events you want to audit

webMethods Manager Server Administrator

webMethods Administrator Users Guide Version 6.1

17

CHAPTER 1 Overview of webMethods Administrator

18

webMethods Administrator Users Guide Version 6.1

CHAPTER

Getting Started with webMethods Administrator

What Are the webMethods Administrator Packages? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Connecting to the webMethods Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Portal to IS Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Starting Other webMethods HTML-based Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Defining Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

webMethods Administrator Users Guide Version 6.1

19

CHAPTER 2 Getting Started with webMethods Administrator

What Are the webMethods Administrator Packages?

The webMethods Administrator consists of two packages: WmAdmin and WmAdminResource. Using the webMethods installer, webMethods Administrator is installed as an optional component in its own directory called webMethods Administration. If you select these packages, both are installed in the webMethods6\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 function in any of three ways: The webMethods Administrator A server that can be administered by the webMethods Administrator As both After the WmAdmin and WmAdminResource packages are installed on a local and remote server, respectively, the following users and groups are created on the local and remote servers. Central users Central administrators CentralAdministrators group CentralUsers group The server uses user and group information to authenticate clients and determine the server 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 services and tasks each user performs. For information on group levels, see Predefined Groups and User-Access Levels on page 33.

WmAdmin and WmAdminResource Packages

The WmAdmin package installs on the Integration Server and acts as the webMethods Administrator, and provides the administrative services and Dynamic Server Pages (DSPs). The WmAdminResource package, or client, provides services that the webMethods Administrator invokes remotely to retrieve resource information from remote servers. Any server with the WmAdmin package installed has webMethods Administrator capability. There is no limit to the number of webMethods Administrators that you can install on an integration platform. Any server with the WmAdminResource package installed can respond to resource queries from webMethods Administrator. When installed, the WmAdmin and WmAdminResource packages establish all the necessary users, groups, and Access Control Lists (ACLs) required for the Integration Server to provide administrative and client functionalities. In addition, each

20

webMethods Administrator Users Guide Version 6.1

What Are the webMethods Administrator Packages?

IS Administrator screen contains the following link to the webMethods Administrator main screen to allow users quick access to the central functionality, as shown in the example below.
http://localhost:5555/WmAdmin

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

Example
The WmAdmin package resides on the local Integration Server. This Integration Server is the server from which you will administer remote servers. The WmAdminResource package 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 the WmAdminResource package is installed on both the Sales and Manufacturing. The Production server is local to you, so you want to administer the remote servers from there. (See the illustration below.) Production
WmAdmin

Manufacturing
WmAdmin Resource

Sales
WmAdmin Resource

webMethods Administrator Users Guide Version 6.1

21

CHAPTER 2 Getting Started with webMethods Administrator

Connecting to the webMethods Administrator

After you have installed both webMethods Administrator packages, you can log on to the tool and begin setting up the view to your network. To use webMethods Administrator, simply open your browser and point it to the port on the host machine where the webMethods Administrator is running. Important! The Integration Server must be running in order to use this tool. If the server is not 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.

Logging On to webMethods Administrator

To use the webMethods Administrator, simply open your browser and point it to the port on the host machine where the webMethods Administrator is running on the Integration Server. To log on to webMethods Administrator 1 Start your Integration Server. For Windows: From the Start menu, choose Programs webMethods Integration Server. webMethods Servers

For UNIX: Locate the server.sh script file that you modified for your environment when you installed the server. Execute this script. Note: Run this script when logged on as a non-root user. Running the script as root might reduce the security of your system. 2 3 Start your browser. Point your browser to the host and port where the webMethods Administrator is running.

22

webMethods Administrator Users Guide Version 6.1

Connecting to the webMethods Administrator

Examples If webMethods Administrator is running on the default port on the same machine where you are running, type:
http://localhost:5555/WmAdmin

If webMethods Administrator is running on port 4040 on a machine called THOTH, type:

http://THOTH:4040/WmAdmin

Log on to the webMethods Administrator with a user name and password that has administrator privileges. If you just installed webMethods Administrator, you can use the following default values: User Name: Password: Central manage

Important! Use the exact combination of upper- and lower-case characters shown above; user names and passwords are case sensitive. After installation, webMethods strongly recommends that you change the password immediately to avoid anyone tampering with your system. When you change the password, be sure to select one that is difficult to guess. For example, use a mixture of upper- and lower-case letters, numbers, and special characters. Do not use a name, phone number, social security number, license plate, or other generally available information. When you start webMethods Administrator, your browser displays the webMethods Administrator main screen, as shown on page 14. Even if you are already logged on, you will be prompted to log on again if the session time-out period has been reached.

webMethods Administrator Users Guide Version 6.1

23

CHAPTER 2 Getting Started with webMethods Administrator

Logging Off webMethods Administrator

Log off of webMethods Administrator when you no longer need to continue your current session. If you are going to be away from your machine, log off of the webMethods Administrator to prevent someone from accessing webMethods Administrator with your user name from your machine. To log off of webMethods Administrator 1 Click Log Off in the upper right corner of any webMethods Administrator screen. You will be prompted for the password. Enter the password.

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

Portal to IS Administrator
You can access the IS Administrator from webMethods Administrator. Accessing the IS Administrator 1 2 Log on to the webMethods Administrator if you are not already logged on. In the webMethods Resource area of the screen, under the Resources column, 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 the Status column. When prompted, enter the user name and password for that remote server. The IS Administrator user must have privileges to access the remote server. For more

24

webMethods Administrator Users Guide Version 6.1

Portal to IS Administrator

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

Click to access IS Administrator

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

Returning to webMethods Administrator

From the IS Administrator, you can return to webMethods Administrator in either of two ways: Click Packages Management and click the WmAdmin webMethods Administrator main screen. icon to return to

Use the Back button on your browser to return to webMethods Administrator main screen.

webMethods Administrator Users Guide Version 6.1

25

CHAPTER 2 Getting Started with webMethods Administrator

Starting 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

webMethods Broker Administrator

The webMethods Broker Administrator is used to configure and monitor the webMethods Broker Server. Starting the webMethods Broker Administrator 1 Start your Integration 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 environment when you installed the server. Execute this script. Note: Run this script when logged on as a non-root user. Running the script as root might reduce the security of your system. 2 Start your browser. Point your browser to the host and port where the webMethods Broker Administrator is running. Examples If webMethods Broker Administrator is running on the default port on the same machine 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

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

26

webMethods Administrator Users Guide Version 6.1

Starting Other webMethods HTML-based Components

If you just installed webMethods Broker Administrator, you can use the following default values: User Name: Password: Administrator manage

Use the exact combination of upper- and lower-case characters shown above. User names and passwords are case sensitive. Important! After installation, webMethods recommends that you change the password immediately to avoid anyone tampering with your system. Broker Administrator may take a few minutes to load. When you start webMethods Broker Administrator, your browser displays the webMethods Broker Administrator main screen. For more information, see webMethods Broker Administrators Guide.

webMethods Manager Server Administrator

The webMethods Manager Server Administrator is used to monitor webMethods Manager Server. Important! The Server Administrator requires that JavaScript to be turned on in your browser. Important! The Integration Server must be running in order to use this tool. If the server is not 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 1 Start your Integration 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 environment when you installed the server. Execute this script. 2 Start your browser. Point your browser to the host and port where the Manager Server Administrator is running.

webMethods Administrator Users Guide Version 6.1

27

CHAPTER 2 Getting Started with webMethods Administrator

Examples If Manager Server Administrator is running on the default port on the same machine where you are running, type:
http://localhost:5555/

If Manager Server Administrator is running on port 4040 on a machine called QUICKSILVER, type:
http://QUICKSILVER:4040/

Log on to the Manager Server Administrator with a user name and password that has administrator privileges for the host Integration Server. If you just installed Manager Server Administrator, you can use the following default values: User Name: Password: Administrator manage

Use the exact combination of upper- and lower-case characters shown above. User names and passwords are case sensitive. Important! After installation, webMethods recommends that you change the password immediately to avoid anyone tampering with your system. The Server Statistics screen of the IS Administrator is the main screen for the Manager Server. After you install the Manager Server, this page will become the default page displayed when accessing the IS Administrator. For more information about the Manager Server Administrator, see webMethods Manager Server Guide.

28

webMethods Administrator Users Guide Version 6.1

Starting Other webMethods HTML-based Components

webMethods Mainframe Administrator

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

Starting webMethods Mainframe Administrator and connect to webMethods Administrator 1 2 Start your browser. Point your browser to the host and port where the webMethods Integration Server stores configurations for one or more instances of webMethods Administrator. Use the following syntax:
http://hostname:port_number/WmMainframe

For example, if the webMethods Integration Server is running on the default port on a machine named myhost, type:
http://myhost:5555/WmMainframe

If the webMethods Integration Server is running, you are prompted for a user name and password. 3 Log on with a user name that has administrator privileges. For information on maintaining administrator privileges, see webMethods Integration Server Administrators Guide. In the Choose Connection screen, connect to an instance of webMethods Administrator, as described in webMethods Mainframe Administrators Guide.

webMethods Administrator Users Guide Version 6.1

29

CHAPTER 2 Getting Started with webMethods Administrator

Defining Users
Defining different users allows the server to identify who is currently accessing the resources on the server through the user name. For example, if there are several applications accessing resources in the Integration Server, then the administrator can define different users to represent these different applications. Predefined users are used to invoke different services from different applications. For example, only users that are members of the Developers group can connect to the server from the webMethods Developer to create, modify, and delete services. When you add a user to webMethods Administrator, you specify a user name and password. The user is initially assigned to the Everybody group. When adding a user to the webMethods Administrator, you are adding a user to the local Integration Server. See Predefined Groups and User-Access Levels on page 33. Click the Users menu in the navigation area to add a user, or view a list of predefined users.
I

30

webMethods Administrator Users Guide Version 6.1

Defining Users

Predefined Users
The webMethods Administrator has four predefined users. User Administrator Description A user account that has administrator privileges. You can use the Administrator user account to access the IS Administrator to configure and manage an Integration Server. You can have more than one administrator per server. In this case, all administrators belong to the Administrators group and have the same privileges. Central Developer The default administrator user for webMethods Administrator with full access to webMethods Administrator. A user that can connect to the server from the webMethods Developer to create, modify, and delete services that reside on the server. The user account that the server uses during package replication. For more information about package replication, see webMethods Integration Server Administrators Guide.

Replicator

Creating a User Account

To create a user account from webMethods Administrator, you must have administrative privileges. If you are the administrator of the server, you need to access the IS Administrator to change the privileges. See webMethods Integration Server Administrators Guide for information about changing user privileges. If you are not the administrator to the Integration Server to which you want access, you need to ask the administrator of the Integration Server to grant you the privileges. To create a user 1 2 3 Open the webMethods Administrator if it is not already open. In the navigation area, click Users. Click Add and Remove Users.

webMethods Administrator Users Guide Version 6.1

31

CHAPTER 2 Getting Started with webMethods Administrator

In the Create Users area of the screen, specify the following information: For this parameter User Names Specify A unique user name made up of a combination of letters, numbers, or symbols. You can specify one user name or one user name;password combination per line. Press Enter to separate the lines. Important! User names are case sensitive. When you create a user account, type it exactly as you want the client to enter it. Password A password made up of a combination of letters, numbers, or symbols. You can specify the password in the User Names field by entering user name;password or you can enter the password in this field. If there is no password in the User Names field, the server uses the password specified in this field. If you specify multiple users without passwords in the User Names field, the server uses the password in the Password field as the password for those users. A password is required. Important! Passwords are case sensitive. Type these values exactly as you want the client to enter it. Be sure to select passwords that are difficult to guess. For example, use a mixture of upper- and lower-case letters, numbers, and special characters. Do not use a name, phone number, social security number, license plate or other generally available information. Re-Enter Password The same password again to make sure you typed it correctly.

Click Create Users. A new user is automatically added to the Everybody group without any access. The administrator must change the access level to either limited access or full access. To change access levels, see Changing user-access levels on page 36.

32

webMethods Administrator Users Guide Version 6.1

Defining Users

Removing Users
Use the following procedure to delete a user account when it is no longer needed from the server on which the account was created. Note: The server will not allow you to remove the following built-in user accounts: Administrator, Central, Developer, and Replicator. To remove a user 1 2 3 4 5 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Users. Click Add and Remove Users. In the Remove Users area of the screen, select the user names for the user accounts you want to delete. Click Remove Users. You are prompted to verify that you want to delete the user account. Click OK to remove the user account.

Predefined Groups and User-Access Levels

Access to the servers resources is controlled at the group level. A group membership identifies the groups to which a user belongs. The webMethods Administrator is installed with the following predefined groups. The Everybody group is predefined by IS Administrator. The CentralUsers and CentralAdministrators groups are predefined by webMethods Administrator. A group is a named collection of users that share privileges. The following table shows the predefined group name, member, access level, and a description for each group. Each user has a level of access associated with his or her user account, and a group to which that user belongs. The webMethods Administrator users belonging to the Everybody, CentralUsers, or CentralAdministrator groups are automatically added to the Integration Server on which the webMethods Administrator, where the user accounts were created, resides. The administrator can add or remove a user to or from any of the groups identified in the following table. To perform this task, you must be in the IS Administrator with administrator privileges. For more information about group membership, see webMethods Integration Server Administrators Guide.

webMethods Administrator Users Guide Version 6.1

33

CHAPTER 2 Getting Started with webMethods Administrator

Group Name CentralAdministrators

Members Central administrator

Access Level Full Access

Description Users can configure and manage an Integration Server using the webMethods Administrator. Important! Membership in this group gives authority to change the configuration of the webMethods Administrator. Use caution in assigning membership in this group.

CentralUsers

Central user

Limited Access

If a user only has limited access, the user can do the following tasks: Add folders/resources Register servers Change his or her own password With limited access, the user cannot perform the following tasks: Change or define access level for other users Change other users' passwords Add or remove users from the system Cannot access other users home pages

34

webMethods Administrator Users Guide Version 6.1

Defining Users

Group Name Everybody

Members Administrator Central Developer Replicator

Access Level No Access

Description All users are a member of this group. Every new user is automatically added to the Everybody group. Tasks cannot be performed by a user who does not have an access level specified. When a new user is created in webMethods Administrator, the default access level is no access. In order for this user to perform some tasks, the administrator (who has full access) will need to change this user's access level to either limited access or full access. That is, if the administrator wants the new user to be an administrator too.

webMethods Administrator Users Guide Version 6.1

35

CHAPTER 2 Getting Started with webMethods Administrator

Changing user-access levels An Administrator can change the access level of a user in the Everybody group from no access to limited access. 1 2 Open the webMethods Administrator if it is not already logged on. In the navigation area, click Users. A list of currently defined users is displayed. 3 4 In the webMethods Administrator Users area of the screen, select either the No Access, Limited, or Full Access button. Click Save Changes.

Changing Passwords
After you have been assigned a user account on webMethods Administrator, you can change the password for your user account. If you have limited access, you can only change your user account password. As an administrator with full access, you can control whether users are allowed to change their passwords through the webMethods Administrator. Changing a users password 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Password. In the Change Password area of the screen, select the user name for the user whose password you want to change, then click change password. Enter the following information:

36

webMethods Administrator Users Guide Version 6.1

Defining Users

For this parameter New Password

Specify The new password, made up of any combination of letters, numbers, or symbols. Important! Passwords are case sensitive. Type this value exactly as you want the client to enter it. Be sure to select passwords that are difficult to guess. For example, use a mixture of upper- and lower-case letters, numbers, and special characters. Do not use a name, phone number, social security number, license plate or other generally available information.

Confirm Password

The same password again to make sure you typed it correctly.

Click Save Password.

webMethods Administrator Users Guide Version 6.1

37

CHAPTER 2 Getting Started with webMethods Administrator

38

webMethods Administrator Users Guide Version 6.1

CHAPTER

Managing Resources
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Adding Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Mapping Logical Servers to Physical Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

webMethods Administrator Users Guide Version 6.1

39

CHAPTER 3 Managing Resources

Overview
The webMethods Administrator is capable of administering multiple tasks on remote servers. This chapter provides information about tasks that are commonly performed and the users that can perform them from webMethods Administrator. User Any user belonging to CentralUsers group or CentralAdministrators group Can perform these tasks 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 the package access group Accessing packages

For information about CentralUsers and CentralAdministrator groups, see Predefined Groups and User-Access Levels on page 33. Note: You must perform some of the more complex tasks using the IS Administrator.

Creating a Folder
To group the managed servers in your network, webMethods Administrator allows you to organize your view of resources in folders; for example, Production, Staging, Quality Assurance, and Development. The webMethods Administrator main screen contains a list of folders in your view, which is an area where you can customize folders with resources to which you have administration access. Each folder contains a list of managed servers and their resources. You can add and remove folders and add and remove available servers to and from each folder. You can group the servers into folders based on any given naming 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 your resources to it. All resources are listed in a tree view in the Add and Remove Folders screen accessible from the Resources menu.

40

webMethods Administrator Users Guide Version 6.1

Creating a Folder

Any resources you add to your folders do not reside on webMethods Administrator, but reside on the remote server to which those resources belong. Note: Make sure the Integration Server with webMethods Administrator installed on it is running before logging on to webMethods Administrator. To start the Integration Server, see Logging On to webMethods Administrator on page 22. Creating a folder 1 2 3 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. In the blank field to the right of the folder icon, enter the name of the folder you want to create.

Name of Folder

Folder Description

4 5

In the Description field, enter a description of the new folder. Click Create Folder. A new folder is created in the existing view and is displayed in the tree view.

Removing a Folder 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. On the Add and Remove Folders screen, locate the folder you want to remove from your tree view. Click from the Remove column to remove the folder. You are prompted whether you want to remove the selected folder or not. Click OK. The folder and its contents, server aliases, are removed from your view. However, the server aliases are not removed from your webMethods Administrator view.

webMethods Administrator Users Guide Version 6.1

41

CHAPTER 3 Managing Resources

Adding Resources
After you have created a folder, you need to add resources to that folder and to other folders. These resources appear in your webMethods Administrator tree view, but are actually on the remote server you are administering. Registering a Server 1 2 3 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. On the Add and Remove Folders screen, locate the folder to which you want to register a server. Your registered server will reside in this folder. 4 Click Add Resources. The next screen lists all the registered servers, if any. 5 6 At the top of the screen, click Registered Servers. In the Server Registration screen, enter the host, port, and valid account information for the server. For this parameter... Alias Specify... The name of the alias. There is no restriction on the characters you can specify, or limit to the length of the alias name. The alias name is what appears in webMethods Administrator. Hostname or IP Address Port The domain name or numeric IP address of the remote server. The port number on the remote server to which requests will be sent when this alias is used. The default port number is 5555. Remote Methods Invocation port. This is the port that a Java program uses to invoke a remote service from an RMI Server. Specify this port for Workflow Servers only.

RMI Port

42

webMethods Administrator Users Guide Version 6.1

Adding Resources

For this parameter... User Name

Specify... The user name that webMethods Administrator will use when it submits requests using this alias. Specify a user name that has access to the resources that webMethods Administrator will need to use on the remote server. The password for the user account specified in User Name. Whether you want your server to connect to the remote server using Secure Sockets Layer (SSL). To ensure that data is transmitted privately and that the content of the data is not altered during transit, see webMethods Integration Server Administrators Guide. The name of the file containing the key associated with your servers digital certificate; for example, d:\certs\privkey.der. The names of files that make up the certificate chain for your server. Specify the entire certificate chain using this format: Subject, Intermediate1, Intermediate2,..., Root Subject is your servers certificate (the certificate you want to present to the remote server). Intermediate1 and Intemediate2 are certificates of intermediate CAs (if the chain has intermediate CAs). Root is the certificate of the root-level CA. Specify an absolute, fully qualified file name for each element of the chain, separated with commas; for example,
d:\certs\cert.der,d:\certs\intermedcert.der, d:\certs\cacert.der

Password Use SSL

Private Key

Certificates

Once you have completed the Server Registration screen, click Register Server. The IS Administrator updates and registers the server by creating a remote server alias and querying the alias for its resource information.

webMethods Administrator Users Guide Version 6.1

43

CHAPTER 3 Managing Resources

Adding Resources to a Folder 1 2 3 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. Choose the folder to which you want to add resources, then click Add Resources. The Registered Servers screen displays a list of aliases to the remote servers defined on the IS Administrator. 4 5 Select the Add checkboxes next to the remote alias servers you would like to add to your folder. Click the Add Servers button. Each server is added to your folder. Editing a Registered Server 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. In the Add and Remove Folder screen, locate the registered server you want to modify, then under the Add Resources column, click Edit. In the Server Registration screen, make your changes and click Save Changes.

Removing a Server from a Folder 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. From the Add and Remove Folders screen, locate the server from the appropriate folder in the tree view. In the Remove column, click to remove the selected server. Click OK to the prompt that 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 a resource in the webMethods Administrator view. Important! You can remove a remote server alias from webMethods Administrator or IS Administrator.

44

webMethods Administrator Users Guide Version 6.1

Adding Resources

Removing a Server from the System 1 2 Log on to the webMethods Administrator if you are not already logged on. Click Resources. A list of registered server aliases is displayed. 3 In the Remove column, click to remove the selected server alias.

The server alias is removed from the system and your view. Accessing Packages 1 Log on to the webMethods Administrator if you are not already logged on. To access a package, you must belong to the package access group. To check whether you belong to a packages access group, see webMethods Integration Server Administrators Guide. 2 In the webMethods Resources area of the screen, locate the server from which you want to view and access packages. To expose the packages of the remote server, expand the tree view for that remote server. Then click the name of the package you want to access. You are launched to the package main screen. The Default package is the only package that will launch you to IS Administrator.

Renaming Resources 1 2 3 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. Click Rename Resources. The Folders and Resources screens display.

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

webMethods Administrator Users Guide Version 6.1

45

CHAPTER 3 Managing Resources

Administering a Server or Resource in a Folder 1 2 3 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. 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 that remote server or resource. You are redirected to the administrative URL for that server or resource. 4 5 6 Click OK to gain access to the remote server or resource in IS Administrator. Complete your administrative tasks in the IS Administrator. Click the Back button on the browser, or from IS Administrator, click Packages Management and click the WmAdmin Administrator. icon to return to webMethods

Clustering
Clustering is an advanced feature of the webMethods Integration Platform that substantially extends the reliability, availability, and scalability of the Integration Server. The clustering feature uses a repository to share cluster information and thereby link multiple Integration Servers into a virtual server cluster. For more information about clustering, 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. The webMethods Administrator makes no distinction between resources that are members of a cluster versus standalone resources. You can organize members of a cluster any way you like. For example, you can add all members of a cluster into a folder that represents that cluster, or you can separate them in different folders. Important! Make sure that the WmAdmin package runs on all servers in a cluster so that any one of them can take over the function of webMethods Administrator.

46

webMethods Administrator Users Guide Version 6.1

Mapping Logical Servers to Physical Servers

Mapping Logical Servers to Physical Servers

The purpose of mapping logical servers to physical servers is to allow you the flexibility to map different processes to servers, and to change that mapping easily. The webMethods Modeler is a graphical modeling tool for specifying business processes, which includes the ability to generate skeleton code to implement the modeled process. The 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 server is a simple token to identify a server for use in modeling from an architectural viewpoint. It lacks physical parameters such as a host or port. The logical server is comprised of high-level functionality with a logical name. A physical server is an actual Integration Server to which the logical server is mapped. Once a logical server is mapped to a physical server, you can change the mapping without affecting the high-level usage. As you draw the model in the webMethods Modeler, you identify where each step is to be completed; that is, you assign steps to servers. However, when assigning the steps, you do not specify a specific physical server (for example, acct45.company.com:5555). Rather, you assign steps to a logical server (for example, Accounting). Each logical server is mapped to a physical server. By assigning the steps to logical servers, you assign steps based on functionality 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 Modeler, or every time you start the Modeler. The location where the logical and physical mapping resides is not on the Modeler tool, but on the Integration Server, which you access through webMethods Administrator. The logical server is mapped to a physical server through a mapping that you manage through the webMethods Administrator.

webMethods Administrator Users Guide Version 6.1

47

CHAPTER 3 Managing Resources

Modeler
Assigns established logical servers to process model steps

Integration Servers

Logical and physical server mappings reside

IS webMethods Administrator

Mapping is managed

After you finish mapping, the Modeler queries the mapping to determine which physical servers should generate packages. For more information about the Modeler, refer to webMethods 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 logical servers and associate them with, that is, add or remove them from the physical servers

48

webMethods Administrator Users Guide Version 6.1

Mapping Logical Servers to Physical Servers

To add a logical server, you do not need to fill in the Physical Server field. You can simply add the logical server, and map a physical server to the logical server at a later time. Adding a logical server 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Logical Servers. Click Add Logical Servers. Specify the following information: For this parameter... Name Specify... The server name you give the logical server. The name is managed by the system; you cannot change it after you have assigned it. The type of physical server: Integration Server or Workflow. The type is used to constrain which types of physical servers can be mapped to which logical servers.

Type

webMethods Administrator Users Guide Version 6.1

49

CHAPTER 3 Managing Resources

For this parameter... Description (optional) Physical Server

Specify... Describes the functionality of the logical server. The name of the selected physical server to map to the logical server. The physical server list is comprised of the registered servers in webMethods Administrator. You do not have to choose a physical server to be mapped to the logical server at this time. If you prefer, you can add the physical server mapping at a later time. However, if you want to associate a logical server with a physical server, make sure you have registered a physical server. To do so, see Adding Resources to a Folder on page 44.

Click Add Logical Server.

To map a logical server to a physical server 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Logical Servers. Locate the logical server you need to map and click Edit in the Edit column. 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.

50

webMethods Administrator Users Guide Version 6.1

Mapping Logical Servers to Physical Servers

Editing a logical server 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Logical Servers. Locate the server you want to modify and click Edit in the Edit column. 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 physical server. You cannot change the name of the logical server.

Viewing the list of logical servers mapped to a selected physical server To view the list of logical servers mapped to a physical server, you need to have at least one folder created. 1 2 3 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Resources. From the Add and Remove Folders page, locate the folder that contains the physical server you want to view, then click Edit in the Add Resources column. The attributes for that physical server are displayed as well as a table called Associated Logical Servers that shows the logical servers mapped to that physical server. Deleting a logical server 1 2 3 4 Log on to the webMethods Administrator if you are not already logged on. In the navigation area, click Logical Servers. Locate the server you want to delete. Click logical server. in the Remove column to remove the

A prompt asks if you are sure you want to remove the logical server. Click OK. The server is deleted from your view.

webMethods Administrator Users Guide Version 6.1

51

CHAPTER 3 Managing Resources

Security
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 the Integration Server, this will not be a problem because the underlying Integration Server security model will be used. For products not hosted on the Integration Server, it will be the responsibility of that servers administrator to institute acceptable security for the underlying servers. For all products, appropriate ACLs need to be set on the services contained in the HTMLbased Admin packages such as WmAdmin, WmBrokerAdmin, WmMainframeAdmin to prevent unauthorized users from accessing administrative functions of the underlying server products. For example, in the WmAdmin package, all services and DSP files have associated ACLs. As a result, users without privileges are denied access. Note: Creating and managing ACLs is a task performed in IS Administrator. To create, update, and delete ACLs, see webMethods Integration Server Administrators Guide. The webMethods Administrator tool provides the following security options: Uses the existing Integration Server authentication model that uses the browser-based logon to the server. The browser caches all security credentials and resends the authentication information on every HTTP request to the Integration Server. With this approach, all sessions established on the remote Integration Server will remain active until timed out (as a result of the lack of activity), or until the webMethods Administrator user exits the browser session. At this point, the user is prompted again for credential information to access that resource again. The security advantage is that webMethods Administrator stores no remote server credential information locally. Uses user account and group information retrieved from Lightweight Directory Access Protocol (LDAP). LDAP is used for the user accounts and groups defined on the Integration Server. This security option is provided through existing Integration Server LDAP capability. For information about the IS Administrator security, see webMethods Integration Server Administrators Guide and the webMethods Integration Server Security Best Practices.

52

webMethods Administrator Users Guide Version 6.1

Index

Index
A
accessing 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, 29 webMethods Manager Server Administrator 17, 27

F
folders 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

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

L
limited-access privileges 34 list of logical to physical server mappings 51 local server administering 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 51 editing 51 mapping list 51 mapping to physical server 50

D
deleting a logical server 51 documentation additional 5 conventions used 5 feedback 5

E
editing a local server 44 editing a logical server 51 Everybody group 30, 33, 35

webMethods Administrator Users Guide Version 6.1

53

Index

M
mapping a logical server to a physical server example 47 purpose 47, 48

T
troubleshooting information 5 typographical conventions in this document 5

N
no-access privileges 35

U
user 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

O
overview of webMethods Administrator 12, 40

P
packages accessing 45 WmAdmin 20 WmAdminResource 20 physical server 47, 50 predefined groups 33 predefined users 30, 31 program code conventions in this document 5

W
webMethods Administrator connecting 22 example 21 logging off 24 logging on 22 overview 12, 40 security 52 WmAdmin package 20 WmAdminResource package 20 webMethods Broker Administrator description 17 starting 26 webMethods Mainframe Administrator description 17 starting 29 webMethods Manager Server Administrator description 17 starting 27

R
registering local servers 42 remote server, clustering 46 removing a server from a folder 44 removing a server from the system 45 removing a user account 33 removing folders 41 resources administering 46 defined 12 renaming 45

S
Secure Sockets Layer (SSL) 43 security 52

54

webMethods Administrator Users Guide Version 6.1