0% found this document useful (0 votes)

8 views78 pages

7-1-1 Metadata Library Users Guide

The document is the User's Guide for the webMethods Metadata Library, version 7.1.1, detailing its features, installation, configuration, and usage. It includes sections on document conventions, introduction, default configuration, and configuration processes. The guide also lists trademarks and copyright information related to webMethods and other associated products.

Uploaded by

raghup0715

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

8 views78 pages

7-1-1 Metadata Library Users Guide

Uploaded by

raghup0715

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 78

Title Page

Metadata Library Version 7.1.1 webMethods Metadata Library User’s

Guide
Copyright
& Docu‐
ment ID

Cerebra, Glue, Infravio X‐Broker, Infravio X‐Registry, Infravio, My webMethods Server, My webMethods, webMethods Access, webMethods Administrator,
webMethods Broker, webMethods Central Configuration, webMethods Dashboard, webMethods Designer, webMethods Developer, webMethods Fabric,
webMethods Glue, webMethods Infrastructure Data Collector, webMethods Infravio X‐Broker, webMethods Infravio X‐Registry, webMethods Installer,
webMethods Integration Server, webMethods logo, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor,
webMethods Optimize for Infrastructure, webMethods Optimize for Process, webMethods Optimize, webMethods Portal, webMethods Process Engine,
webMethods Servicenet, webMethods Task Engine, webMethods Trading Networks, webMethods Workflow, and webMethods are either registered
trademarks or trademarks of webMethods, Inc.
Acrobat, Acrobat, and Reader are registered trademarks of Adobe Systems Incorporated. Amdocs and ClarifyCRM are registered trademarks of Amdocs.
Ariba is a registered trademark of Ariba, Inc. BEA, BEA WebLogic Server, Jolt, and Tuxedo are registered trademarks, and BEA WebLogic Platform is a
trademark of BEA Systems, Inc. Action Request System, BMC Software, PATROL, and Remedy are registered trademarks of BMC Software, Inc. BroadVision
is a registered trademark of BroadVision, Inc. Chem eStandards and CIDX are trademarks of CIDX, The Chemical Industry Data Exchange. SiteMinder and
Unicenter are registered trademarks of CA, Inc. PopChart is a registered trademark of CORDA Technologies, Inc. Kenan and Arbor are registered trademarks
of Alcatel‐Lucent. Data Connection and SNAP‐IX are registered trademarks of Data Connection Corporation. D&B and D‐U‐N‐S are registered trademarks of
Dun & Bradstreet Corporation. Eclipse is a trademark of Eclipse Foundation, Inc. Entrust is a registered trademark of Entrust, Inc. papiNet is a registered
trademark of the European Union and the United States. Financial Information eXchange, F.I.X, and F.I.X Protocol are trademarks of FIX Protocol Ltd.
UCCnet and eBusinessReady are registered trademarks, and 1SYNC and Transora are trademarks of GS1 US. Hewlett‐Packard, HP, HP‐UX, OpenView, PA‐
RISC, and SNAplus2 are trademarks of Hewlett‐Packard Company. i2 is a registered trademark of i2 Technologies, Inc. AIX, AS/400, CICS, ClearCase, DB2,
Domino, IBM, Informix, Infoprint, Lotus, Lotus Notes, MQSeries, OS/390, OS/400, RACF, RS/6000, SQL/400, S/390, System/390, VTAM, and WebSphere, and
z/OS are registered trademarks; and Communications System for Windows NT, DB2 Universal Database, IMS, MVS, and SQL/DS are trademarks of IBM
Corporation. InnoDB is a trademark of Innobase Oy. Itanium is a registered trademark of Intel Corporation. Linux is a registered trademark of Linus
Torvalds. W3C is a registered trademark, and X Window System is a trademark of the Massachusetts Institute of Technology. MetaSolv is a registered
trademark of Metasolv Software, Inc. ActiveX, Microsoft, Outlook, Visual Basic, Visual SourceSafe, Windows, Windows NT, and Windows Server are
registered trademarks of Microsoft Corporation. Six Sigma is a registered trademark of Motorola, Inc. Firefox and Mozilla are registered trademarks of the
Mozilla Foundation. MySQL is a registered trademark of MySQL AB. nCipher is a trademark of nCipher Corporation Ltd. Eclipse is a trademark of Eclipse
Foundation, Inc. Entrust is a registered trademark of Entrust, Inc. papiNet is a registered trademark of the European Union and the United States. Financial
Information eXchange, F.I.X, and F.I.X Protocol are trademarks of FIX Protocol Ltd. UCCnet and eBusinessReady are registered trademarks, and 1SYNC and
Transora are trademarks of GS1 US. Hewlett‐Packard, HP, HP‐UX, OpenView, PA‐RISC, and SNAplus2 are trademarks of Hewlett‐Packard Company. i2 is a
registered trademark of i2 Technologies, Inc. AIX, AS/400, CICS, ClearCase, DB2, Domino, IBM, Informix, Infoprint, Lotus, Lotus Notes, MQSeries, OS/390,
OS/400, RACF, RS/6000, SQL/400, S/390, System/390, VTAM, and WebSphere, and z/OS are registered trademarks; and Communications System for Windows
NT, DB2 Universal Database, IMS, MVS, and SQL/DS are trademarks of IBM Corporation. InnoDB is a trademark of Innobase Oy. Itanium is a registered
trademark of Intel Corporation. Teradata is a registered trademark of NCR Corporation. Netscape is a registered trademark of Netscape Communications
Corporation. ServletExec is a registered trademark, and New Atlanta is a trademark of New Atlanta Communications, LLC. SUSE is a registered trademark
of Novell, Inc. Appia is a registered trademark and Javelin Technologies is a trademark of NYFIX, Inc. CORBA is a registered trademark of Object
Management Group, Inc. JD Edwards, OneWorld, Oracle, PeopleSoft, Siebel, and Vantive are registered trademarks; and Infranet, PeopleSoft Pure Internet
Architecture, Portal, and WorldSoftware are trademarks of Oracle Corporation. Perforce is a trademark of Perforce Software. JBoss and Red Hat are
registered trademarks of Red Hat, Inc. PIP and RosettaNet are trademarks of RosettaNet, a non‐profit organization. SAP and R/3 are registered trademarks
of SAP AG. PVCS is a registered trademark of Serena Software, Inc. SWIFT and SWIFTNet are registered trademarks of Society for Worldwide Interbank
Financial Telecommunication SCRL. SPARC and SPARCStation are registered trademarks of SPARC International, Inc. BAAN and SSA are registered
trademarks; and SSA Global is a trademark of SSA Global Technologies, Inc. EJB, Enterprise JavaBeans, Java, JavaServer, JDBC, JSP, J2EE, Solaris, Sun, and
Sun Microsystems are registered trademarks; and Java Naming and Directory Interface, JavaServer Pages, SOAP with Attachments API for Java, and SunSoft
are trademarks of Sun Microsystems, Inc. Sybase is a registered trademark of Sybase, Inc. VERITAS is a registered trademark, and VERITAS Cluster Server is
a trademark of Symantec Corporation. UNIX is a registered trademark of The Open Group. Unicode is a trademark of Unicode, Inc. VeriSign is a registered
trademark of Verisign, Inc.
Software AG and all Software AG product names are either trademarks or registered trademarks of Software AG.
Other product and company names mentioned herein may be the trademarks of their respective owners.
Copyright © 2004—2007 webMethods, Inc. All rights reserved.
Copyright © 2004—2007 Software AG and/or its suppliers, Uhlandstrasse 12, 64297 Darmstadt, Germany. All rights reserved.

Document ID: MDL-UG-711-20071207

Contents

About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
How to Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing and Uninstalling Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Starting and Stopping the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Restarting the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Running the Metadata Library as a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2. Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Starting the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Defining a Database Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating a Metadata Library Configuration Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Adding a Metadata Library Logical Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring the Metadata Library Logical Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Defining a Metadata Library Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Mapping the Logical Server to a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Mapping an Endpoint on the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Mapping Metadata Library Database Components to Database Pools . . . . . . . . . . . . . . . . . . . . . . . 27
Validating the Metadata Library Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Deploying the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3. Configuring the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Using Central Configuration to Make Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Accessing the Configuration Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Making Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CentraSite Asset Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Metadata Library Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

webMethods Metadata Library User’s Guide Version 7.1.1 3

Contents

Configuration Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Defining and Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Validating and Deploying a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Metadata Library Built-In Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Using My webMethods Server to Authenticate Metadata Library Users . . . . . . . . . . . . . . . . . . . 53
Using My webMethods Server to Grant Access to the Metadata Library . . . . . . . . . . . . . . . . . . 55
Using SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Enabling the Metadata Library to use SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Configuring Designer to Connect to the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Enabling CentraSite Metadata Extraction without Using Central Configuration . . . . . . . . . . . . . . . . . 67

Chapter 4. Using the Metadata Library in Integration Server . . . . . . . . . . . . . . . . . . . . . . 69

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Starting the Integration Server Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Accessing Asset Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configuring Integration Server to Connect to the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Selecting Assets for Metadata Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Deselecting Assets for Metadata Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Publishing Metadata to the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Scheduling Metadata Publish Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Retracting an Asset’s Metadata from the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
WmAssetPublisher.pub.asset:publish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

webMethods Metadata Library User’s Guide Version 7.1.1 4

About This Guide

This guide explains how to configure and manage webMethods Metadata Library. It
also contains information about how to use the Metadata Library with webMethods
Designer 7.1.x, webMethods Integration Server 7.1.x, My webMethods Server 7.1.x,
CentraSite GE 7.1 SP1, and CentraSite EE 3.1.7.

Document Conventions

Convention Description
Bold Identifies elements on a screen.
Italic 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.
Narrow font Identifies storage locations for services on the
webMethods Integration Server using the convention
folder.subfolder:service.
Typewriter font Identifies characters and values that you must type
exactly or messages that the system displays on the
console.
UPPERCASE 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.

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

webMethods Metadata Library User’s Guide Version 7.1.1 5

About This Guide

Additional Documentation. Starting with 7.0, you have the option of downloading the
documentation during product installation to a single directory called
“_documentation,” located by default under the webMethods installation directory. In
addition, you can find documentation for all webMethods products on the
webMethods Bookshelf.

webMethods Metadata Library User’s Guide Version 7.1.1 6

Chapter 1. Introduction

How to Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing and Uninstalling Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Starting and Stopping the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Restarting the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Running the Metadata Library as a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

webMethods Metadata Library User’s Guide Version 7.1.1 7

1. Introduction

How to Use this Guide

This chapter provides a brief overview of Metadata Library and instructions on starting
and running the Metadata Library.
Chapter 2, “Default Configuration” contains instructions on establishing a default
configuration of Metadata Library in webMethods Central Configuration. The first time
you use Central Configuration to configure the Metadata Library, you should follow the
instructions in this chapter.

Note: You only need to follow the instructions in Chapter 2 once. After you have
established the default configuration, you should refer to Chapter 3, “Configuring the
Metadata Library” for instructions on making any future configuration changes.

Chapter 3, “Configuring the Metadata Library” contains detailed instructions on using

Central Configuration to configure the Metadata Library. You should use this chapter as
your primary reference for configuring the Metadata Library once the default
configuration has been established (in Chapter 2).
Chapter 4, “Using the Metadata Library in Integration Server” contains instructions on
publishing and retracting metadata from an Integration Server.

Overview

Metadata Library
Metadata is data about assets in webMethods components (for example, assets modeled in
Designer, Integration Server packages, or CentraSite services).
A Metadata Library provides metadata storage and retrieval features to webMethods
components. A Metadata Library operates as a shared database of metadata. The main
purpose of a Metadata Library is to allow reuse of assets among users. A user can publish
metadata about an asset to the Metadata Library. Other users will be able to see the
published metadata and incorporate the asset into their own projects.
A user does not directly access the Metadata Library. Rather it is accessed by other
webMethods components, namely webMethods Designer, Integration Server, and
CentraSite.

webMethods Metadata Library User’s Guide Version 7.1.1 8

1. Introduction

Designer
Designer can publish metadata about assets to the Metadata Library. It can also browse
the Metadata Library and use metadata in projects.
Designer has an extensive online Help system. Refer to the online Help for instructions on
using Designer.

CentraSite
The Metadata Library itself receives metadata from CentraSite. There is no separate
metadata publisher that must be configured and no configuration is required in
CentraSite.
Metadata extraction from CentraSite is configured in the Metadata Library Configuration
environment in Central Configuration. For more information, see “CentraSite Asset
Publisher” on page 34.

Integration Server
Integration Server can publish metadata about packages to the Metadata Library. For
more information, see Chapter 4, “Using the Metadata Library in Integration Server”.

Installing and Uninstalling Metadata Library

This guide does not contain installation instructions. It is assumed you have already
installed the Metadata Library. Likewise, uninstallation instructions are not provided in
this guide. For installation and uninstallation instructions, see the webMethods Installation
Guide.
After you have completed installation by following the instructions in the webMethods
Installation Guide, an additional step is required to complete the installation of Metadata
Library. You must run MLIVP (Metadata Library Install and Verification Program).
MLIVP verifies the Metadata Library installation and prepares it for use. It is necessary to
run MLIVP only once. It is not required after that and should not be run more than once
unless you are specifically instructed to do so.

Note: If you are using DB2 for Metadata Library’s database components, check DB2’s
transaction log configuration parameters before running MLIVP. The parameters must be
set to at least the recommended minimums (not defaults), namely LOGFILSZ = 1000,
LOGPRIMARY = 10, and LOGSECOND = 2. Consult your database administrator for help.

webMethods Metadata Library User’s Guide Version 7.1.1 9

1. Introduction

To run MLIVP

1 Start the Metadata Library.

See “Starting and Stopping the Metadata Library” below.
2 Run MLIVP:
On Windows: in a command prompt, run Metadata
Library_directory\mlivp\setup.bat
On a Unix‐based system, execute the following script:
Metadata Library_directory/mlivp/setup.sh

Note: By default, MLIVP assumes the Metadata Library is running on port 8090 (which
is the default provided during installation). If you chose to install it to run on a
different port, edit the setup.sh or setup.bat file before running it. In the file, there is a
-port flag. Change the -port value to the correct port number. Save the file and then
run it as instructed above.

3 When asked if you want to continue, type “y” and press Enter.
Wait for the program to finish. It might take a few minutes to complete.
4 You can now begin using the Metadata Library.

webMethods Metadata Library User’s Guide Version 7.1.1 10

1. Introduction

Starting and Stopping the Metadata Library

The Metadata Library can be started like a regular application or can be configured to
start and run automatically as a service (only in Windows).

Note: On Unix‐based operating systems, the Metadata Library is always started as an

application.

To start the Metadata Library as an application

1 Start the Metadata Library:

On Windows: Start >Programs > webMethods > Servers > Metadata Library.
(Alternatively, you can execute the following script:
Metadata Library_directory/library/bin/library.bat)
On a Unix‐based system, execute the following script:
Metadata Library_directory/library/bin/library.sh
2 The Metadata Library command prompt or console appears, displaying status
messages about the Metadata Library. Wait for the following messages to appear
(which indicate the Metadata Library is running):
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
===========================================
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
Build information:
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
cerebra-owlapi-svc.war -- Build <build number> (<date>)
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
cerebra-reasoning-svc.war -- Build <build number> (<date>)
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
uddi-extractor.war -- Build <build number> (<date>)
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
Server Started
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
===========================================

3 Leave the Metadata Library command prompt or console open.

Important! Do not close the Metadata Library command prompt or console. Closing it
will shut down the Metadata Library.

webMethods Metadata Library User’s Guide Version 7.1.1 11

1. Introduction

To start the Metadata Library if it is installed as a service (Windows only)

If the Metadata Library is installed as a Windows service and has been stopped,
start it using the Windows Services management console (Start > Programs >
Administrative Tools > Services). The service name is webMethods Metadata Library.

To stop the Metadata Library if it is running as an application

(Note: This applies to either Windows or Unix‐based systems.)

1 In a Web browser, go to http://localhost:8090/fabric‐admin.
2 For User Name, type Administrator.
3 For Password, type manage.

Note: “manage” is the default password for the Administrator user. For security
reasons, your system administrator might have changed it. If so, ask him or her for the
password.

4 Click OK.
5 Under SERVER FUNCTIONS, click Stop Server.
“Server shutdown in progress” appears.
6 Close the Web browser.
7 The Metadata Library command prompt or console remains open. Close it.

To stop the Metadata Library if it is running as a service (Windows only)

If the Metadata Library is installed as a Windows service, stop the service using
the Windows Services management console (Start > Programs > Administrative Tools >
Services). The service name is webMethods Metadata Library.

webMethods Metadata Library User’s Guide Version 7.1.1 12

1. Introduction

Restarting the Metadata Library

After certain configuration changes, you might have to restart the Metadata Library for
the configuration changes to take effect.

To restart the Metadata Library

(Note: This applies to either Windows or Unix‐based systems.)

1 In a Web browser, go to http://localhost:8090/fabric‐admin.
2 For User Name, type Administrator.
3 For Password, type manage.

Note: “manage” is the default password for the Administrator user. For security
reasons, your system administrator might have changed it. If so, ask him or her for the
password.

4 Click OK.
5 Under SERVER FUNCTIONS, click Restart Server.
“Server restart in progress” appears.
6 Close the Web browser.
7 The Metadata Library command prompt or console displays status messages about
the Metadata Library. Wait for the following messages to appear (which indicate the
Metadata Library is running again):
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
===========================================
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
Build information:
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
cerebra-owlapi-svc.war -- Build <build number> (<date>)
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
cerebra-reasoning-svc.war -- Build <build number> (<date>)
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
uddi-extractor.war -- Build <build number> (<date>)
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
Server Started
[com.webmethods.fabric.server.logging.LoggingService] <date‐time> FATAL:
===========================================

8 Leave the Metadata Library command prompt or console open.

Important! Do not close the Metadata Library command prompt or console. Closing it
will shut down the Metadata Library.

webMethods Metadata Library User’s Guide Version 7.1.1 13

1. Introduction

Running the Metadata Library as a Service

If the Metadata Library is not currently running as a service, that is you must manually
start it like an application, you can configure it to run as a service.

Note: You can run Metadata Library as a service in Windows only. You cannot run it as a
service on Unix‐based systems.

To install the Metadata Library as a Windows Service

1 In a command prompt, navigate to: Metadata Library_directory\library\bin\

2 Type the command: installservice.bat “webMethods Metadata Library”
3 Press ENTER.
4 Restart Windows.
The Metadata Library service starts automatically when you restart.

To uninstall the Metadata Library as a Windows Service

1 In a command prompt, navigate to: Metadata Library_directory\library\bin\

2 Type the command: JBossService.exe -uninstall “webMethods Metadata
Library”
3 Press ENTER.

Note: Since it is no longer installed as a Windows service, you must manually start the
Metadata Library as an application from now on. See “Starting and Stopping the
Metadata Library” on page 11.

webMethods Metadata Library User’s Guide Version 7.1.1 14

Chapter 2. Default Configuration

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Starting the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Defining a Database Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Creating a Metadata Library Configuration Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Adding a Metadata Library Logical Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuring the Metadata Library Logical Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Defining a Metadata Library Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Mapping the Logical Server to a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Mapping an Endpoint on the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Mapping Metadata Library Database Components to Database Pools . . . . . . . . . . . . . . . . . . . 27

Validating the Metadata Library Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Deploying the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

webMethods Metadata Library User’s Guide Version 7.1.1 15

2. Default Configuration

Introduction
To use webMethods Central Configuration to configure the Metadata Library, follow the
instructions in this chapter. You will create a Metadata Library Configuration
environment in Central Configuration and initialize it with default options. Once
established you can use this environment to make future changes to the Metadata
Library’s configuration.
Most, but not all, Metadata Library features are enabled and configured in this chapter. If
you want to enable features not covered here, complete this default configuration and
then see Chapter 3, “Configuring the Metadata Library”. Chapter 3 provides information
about setting options to values other than the defaults provided in this chapter.

Important! After installing the Metadata Library, MLIVP (Metadata Library Install and
Verification Program) must be run once before you start using the Metadata Library. If
MLIVP has not been run, you must do so before following the instructions in this chapter.
See “Installing and Uninstalling Metadata Library” on page 9.

Starting the Metadata Library

You must have the Metadata Library running to complete the procedures in this chapter.
See “Starting and Stopping the Metadata Library” on page 11.

Defining a Database Pool

You must configure a database pool for connecting to the Metadata Library.

To define a database pool for the Metadata Library

1 Log into My webMethods:

a In a Web browser, go to http://localhost:8585.
If you are not on the computer that is running the My webMethods Server,
replace localhost with the host name or IP of the computer it is running on. If it
is not listening to port 8585, enter the correct port instead.
b For User Name, type Administrator.
c For Password, enter Administrator’s password (default is manage).
d Click Login.

Note: You must log in as Administrator or as a user with administrator privileges. For
more information, see Getting Started with My webMethods or the My webMethods Server
Administrator’s Guide.

webMethods Metadata Library User’s Guide Version 7.1.1 16

2. Default Configuration

2 In the navigation bar, select Administration.

3 Select System-Wide > Environments > Database Pool Configuration.
4 Click Add Pool.
5 Give the pool a name and description:
a For Name, type MDL.
b For Description, type For connections to Metadata Library.
6 Specify database connection settings:
a For RDBMS, select the relational database management system that is used by the
Metadata Library.
b For URL, replace the sample format with an actual URL.

Note: There are two database components for the Metadata Library: Repository
and Reasoner. If they were installed to two different databases, you should create
two database pools, one for each component. If they are installed to the same
database, you can use the same, single database pool. You can determine if they
were installed to different databases by looking at the cerebraRepo.xml and
cerebraReso.xml files. For more information, see the note following the table
below.

The following are sample URLs for the supported relational database
management systems:

RDBMS URL Syntax

Oracle jdbc:wm:oracle://server:port;serviceName=service[;option=value...]
For example:
jdbc:wm:oracle://localhost:1521;ServiceName=oracle_service_name

webMethods Metadata Library User’s Guide Version 7.1.1 17

2. Default Configuration

RDBMS URL Syntax

SQL jdbc:wm:sqlserver://server:port;databaseName=database[;option=value...]
Server
For example:
jdbc:wm:sqlserver://localhost:1433;DatabaseName=mdl
DB2 jdbc:wm:db2://server:port;databaseName=database[;option=value…]
For example:
jdbc:wm:db2://localhost:50000;DatabaseName=mdl

Important! For DB2, if you are installing in a schema other than the
default schema for the specified database user, you must specify these
connection options:
AlternateId=schema;InitializationString="SET CURRENT
PATH=schema"
AlternateID is the name of the default schema that is used to qualify
unqualified database objects in dynamically prepared SQL
statements.

Note: The database connection URL was initially set during installation of the
Metadata Library. You can find the URL specified during installation by viewing
the cerebraRepo.xml and cerebraReso.xml files. The files are located in: Metadata
Library_directory\library\server\library\conf\JDBC\pools. In each file, the <url>
element specifies the database connection URL. For example:
<connection>
<url>jdbc:wm:sqlserver://localhost;DatabaseName=mdl</url>

</connection>

The <url> element in the cerebraRepo.xml file specifies the URL for the Metadata
Repository. The <url> element in the cerebraReso.xml file specifies the URL for the
Metadata Reasoner. Typically, both <url> elements will specify the same database.

c For Database User, enter a valid user for accessing the Metadata Library database.
If you used the default during Metadata Library installation, the database user is
mdluser.

webMethods Metadata Library User’s Guide Version 7.1.1 18

2. Default Configuration

d For Database Password, enter the password for the database user. If you used the
default during Metadata Library installation, the password is mdluserpass.
e Click Test to make sure you can connect to the Metadata Library database with the
connection settings you just specified.
“Test Passed!” should appear at the bottom of the screen.

Note: If the test fails, make sure the Metadata Library is running. For information
about starting the Metadata Library, see “Starting and Stopping the Metadata
Library” on page 11.

7 Set pool options as described in the following table.

(Note that all values are the defaults, except Maximum Connections.)

Option Value
Minimum Connections 4

Maximum Connections 50 (not the default, change it to this value)

Idle Connection Timeout 20

Ramp‐up Delay 500

Connection Tries 8

Retries Backoff 500

Allow Statement Caching (clear the check box, which disables statement
caching)

8 Click Save.
9 You are returned to the Database Pool Configuration page. MDL appears under POOL.

Creating a Metadata Library Configuration Environment

A configuration environment is a collection of configuration settings for a particular type
of component. You must create a configuration environment for the Metadata Library. For
more information about environments, see the webMethods Central Configuration and
Deployment Guide.

To create a Metadata Library Configuration environment

1 Select System-Wide > Environments > Define Environments.

2 Click Add Environment.

webMethods Metadata Library User’s Guide Version 7.1.1 19

2. Default Configuration

3 For Environment Name, type Metadata Library Configuration.

Note: You can choose any name you want for the environment. However, Software AG
recommends you use the name suggested above. The rest of this guide refers to this
name. If you choose a different name, substitute it whenever you see the
recommended name used in this guide.

4 For Description, type Configuration options for Metadata Library and

CentraSite extractor.

5 Click Save.
The Metadata Library Configuration environment appears under ENVIRONMENT NAME.

Adding a Metadata Library Logical Server

You must add a Metadata Library logical server to the Metadata Library Configuration
environment. A logical server describes the configuration settings for a webMethods
software component. It is called a logical server to distinguish it from a physical server. It is
“logical” in the sense that it is an abstract description or specification of a server. Logical
servers are mapped to one or more physical servers. For more information about logical
servers, see the webMethods Central Configuration and Deployment Guide.

To add a Metadata Library logical server

1 Under ENVIRONMENT NAME, select Metadata Library Configuration.

2 On the Design Servers tab, click Add.
3 In the Add Logical Servers dialog box, select Medata Library v7.1.0.0 and click OK.
Medata Library v7.1.0.0 appears under LOGICAL SERVER NAME.

Configuring the Metadata Library Logical Server

You must specify the following for the Metadata Library logical server:
How the Metadata Library connects to CentraSite to extract metadata.

What type of information will be written to the Metadata Library’s log file.

Whether the Metadata Library connects to the My webMethods Server for user
authentication.
What port the Metadata Library is listening to.

webMethods Metadata Library User’s Guide Version 7.1.1 20

2. Default Configuration

To configure the Metadata Library logical server

1 Select the Configure Servers tab.

2 Under CONFIGURATION, expand Medata Library v7.1.0.0.
3 Set CentraSite options:
These options control how metadata is extracted from CentraSite about registered
services. For more information, see “CentraSite Asset Publisher” on page 34.
a Select CentraSite Asset Publisher.
CentraSite Asset Publisher for Metadata Library options appear.
b Set options as described in the following table.

Option Setting
Registry User [email protected] (default)

Note: If you want to disable metadata extraction

from CentraSite, leave this option blank and skip
the rest of these options.

Registry Password manage

Note: A masked password is shown by default. Be

sure to replace it with “manage”. This is the default
password. However, your system administrator
might have changed it. If so, ask him or her for the
new password.

webMethods Metadata Library User’s Guide Version 7.1.1 21

2. Default Configuration

Option Setting
Registry Security URL For these options, do not change anything but
localhost or port number if necessary. If
Registry Inquiry URL CentraSite is located on another computer, replace
Registry Publish URL localhost with the host name or IP address of the
computer. If CentraSite is listening to a different
Registry Taxonomy URL port, replace the default 2020 with the correct port.
Registry Subscription URL
Note: Registry Taxonomy URL is optional.

Note: By default, CentraSite is installed to listen to

port 2020. Unless a different port was chosen
during installation, you should keep the default
port of 2020 for these options.

Note: To have the Metadata Library connect to

CentraSite using SSL, change the protocol prefix in
these URLs to “https”. Make sure the Metadata
Library is set up as an SSL client to CentraSite; see
“Enabling the Metadata Library to use SSL” on
page 58.

Registry Subscription 2 (default)

Interval
Note: This value is in minutes.

Registry Subscription Name webMethods (default)

OverviewURL Loader Class The class that is used to load the WSDL content
using the WSDL URL of the service. If no value is
specified, the following default value is used:
com.webmethods.uddi.extractor.XRegistryURLLoader

c Click Save.
4 Set logging options:
These options control how system or error information about the Metadata Library is
logged and displayed.
a Select MDL Journal Logging.
Journal Loggers for Metadata Library options appear.

webMethods Metadata Library User’s Guide Version 7.1.1 22

2. Default Configuration

b Leave the options at their defaults as shown in the following illustration.

With these settings, logging information will be saved to the following file:
Metadata Library_directory\library\server\library\log\server.log.
For more information, see “Logging” on page 37.
c Click Save.
5 Select Metadata Library Configuration.
6 Set Metadata Library options:
These options control how the Metadata Library exposes itself for access by other
applications and how it runs.
a For Host, leave the default value of localhost.
b For Port, enter the port the Metadata Library is listening to. By default, this is
8090.

The port number is initially set during installation of the Metadata Library. If the
default was chosen, the port is 8090. If you are unsure what port number was
entered during installation you can find it in the server.xml file. The file location
is: Metadata Library_directory\library\server\library\deploy\fabric‐
tomcat.sar\server.xml. In that file, the port attribute of the Connector element
specifies the port number. For example:

webMethods Metadata Library User’s Guide Version 7.1.1 23

2. Default Configuration

Note: If you specify a port that is already in use by another application or service
and deploy the Metadata Library configuration, Central Configuration will no
longer be able to communicate with the Metadata Library. If this occurs, see “To
fix the Metadata Library port” on page 42.

c For MwS Location (Specify to enable MwS authentication), enter the URL of a My
webMethods Server.
The Metadata Library can authenticate users on its own. Entering the URL of a
My webMethods Server here means the Metadata Library should also rely on the
My webMethods Server to authenticate users (in addition to its own
authentication services). You can leave this option blank if you want users
authenticated only by the Metadata Library itself. For more information, see
“Using My webMethods Server to Authenticate Metadata Library Users” on
page 53.
By default, MwS Location (Specify to enable MwS authentication) is
http://localhost:8585. If the My webMethods Server is running on another
computer, enter that computer’s host name or IP address in place of “localhost”. If
the My webMethods Server is listening to a different port, enter it in place of
“8585”.

Note: If the My webMethods Server requires SSL, enter https instead of http in
the MwS Location (Specify to enable MwS authentication) URL. Also, you must specify a
trust store and password; see step g below.

d For MwS User, accept the default of Administrator.

e For MwS Password, type the password manage.
If the Administrator user’s password has been set to something different, enter it
instead.
f For Key Store (Specify to enable SSL) and Key Store Password, leave them blank. If Key
Store has a value entered for it, delete it.
g If the My webMethods Server requires SSL, specify the truststore file in Trust Store
(Specify if accessing MwS via SSL). If SSL is not required, leave Trust Store blank.
a

Note: A truststore allows the Metadata Library to verify that it can trust
communication from the My webMethods Server. The truststore file contains
certificates obtained from a certificate authority (for example, VeriSign), and is
provided and installed by your system administrator.

What you enter in the Trust Store box is interpreted as a relative path off Metadata
Library_directory/library/server/library/conf/. Typically, the truststore file is placed

webMethods Metadata Library User’s Guide Version 7.1.1 24

2. Default Configuration

in the ../conf/security/ directory (in which case you would enter

./security/filename).

Important! You must use Unix path syntax (for example, “/” instead of “\”) in the
this box even if you are on a Windows system.

h If you specified a truststore above, for Trust Store Password, enter a password to
access it.
Your system administrator should provide you with this password.
i Click Save.

Note: The password fields might show a different number of mask characters than
the number of actual characters in the password. This is intentionally done to hide
the number of characters in the password.

Defining a Metadata Library Host

You must specify the Metadata Library host; that is, you must specify the computer that is
running the Metadata Library. Complete the following steps.

To define the Metadata Library host

1 Select the Define Hosts tab.

2 Click Add Hosts.
The Add/Edit Host dialog box appears.
3 For Display Name, type Metadata Library.
4 For Host Name or IP Address: enter the host name or IP address of the computer running
the Metadata Library.
If it is running on the same computer as Central Configuration, type localhost.

Note: Enter only the host name or IP address. Do not include a protocol prefix like
“http://”.

webMethods Metadata Library User’s Guide Version 7.1.1 25

2. Default Configuration

Mapping the Logical Server to a Host

You must map the Metadata Library logical server to a physical host (that is, an actual
computer running the Metadata Library). Complete the following steps.

To map the Metadata Library logical server to a host

1 Select the Map Servers tab.

2 Under ACTIONS, click the (Edit) icon for Metadata Library.

The Edit Host Mapping For: Metadata Library dialog box appears.
3 Under AVAILABLE HOSTS TO MAP, select the host you defined earlier (see “Defining a
Metadata Library Host” on page 25).

4 Click the icon.

The selected host appears under MAPPED HOSTS TO THIS LOGICAL SERVER.
5 Click Save.

Mapping an Endpoint on the Host

The Metadata Library has a Configuration Agent service that takes the settings chosen in
Central Configuration and applies them to the Metadata Library. Central Configuration
does not directly configure the Metadata Library. It sends configuration settings to the
Configuration Agent.
You must specify which port the Configuration Agent is listening to for configuration
changes—referred to as mapping an endpoint.

To map an endpoint

1 Select the Map Endpoints tab.

2 Under INCOMING CONNECTIONS, enter the port that the Configuration Agent is
listening to. Leave the http portion as it is.
By default the port number is 8090.

Note: The port number you enter here must match the port number you entered for
Port on page 23.

3 Under ACTIONS, click the (Edit) icon for Configuration Agent.

The Edit Configuration Agent Credential Metadata Library dialog box appears.

webMethods Metadata Library User’s Guide Version 7.1.1 26

2. Default Configuration

4 For User Name, type Administrator.

5 For User Password, enter the Administrator user’s password (default: manage).

Note: The user name and password you enter here must be for a valid Metadata
Library user, not a My webMethods Server user. The Metadata Library maintains its
own internal list of users. By default, the Metadata Library has a user named
“Administrator” with password “manage”.

6 Click Save to return to the Map Endpoints tab.

7 Click Save.

Mapping Metadata Library Database Components to Database

Pools
You must map Metadata Library database components to the MDL database pool you
created in “Defining a Database Pool” on page 16.

To map the Metadata Library database components to a database pool

1 Select the Map DB Pools tab.

2 For the three database components, select the MDL pool. See the following illustration.

Select the MDL pool

for each component

ReasoningDB refers to the Metadata Reasoner database component. RepositoryDB

and SnapshotDB refer to the Metadata Repository database component. These
database components were installed using the DCI scripts when you installed the
Metadata Library.
3 Click Save.

webMethods Metadata Library User’s Guide Version 7.1.1 27

2. Default Configuration

Validating the Metadata Library Configuration

Before deploying the configuration, you must validate it. Validation ensures that required
settings are in place and that the configured endpoint maps to a valid Configuration
Agent on the Metadata Library.

To validate the configuration

1 Make sure all tabs (except Validate) in the environment have green check marks,
indicating they have been configured. See the following illustration.

2 Select the Validate tab.

The configuration is validated. If it is valid, “Valid Configuration” appears. If not,
“Invalid Configuration” appears and the Configuration Report box lists the problems
found in the configuration. Use this information to correct any problems. You can go
back to any of the tabs and make changes.
3 If the configuration is valid, click Finish.
You are returned to the Define Environments page. Green check marks appear under
CONFIGURED and READY TO DEPLOY for Metadata Library Configuration.

Deploying the Configuration

Once you have a valid configuration, you are ready to deploy it to the Metadata Library.
Complete the following steps.

Note: The configuration options you have selected will not be reflected in the Metadata
Library until you deploy the configuration.

To deploy the configuration

1 Under ACTIONS, click the (Deploy) icon for Metadata Library Configuration.
2 Click Deploy All.
“Successfully deployed environment” appears.

Note: For more information about deploying a configuration environment, see the
webMethods Central Configuration and Deployment Guide.

webMethods Metadata Library User’s Guide Version 7.1.1 28

2. Default Configuration

3 Click Close.
You are returned to the Define Environments page. You are done using Central
Configuration; you can logout of My webMethods if you want.

webMethods Metadata Library User’s Guide Version 7.1.1 29

2. Default Configuration

webMethods Metadata Library User’s Guide Version 7.1.1 30

Chapter 3. Configuring the Metadata Library

Using Central Configuration to Make Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Accessing the Configuration Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Making Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Validating and Deploying a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

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

Configuring Designer to Connect to the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Enabling CentraSite Metadata Extraction without Using Central Configuration . . . . . . . . . . . . . 67

webMethods Metadata Library User’s Guide Version 7.1.1 31

3. Configuring the Metadata Library

Using Central Configuration to Make Configuration Changes

In Chapter 2, “Default Configuration” you completed a default configuration of the
Metadata Library.
This chapter contains more detailed information than Chapter 2 and is intended to be
used whenever you want to make configuration changes to the Metadata Library.

Important! This chapter assumes you have created the Metadata Library Configuration
environment in Chapter 2, “Default Configuration”.

To make configuration changes to the Metadata Library, you will use the Metadata
Library Configuration environment in Central Configuration.

Almost all configuration is performed using the configuration tabs in this environment:

Design Servers Map Endpoints

Configure Servers Map DB Pools
Define Hosts Validate
Map Servers

Each tab contains a number of configuration options.

webMethods Metadata Library User’s Guide Version 7.1.1 32

3. Configuring the Metadata Library

Typically, the general steps in making configuration changes to the Metadata Library are:
1 Make changes in the configuration tabs.
2 Validate and deploy the configuration.
3 Restart the Metadata Library.
The remaining sections of this chapter describe how to perform these tasks.

Note: The Metadata Library you want to configure must be running. For instructions, see
“Starting and Stopping the Metadata Library” on page 11.

Accessing the Configuration Environment

To make configuration changes, you must access the Metadata Library Configuration
environment.

To access the Metadata Library Configuration environment

1 Log into My webMethods:

Note: You must log in as Administrator or as a user with administrator privileges. For
more information, see Getting Started with My webMethods or the My webMethods Server
Administrator’s Guide.

2 In the navigation bar, select Administration.

3 Select System-Wide > Environments > Define Environments.

webMethods Metadata Library User’s Guide Version 7.1.1 33

3. Configuring the Metadata Library

4 Under ENVIRONMENT NAME, select Metadata Library Configuration.

Note: “Metadata Library Configuration” is the recommended name for the

configuration environment. However, the person who performed the default
configuration of the Metadata Library might have chosen a different name for the
environment. If there is not an environment named “Metadata Library
Configuration”, you might be able to determine which is the correct environment by
selecting each of the environments listed. If the Design Server tab lists only a Medata
Library v7.1.0.0 logical server name, then you are probably in the correct environment.
If you are unsure, you should consult the person who initially configured the
Metadata Library.

Making Configuration Changes

CentraSite Asset Publisher

The Metadata Library can extract metadata about the services registered in CentraSite.

Note: You can enable metadata extraction from CentraSite without using Central
Configuration. See “Enabling CentraSite Metadata Extraction without Using Central
Configuration” on page 67.

To enable or disable CentraSite metadata extraction

webMethods Metadata Library User’s Guide Version 7.1.1 34

3. Configuring the Metadata Library

To set CentraSite Asset Publisher options

Important! If you do not want to change a setting, leave it at its current value; do not
blank it out. All values are required for metadata extraction from CentraSite to work
properly.

Note: The URLs (that is, Registry Security, Inquiry, Publish, and Subscription) in the
following table show the correct paths to the various services. The paths in these
URLs should not change. Only change localhost or the port number if necessary. If
CentraSite is running on another server, replace localhost with the host name or IP
address of the server. If CentraSite is listening to a different port, replace the default
with the correct port. By default, CentraSite is installed to listen to port 2020. Unless a
different port was chosen during installation, you should use the default port of 2020
for these options.

Note: To connect to CentraSite using SSL, change the protocol prefix in the Registry
Security, Inquiry, Publish, and Subscription URLs to https instead of http. Make sure
the Metadata Library is set up as an SSL client to CentraSite; see “Enabling the
Metadata Library to use SSL” on page 58.

Option Description
Registry User A valid CentraSite user name. A default user name
initially installed in the system is:
[email protected]

Note: To disable metadata extraction from CentraSite,

leave this option blank. That is all that is needed to
disable extraction. To re‐enable it, enter a valid user
name.

webMethods Metadata Library User’s Guide Version 7.1.1 35

3. Configuring the Metadata Library

Option Description
Registry Password The password for the user name you entered above.
The initial, default password for the
[email protected] user is: manage

Note: The default password might have been changed

by your system administrator for security reasons.

Registry Security URL The URL for fetching UDDI authentication tokens
from CentraSite. An authentication token is required
for inquiry access to CentraSite.
Example URL:
http://localhost:2020/registry/uddi/
security
Registry Inquiry URL The URL for accessing the inquiry API of CentraSite.
Web service details are fetched from CentraSite using
this URL.
Example URL:
http://localhost:2020/registry/uddi/
inquiry
Registry Publish URL The URL for accessing the publish API of CentraSite.

Example URL:
http://localhost:2020/registry/uddi/
publish
Registry Taxonomy URL The URL for accessing the taxonomies of CentraSite.
This field is optional.

Example URL:
http://localhost:2020/registry/uddi/
taxonomy
Registry Subscription URL The URL for accessing the subscription API of
CentraSite.
Example URL:
http://localhost:2020/registry/uddi/
subscription
Registry Subscription Interval How often CentraSite is checked for changes to Web
services. This is a numeric value, interpreted in
minutes. Recommended setting: 2.

webMethods Metadata Library User’s Guide Version 7.1.1 36

3. Configuring the Metadata Library

Option Description
Registry Subscription Name This option controls which business in CentraSite will
have metadata extracted about its services. You can
extract metadata from only one business at a time.
“Business” is a level in the data hierarchy in
CentraSite. By convention, it usually represents an
actual business entity. For more information, see the
CentraSite Governance Edition User’s Guide.
Recommended setting: webMethods
OverviewURL Loader Class The class that is used to load the WSDL content using
the WSDL URL of the service. If no value is specified,
the following default value is used:
com.webmethods.uddi.extractor.XRegistryURLLoader

4 Click Save.

Logging
A text log file is created and updated with system and error information about the
Metadata Library. If you experience any problems with the Metadata Library, looking in
the log file might help diagnose their nature.
The log file is located in Metadata Library_directory\library\server\library\log\. The
name of the log file is server.log. This is a daily file that is rolled over at midnight, local
time. Previous days’ files have the date appended to their names, in the format
server.log.YYYY‐MM‐DD (for example, server.log.2007‐04‐15). The current day’s file is
always named server.log.
You can control the type of information and level of detail that is written to the log file and
whether the information is also displayed to the Metadata Library console or command
prompt.

To access logging options

webMethods Metadata Library User’s Guide Version 7.1.1 37

3. Configuring the Metadata Library

3 Select MDL Journal Logging.

The JOURNAL LOGGERS FOR METADATA LIBRARY panel appears. For example:

There are different loggers for various components of Metadata Library. Each logger
is responsible for adding information about its component to the server.log file. Root
is the main logger. It serves as the default. It specifies whether logging in general is
enabled and provides the logging threshold for any component not represented by
one of the other loggers. It also can override the threshold for the other loggers. If
root’s threshold is more stringent than any of the others, the other loggers will adhere
to root’s threshold regardless of what is set individually for them.

To enable or disable logging

1 Navigate to the JOURNAL LOGGERS FOR METADATA LIBRARY panel.

For instructions, see “To access logging options” on page 37.

2 Click the (ASSIGN TARGETS) button for root.

The ASSIGN TARGETS TO ROOT panel appears:

3 To enable logging, select the check box for Console or DailyFile or both.

webMethods Metadata Library User’s Guide Version 7.1.1 38

3. Configuring the Metadata Library

If you want information displayed to the Metadata Library command prompt or

console, select Console.
If you want logging information written to the server.log file, select DailyFile.

Note: If you do not see DailyFile or Console targets listed, you must create them. For
instructions, see “To create a DailyFile target” on page 40 or “To create a Console
target” on page 40.

4 To disable logging, clear all check boxes.

This causes the root logger to not have any assigned targets. This disables logging.
5 Click Save.

To set logging thresholds

Each logger has a “threshold” which determines the level of detail that will be logged for
its component. You can choose from a range of thresholds that goes from least to most
severe messages.
1 Navigate to the JOURNAL LOGGERS FOR METADATA LIBRARY panel.
For instructions, see “To access logging options” on page 37.
2 For each logger, under THRESHOLD, select the level of messages you want written to
the server.log file and displayed to the command prompt or console.
The threshold levels range from TRACE to FATAL (least to most severe). Generally,
TRACE provides the most amount of information while FATAL provides the least.
TRACE will log everything including tracing messages produced by the software.
FATAL will log only fatal error messages. The threshold levels in between correspond
to information levels in between TRACE and FATAL.
Setting a logger’s threshold to none means you do not want logging information from
that logger’s component.

Note: A “none” option is not available for the root logger. If you want to disable
logging entirely, see “To enable or disable logging” on page 38.

The threshold level for root can override the other loggers’ thresholds. If a logger’s
threshold is less severe than root’s, then root’s threshold overrides it. For example, if
root threshold is set to ERROR and com.webmethods is set to TRACE, only those
com.webmethods messages ERROR or more severe will be logged. Any message less
severe than ERROR will not be logged even though com.webmethods threshold is set
to TRACE.
3 Click Save.

webMethods Metadata Library User’s Guide Version 7.1.1 39

3. Configuring the Metadata Library

To create a DailyFile target

1 Click Target List.

2 Click Add Target.
3 For Name, type DailyFile.
4 For Description, enter a description (optional).
5 Leave Threshold at its default setting.
6 For Write To, select File.
7 For File:, type ./server.log.
This will write logging information to Metadata Library_directory/library/
server/library/log/server.log.
8 Leave the Rollover file by settings at their defaults of Time Period only and Midnight.
9 Click Save.
10 Click Save again to return to the JOURNAL LOGGERS FOR METADATA LIBRARY panel.

To create a Console target

1 Click Target List.

2 Click Add Target.
3 For Name, type Console.
4 For Description, enter a description (optional).
5 Leave Threshold at its default setting.
6 For Write To, select Console.
7 For Destination, select the output stream messages should be displayed to.
If you are not sure, select System.Out.
8 Click Save.
9 Click Save again to return to the JOURNAL LOGGERS FOR METADATA LIBRARY panel.

webMethods Metadata Library User’s Guide Version 7.1.1 40

3. Configuring the Metadata Library

Metadata Library Port

A Metadata Library is accessed via a particular port on its host server. You can change this
port in Central Configuration.

Note: If you change the port of a Metadata Library, you will have to update any instances
of Designer or Integration Server that connects to it. In their connection configurations,
change the port for Metadata Library to the new port. For more information, see
“Configuring Designer to Connect to the Metadata Library” on page 66 or “Configuring
Integration Server to Connect to the Metadata Library” on page 71.

To change the Metadata Library port

Note: Leave Host set to localhost even if the Metadata Library is running on a
different server. The Host setting on this screen is not currently used by Central
Configuration.

5 For Port, enter the port the Metadata Library should listening to. By default, this is
8090.

Important! The port you enter must not be in use by another program on the same
server. It is recommended you use the default port of 8090. If you enter a port that is
already in use and deploy the Metadata Library configuration, Central Configuration
will no longer be able to communicate with the Metadata Library. If this occurs, see
“To fix the Metadata Library port” on page 42.

6 Click Save.

Important! The Configuration Agent must also be set to the same port. See “To change
Configuration Agent settings” on page 43.

webMethods Metadata Library User’s Guide Version 7.1.1 41

3. Configuring the Metadata Library

To fix the Metadata Library port

If a bad port was configured for the Metadata Library (for example, one already in use),
Central Configuration might no longer be able to communicate with the Metadata
Library. Complete these steps to have the Metadata Library listen to a different, unused
port. Once this is done, Central Configuration should be able to communicate with the
Metadata Library.
1 Open the following file in a text editor:
Metadata Library_directory\library\server\library\conf\
MetadataProperties.xml
2 In this file, the following element controls which port the Metadata Library is
listening to:
<entry key="Port" type="Long">
<rendering-properties>
<property name="label" value="Port"/>
<property name="size" value="10"/>
<property name="type" value="textfield"/>
</rendering-properties>
<value>8090</value>
</entry> Change this value to an unused port

3 Change the port number as indicated above.

4 Save and close the file.
5 Restart the Metadata Library.
For instructions, see “Restarting the Metadata Library” on page 13.
6 In Central Configuration, be sure to update the Metadata Library port to the new port
number you chose.

Configuration Agent
Central Configuration does not directly configure the Metadata Library. Instead it sends
configurations to the Configuration Agent. The Configuration Agent is a Web service that
is part of a Metadata Library. It handles configuration changes to the Metadata Library.
There are two settings you must specify for the Configuration Agent:
Port: the port the agent listens to; this must be the same as the Metadata Library port
(see “Metadata Library Port” on page 41).
User name and password: the user name and password Central Configuration sends to
the Configuration Agent. This is used to verify that Central Configuration is allowed
to send configuration changes to the Metadata Library.

webMethods Metadata Library User’s Guide Version 7.1.1 42

3. Configuring the Metadata Library

To change Configuration Agent settings

1 In the Metadata Library Configuration environment, select the Map Endpoints tab.
For instructions on accessing the environment, see “Accessing the Configuration
Environment” on page 33.
2 Under ENDPOINT CONFIGURATION, expand Medata Library v7.1.0.0.
3 For Configuration Agent, under INCOMING CONNECTIONS, enter the port protocol and
number. In the following illustration, the port protocol is http and the port number is
8090.

Important! The port number you enter here must match the port number you entered
on the Configure Server tab. See “To change the Metadata Library port” on page 41.

4 Under ACTIONS, click the (Edit) icon for Configuration Agent.

The Edit Configuration Agent Credential Metadata Library dialog box appears.
5 For User Name, type Administrator.
6 For User Password, enter the password for the Administrator user that is built into the
Metadata Library (default: manage).

For more information about the Administrator user, see “Metadata Library Built‐In
Users” on page 52.
7 Click Save.

webMethods Metadata Library User’s Guide Version 7.1.1 43

3. Configuring the Metadata Library

Defining and Mapping Hosts

To be able to deploy configuration changes to a Metadata Library, you must specify the
physical host server on which it is running. This is a two stage process.
1 Define a host: specify the host name or IP address of the server on which a Metadata
Library is running.
2 Map the host to the Metadata Library logical server: by mapping a host to the Metadata
Library logical server, you are specifying that you want the configuration changes you
make to be deployed to the host. Any Metadata Library configuration changes you
make in Central Configuration are deployed only to those hosts that are mapped to
the Metadata Library logical server.
An initial host definition and mapping should have been completed during initial
configuration (see Chapter 2, “Default Configuration”). If the Metadata Library has been
moved to a different server, you must change its host definition. See “To change a host
definition and mapping” below.
It is possible to have multiple Metadata Libraries running on different host servers. You
can deploy a configuration from Central Configuration to the Metadata Libraries. All of
the Metadata Libraries will be configured the same. This is accomplished by specifying
multiple hosts and then mapping those hosts to the single Metadata Library logical server.
See “To create a host definition and mapping” on page 45.

To change a host definition and mapping

If a Metadata Library has been moved so it is now running on a different server, you must
change its host definition in Central Configuration to match. Otherwise, you will not be
able to deploy configuration changes to it.
1 In the Metadata Library Configuration environment, select the Define Hosts tab.
For instructions on accessing the environment, see “Accessing the Configuration
Environment” on page 33.
2 Under DISPLAY NAME, select the name of the host server.
The Add/Edit Host dialog appears.
3 For Host Name or IP Address, enter the new host name or IP address.

Note: Enter only the host name or IP address. Do not include a protocol prefix like
“http://”.

4 Click OK.

Note: The host‐to‐logical‐server mapping, on the Map Servers tab, will automatically
update to reflect the new host name or IP address you entered.

webMethods Metadata Library User’s Guide Version 7.1.1 44

3. Configuring the Metadata Library

To create a host definition and mapping

You can create multiple host definitions and mappings if you have multiple Metadata
Libraries. This allows you to set configuration options in Central Configuration and
deploy them to multiple Metadata Libraries at once. Repeat the following instructions for
each Metadata Library.
1 In the Metadata Library Configuration environment, select the Define Hosts tab.
For instructions on accessing the environment, see “Accessing the Configuration
Environment” on page 33.
2 Click Add Host.
The Add/Edit Host dialog appears.
3 For Display Name, enter a name for the host server.
Enter a name that will distinguish it from other hosts.
4 For Host Name or IP Address, enter the host name or IP address of the server.

Note: Enter only the host name or IP address. Do not include a protocol prefix like
“http://”.

5 Click OK.
6 Select the Map Servers tab.

7 Under ACTIONS, click the (Edit) icon for Metadata Library.

The Edit Host Mapping For: Metadata Library dialog box appears.
8 Under AVAILABLE HOSTS TO MAP, select the host you just defined.

9 Click the icon.

The selected host appears under MAPPED HOSTS TO THIS LOGICAL SERVER.
10 Click Save.

To delete a host definition and mapping

If a host definition no longer is needed—for example, the Metadata Library it represents is

no longer used—you should delete it from the Metadata Library Configuration
environment.
1 In the Metadata Library Configuration environment, select the Define Hosts tab.
For instructions on accessing the environment, see “Accessing the Configuration
Environment” on page 33.

webMethods Metadata Library User’s Guide Version 7.1.1 45

3. Configuring the Metadata Library

2 Select the check box for the host definition you want to delete.
If you wantwant to delete more than one host definition, select the check boxes for the
other host definitions to be deleted.
3 Click Delete Host.
4 You are asked if you want to delete the physical server(s). Click OK.

Note: The host‐to‐logical‐server mapping, on the Map Servers tab, will automatically
update to reflect the deletion.

Database Connection
In Central Configuration, a database connection pool specifies the parameters for a
Metadata Library’s connection to its databases which are managed by a relational
database management system (Oracle, SQL Server, or DB2).
Complete the following procedure to change or create a database connection pool for the
Metadata Library.

To edit or create a database connection pool

1 If you are changing the settings for an existing database pool, find the names of the
pools currently used by the Metadata Library:
a In the Metadata Library Configuration environment, select the Map DB Pools tab.
For instructions on accessing the environment, see “Accessing the Configuration
Environment” on page 33.
b In the POOL column, note the pool currently selected for each Metadata Library
component. They might all be the same (by default: MDL).
2 Select System-Wide > Environments > Database Pool Configuration.
3 If you are creating a new pool, click Add Pool and skip to step 5.
4 If you are changing settings for an existing pool, under POOL, select a database
connection pool (the one you found on the Map DB Pools tab).
5 If you are creating a new pool, for Name, click Other. Then enter a name for the pool
and click OK.
6 For RDBMS, select the relational database management system used by the Metadata
Library to store data.

webMethods Metadata Library User’s Guide Version 7.1.1 46

3. Configuring the Metadata Library

7 For URL, enter the URL needed to access the Metadata Library database.

Note: There are two database components for the Metadata Library: Repository and
Reasoner. If they were installed to two different databases, you should create two
database pools, one for each component. If they are installed to the same database,
you can use the same, single database pool. You can determine if they were installed
to different databases by looking at the cerebraRepo.xml and cerebraReso.xml files.
For more information, see the note following the table below.

The following are sample URLs for the supported relational database management
systems:

RDBMS URL Syntax

Oracle jdbc:wm:oracle://server:port;serviceName=service[;option=value...]
For example:
jdbc:wm:oracle://localhost:1521;ServiceName=oracle_service_name
SQL jdbc:wm:sqlserver://server:port;databaseName=database[;option=value...]
Server
For example:
jdbc:wm:sqlserver://localhost:1433;DatabaseName=mdl
DB2 jdbc:wm:db2://server:port;databaseName=database[;option=value…]
For example:
jdbc:wm:db2://localhost:50000;DatabaseName=mdl

Important! For DB2, if you are installing in a schema other than the default
schema for the specified database user, you must specify these
connection options:
AlternateId=schema;InitializationString="SET CURRENT
PATH=schema"
AlternateID is the name of the default schema that is used to qualify
unqualified database objects in dynamically prepared SQL statements.

webMethods Metadata Library User’s Guide Version 7.1.1 47

3. Configuring the Metadata Library

Note: The database connection URL was initially set during installation of the
Metadata Library. You can find the URL specified during installation by viewing the
cerebraRepo.xml or cerebraReso.xml files. The files are located in: Metadata
Library_directory\library\server\library\conf\JDBC\pools. In each file, the <url>
element specifies the database connection URL. For example:
<connection>
<url>jdbc:wm:sqlserver://localhost;DatabaseName=mdl</url>

</connection>

8 For Database User, enter a valid user for accessing the Metadata Library database. If
you used the default during Metadata Library installation, the database user is
mdluser.

Note: During installation of the Metadata Library, if you specified a different database
user in the DCI scripts, enter that user instead.

9 For Database Password, enter the password for the database user. If you used the
default during Metadata Library installation, the password is mdluserpass.

Note: During installation of the Metadata Library, if you specified a different database
user password in the DCI scripts, enter that password instead.

10 Click Test to make sure you can connect to the Metadata Library database with the
connection settings you just specified.
“Test Passed!” should appear at the bottom of the screen.

webMethods Metadata Library User’s Guide Version 7.1.1 48

3. Configuring the Metadata Library

11 Set pool options as described in the following table.

(Note that all values are the defaults, except Maximum Connections.)

Option Value
Minimum Connections 4

Maximum Connections 50 (not the default, change it to this value)

Idle Connection Timeout 20

Ramp‐up Delay 500

Connection Tries 8

Retries Backoff 500

Allow Statement Caching (clear the check box, which disables statement
caching)

For more information about these parameters, see the webMethods Central
Configuration and Deployment Guide.
12 Click Save.
You are returned to the Database Pool Configuration page.
If you created a new pool, it will not be used unless a database component is mapped to it.
See “To map Metadata Library database components to a database pool” below.
If you changed an existing pool, database components mapped to it will automatically use
the new settings once the configuration is deployed.

To map Metadata Library database components to a database pool

1 Select the Define Environments tab.

2 Under ENVIRONMENT NAME, select Metadata Library Configuration.
3 Select the Map DB Pools tab.

webMethods Metadata Library User’s Guide Version 7.1.1 49

3. Configuring the Metadata Library

4 For the three database components, select the pool you created. See the following
illustration.

Select the pool for

each component

ReasoningDB refers to the Metadata Reasoner database component. RepositoryDB

and SnapshotDB refer to the Metadata Repository database component. These
database components were installed using the DCI scripts when you installed the
Metadata Library.
Typically, the database components are all on the same database and you should
select the same pool for them. However, if the components are on different databases,
select the appropriate pool for each. If you have not created the pools yet see “To edit
or create a database connection pool” on page 46.

Note: Since RepositoryDB and SnapshotDB refer to the same database, you should
select the same pool for both.

5 Click Save.

To delete a database pool

1 Select System-Wide > Environments > Database Pool Configuration.

2 Select the check box for the pool you want to delete.
3 Click Delete Pools.
4 You are asked to confirm you want to delete the pool(s). Click Delete.

webMethods Metadata Library User’s Guide Version 7.1.1 50

3. Configuring the Metadata Library

Validating and Deploying a Configuration

Once you are done making configuration changes, you must validate the configuration
and then deploy it. Validation ensures required settings are in place and that the
configured endpoint maps to a valid Configuration Agent on the Metadata Library.
Deploying the configuration sends it to the Configuration Agent which makes the
changes to the Metadata Library’s configuration.

To validate the configuration

1 Make sure all tabs (except Validate) in the environment have green check marks,
indicating they have been configured. See the following illustration.

2 Select the Validate tab.

The configuration is validated. If it is valid, “Valid Configuration” appears. If not,
“Invalid Configuration” appears and the Configuration Report box lists the problems
found in the configuration. Use this information to correct any problems. You can go
back to any of the tabs and make changes.
3 If the configuration is valid, click Finish.
You are returned to the Define Environments page. Green check marks should appear
under CONFIGURED and READY TO DEPLOY for Metadata Library Configuration.

To deploy the configuration

1 Under ACTIONS, click the (Deploy) icon for Metadata Library Configuration.
2 Click Deploy All.
“Successfully deployed environment” appears.

Note: For more information about deploying a configuration environment, see the
webMethods Central Configuration and Deployment Guide.

3 Click Close.
You are returned to the Define Environments page.
4 Restart the Metadata Library.
The configuration changes do not take effect until the Metadata Library is restarted.
For instructions, see “Restarting the Metadata Library” on page 13.

webMethods Metadata Library User’s Guide Version 7.1.1 51

3. Configuring the Metadata Library

Security
Applications (for example, Designer and Integration Server) must provide a user name
and password to access a Metadata Library. When a user name and password are
supplied to a Metadata Library, it checks whether the user can be authenticated by its
built‐in authentication services.
If the Metadata Library cannot authenticate the user itself, it can be configured to allow a
My webMethods Server to authenticate the user. If the My webMethods Server can
authenticate the user as a valid Metadata Library user, the Metadata Library allows the
application access.
Additionally, SSL (Secure Sockets Layer) can be used for secure communication to and
from the Metadata Library. The Metadata Library can act as either SSL server or client
depending on the situation. For more information, see “Using SSL” on page 57.

Metadata Library Built-In Users

A Metadata Library has two built‐in users: Administrator and Developer. The following
table lists which user various webMethods components log into a Metadata Library as.

Component Logs in as:

Central Configuration Administrator
Designer, Integration Server, Developer
CentraSite Asset Publisher

Note: For better security, it is recommended you change the default passwords for the
built‐in users. See “To change the password for a built‐in user” below.

Important! You can change the passwords of the built‐in users. However, you should not
remove the users.

To change the password for a built-in user

1 On the server running the Metadata Library, log into the Server Administration tool:
a In a Web browser, go to http://localhost:8090/fabric‐admin.
If the Metadata Library is on a different port replace 8090 above with the correct
port number.
b For User Name, type Administrator.

webMethods Metadata Library User’s Guide Version 7.1.1 52

3. Configuring the Metadata Library

c For Password, type the Administrator user’s password (original default is

manage).

Note: The built‐in Administrator user is used to log into the Server Administration
tool. While in the Server Administration tool, if you change Administrator’s
password you will have to supply the new password the next time you log into
the Server Administration tool.

d Click OK.
2 For the user whose password is to be changed, type the new password twice.

Important! Be sure to note the new password you have entered. Do not lose it.

Note: Central Configuration uses the Administrator user to send configuration

changes to the Metadata Library. If you changed Administrator’s password, be sure to
update the Metadata Library configuration environment in Central Configuration
with the new password. See “Configuration Agent” on page 42.

3 Click Save (under the new password you just entered).

4 Close the browser.

Using My webMethods Server to Authenticate Metadata

Library Users
You can configure the Metadata Library to use a My webMethods Server to authenticate
users. Authentication by a My webMethods Server acts as a backup to the Metadata
Library’s own authentication services. If the Metadata Library cannot authenticate a user,
it will ask My webMethods Server to authenticate it.
The Metadata Library always attempts to authenticate a user on its own first. If the same
user name appears in both the Metadata Library and My webMethods Server, the user is
authenticated against the Metadata Library’s version first and if that fails, the user is
authenticated against My webMethods Server.
Different privileges and roles can be granted depending on which version of the user
(Metadata Library or My webMethods Server) is able to be validated. For example, if both
the Metadata Library and My webMethods Server has a Library user named “Developer”
but with different passwords, whichever password is supplied determines whether the
user is granted the privileges and roles of the “Developer” user maintained by the
Metadata Library or by the My webMethods Server.

To use My webMethods Server to authenticate users

webMethods Metadata Library User’s Guide Version 7.1.1 53

3. Configuring the Metadata Library

1 In the Metadata Library Configuration environment, select the Configure Servers tab.
For instructions on accessing the environment, see “Accessing the Configuration
Environment” on page 33.
2 Under CONFIGURATION, expand Medata Library v7.1.0.0.
3 Select Metadata Library Configuration.
4 For MwS Location (Specify to enable MwS authentication), enter the URL of the My
webMethods Server.
By default, this is http://localhost:8585. If the My webMethods Server is running
on another computer, enter that computer’s host name or IP address in place of
“localhost”. If the My webMethods Server is listening to a different port, enter it in
place of “8585”.
If the My webMethods Server requires SSL, enter https instead of http in the MwS
Location (Specify to enable MwS authentication) URL. Also, you must specify a trust store
and password; see step 8 below.
5 For MwS User, type Administrator.
Note that this is the Administrator user on the My webMethods Server and not the
Administrator user built into the Metadata Library.
6 For MwS Password, enter Administrator’s password (default: manage).
7 For Key Store (Specify to enable SSL) and Key Store Password, leave them blank. If Key
Store has a value entered for it, delete it.
8 If the My webMethods Server requires SSL, specify the truststore file in Trust Store
(Specify if accessing MwS via SSL). (If SSL is not required, leave Trust Store blank.)
a

Note: A truststore allows the Metadata Library to verify that it can trust
communication from the My webMethods Server. The truststore file is obtained from
a certificate authority (for example, VeriSign) and installed by your system
administrator.

What you enter in the Trust Store box is interpreted as a relative path off Metadata
Library_directory/library/server/library/conf/. Typically, the trust store file is placed in
the ../conf/security/ directory (in which case you would enter ./security/filename).

Important! You must use Unix path syntax (for example, “/” instead of “\”) in the Trust
Store box even if you are on a Windows system.

9 If you specified a truststore above, for Trust Store Password, enter a password to access
it.
Your system administrator should provide you with this password.

webMethods Metadata Library User’s Guide Version 7.1.1 54

3. Configuring the Metadata Library

10 Click Save.

Note: The password fields might show a different number of mask characters than the
number of actual characters in the password. This is intentionally done to hide the
number of characters in the password.

Using My webMethods Server to Grant Access to the

Metadata Library
In a My webMethods Server you can grant users access to the Metadata Library. For
example, you might want to give each Designer user a unique user name and allow them
access to the Metadata Library.
For a user to have access to the Metadata Library, you must assign it the role LibraryUser.

Note: Use the LibraryUser role to grant Metadata Library access to users when you do not
want them to use the Metadata Library built‐in users. For more information, see
“Metadata Library Built‐In Users” on page 52.

To assign the LibraryUser role to a user

1 Log into My webMethods:

Note: You must log in as Administrator or as a user with administrator privileges. For
more information, see Getting Started with My webMethods or the My webMethods Server
Administrator’s Guide.

2 In the navigation bar, select Administration.

3 Select System-Wide > User Management > Roles.
4 Under ROLE NAME, select LibraryUser.

webMethods Metadata Library User’s Guide Version 7.1.1 55

3. Configuring the Metadata Library

Note: If you do not see the LibraryUser role listed, you must create it. See “To create
the LibraryUser role” below.

5 Click the Members tab.

6 Click Edit Members.
7 Use the Query options to find users:
a (Optional) In Keywords, enter keywords found in the user names you are
interested in. If you want to see all users, leave Keywords blank.
b For Search For, select Users.
c Click Search.
8 Under Available, click each user you want to grant the LibraryUser role to.
Selected users appear under Selected.
9 Click Apply.
10 Click Save.

Note: For more information about users and roles, such as creating users, see the My
webMethods Server Administrator’s Guide.

Note: To configure Designer or Integration Server to use one of the users assigned the
LibraryUser role, see “To configure Designer to Connect to the Metadata Library” on
page 66 or “To configure Integration Server to connect to the Metadata Library” on
page 71.

To create the LibraryUser role

1 Log into My webMethods:

webMethods Metadata Library User’s Guide Version 7.1.1 56

3. Configuring the Metadata Library

b For User Name, type Administrator.

c For Password, enter Administrator’s password (default is manage).
d Click Login.

Note: You must log in as Administrator or as a user with administrator privileges. For
more information, see Getting Started with My webMethods or the My webMethods Server
Administrator’s Guide.

2 In the navigation bar, select Administration.

3 Select System-Wide > User Management > Roles.
4 Click Add Role.
5 For Role Name, type LibraryUser.

6 For Role Provider, click the icon for Static Role Provider.
Static Role Provider appears under Selected Items.
7 Click Create Role.

Using SSL
SSL (Secure Sockets Layer) can be used for secure communication to and from the
Metadata Library. The Metadata Library can act as either SSL server or client depending
on the situation.
The Metadata Library acts as SSL server in these cases:
Designer (client) connects to Metadata Library (server) to read, publish, and
retract metadata.
Integration Server (client) connects to Metadata Library (server) to publish and
retract metadata.
My webMethods Server (client) connects to Metadata Library (server) to send
configuration changes.
The Metadata Library acts as SSL client in these cases:
Metadata Library (client) connects to My webMethods Server (server) for user
authentication.
Metadata Library (client) connects to CentraSite (server) to extract metadata.

webMethods Metadata Library User’s Guide Version 7.1.1 57

3. Configuring the Metadata Library

Enabling the Metadata Library to use SSL

For the Metadata Library to use SSL, it must have a keystore to act as SSL server and a
truststore to act as SSL client. The keystore is an encrypted file, residing on the server,
containing public and private keys. The truststore is a file, residing on the client,
containing the certificates of servers that can be trusted by the client.
Your system administrator should obtain a certificate from a certificate authority, such as
VeriSign, and generate keystore and truststore files with it. You will need:
Certificate file
Keystore file and password
Truststore file and password

Note: Inform your system administrator that the keystore must be generated using the
RSA algorithm. Also, the keystore file must be in the *.jks or *.p12 format.

Alternatively, but not generally recommended, you can generate a keystore and truststore
yourself with a self‐signed certificate. For more information, see “To generate a self‐signed
keystore and truststore” on page 65.

To enable the Metadata Library to use SSL

1 If the Metadata Library is running, stop it.

For instructions, see “Starting and Stopping the Metadata Library” on page 11.
2 Place the certificate, keystore, and truststore files supplied by your system
administrator in the following folder or directory:
Metadata Library_directory\library\server\library\conf\security

Note: If you chose to generate self‐signed certificate, keystore, and truststore files,
place them in this folder or directory.

3 Start the Metadata Library.

For instructions, see “Starting and Stopping the Metadata Library” on page 11.

Note: The Metadata Library is now able to use SSL, however you must still configure it for
the particular scenarios in which it will be used (that is, as SSL server and/or client). See
the procedures below.

webMethods Metadata Library User’s Guide Version 7.1.1 58

3. Configuring the Metadata Library

To enable the Metadata Library as an SSL server or client

Complete these steps to enable the Metadata Library to act as:

SSL server to Designer or Integration Server.
SSL server to My webMethods Server (for configuration changes)
SSL client to My webMethods Server (for user authentication).
SSL client to CentraSite.
When following these steps you will be given the option to enable any or all of the above.
1 If it is not already running, start the Metadata Library.
For instructions, see “Starting and Stopping the Metadata Library” on page 11.
2 Log into My webMethods:
a In a Web browser, go to http://localhost:8585.
If you are not on the computer that is running the My webMethods Server,
replace localhost with the host name or IP of the computer it is running on. If it
is not listening to port 8585, enter the correct port instead.
b For User Name, type Administrator.
c For Password, enter Administrator’s password (default is manage).
d Click Login.

Note: You must log in as Administrator or as a user with administrator privileges. For
more information, see Getting Started with My webMethods or the My webMethods Server
Administrator’s Guide.

3 In the navigation bar, select Administration.

4 Select System-Wide > Environments > Define Environments.
5 Under ENVIRONMENT NAME, select Metadata Library Configuration.

Note: “Metadata Library Configuration” is the recommended name for the

webMethods Metadata Library User’s Guide Version 7.1.1 59

3. Configuring the Metadata Library

6 In the Metadata Library Configuration environment, select the Configure Servers tab.
7 Under CONFIGURATION, expand Medata Library v7.1.0.0.
8 Select Metadata Library Configuration.
9 To enable the Metadata Library to act as an SSL server:

Note: Completing this step allows Designer or Integration Server to securely

communicate with the Metadata Library. If you do not want to enable the Metadata
Library to act as SSL server, leave Key Store (Specify to enable SSL) and Key Store
Password blank and skip to step 11.

a In the Key Store (specify to enable SSL) box, enter the location of the keystore file.
What you enter in this box is interpreted as a relative path off Metadata
Library_directory/library/server/library/conf/. Typically, the keystore file is placed
in the ../conf/security directory (in which case you would enter
/security/filename on a Windows system or./security/filename on a Unix‐
based system, where filename is the name of the keystore file).

Important! You must use Unix path syntax (for example, “/” instead of “\”) in the
this box even if you are on a Windows system.

b For Key Store Password, enter the password for the keystore file you specified
above.

c Click Save.

webMethods Metadata Library User’s Guide Version 7.1.1 60

3. Configuring the Metadata Library

10 If you enabled the Metadata Library to act as SSL server in the preceding step, you
must configure My webMethods Server to connect to the Metadata Library as an SSL
client:

Note: This is necessary for Central Configuration to send configuration changes to the
Metadata Library. The Metadata Library does not support running in both SSL and
non‐SSL at the same time. If it is set up to act as an SSL server, any connections to it,
including from Central Configuration, must use SSL.

a Leave My webMethods running (that is, keep the browser open).

b Use the Java keytool utility to import the Metadata Library’s certificate into the
My webMethods Server’s truststore:
1 Copy the Metadata Library’s certificate file to
My_webMethods_directory\server\default\config\glue
where My_webMethods_directory is where My webMethods Server is installed.
2 In a command prompt or console, navigate to
My_webMethods_directory\server\default\config\glue
3 Execute the command:
keytool -keystore glueTrustStore.jks -import -alias serverkeys
-file certificate
where certificate is the file name of the Metadata Library’s certificate, for
example, server.cer.
4 When prompted, enter the password for My webMethods Server’s truststore
(supplied by your system administrator; default password is manage).
c Return to My webMethods.
d Configure the connection to Configuration Agent to use SSL:
1 In the Metadata Library Configuration environment, click the Map Endpoints
tab.
2 For the Configuration Agent, under INCOMING CONNECTIONS, change the
protocol from http to https.
3 Click Save.

webMethods Metadata Library User’s Guide Version 7.1.1 61

3. Configuring the Metadata Library

11 To enable the Metadata Library to act as an SSL client to My webMethods Server:

Note: Completing this step allows the Metadata Library to securely connect to My
webMethods Server for user authentication (for more information, see “Using My
webMethods Server to Authenticate Metadata Library Users” on page 53). If you do
not want to enable the Metadata Library to act as SSL client to My webMethods
Server, leave Trust Store (Specify if accessing MwS via SSL) and Trust Store Password blank
and skip to step 12.

a Use the Java keytool utility to import My webMethods Server’s certificate into the
Metadata Library’s truststore:
1 Obtain a certificate file from your system administrator for My webMethods
Server.
2 Copy the My webMethods Server certificate file to
Metadata Library_directory\library\server\library\conf\security\
3 In a command prompt or console, navigate to Metadata
Library_directory\library\server\library\conf\security\
4 Execute the command:
keytool -keystore truststore -import -alias serverkeys
-file certificate

where truststore is the Metadata Library’s truststore file and certificate is My

webMethods Server’s certificate file.
5 When prompted, enter the password for Metadata Library’s truststore
(supplied by your system administrator).
b Return to My webMethods.
c In the Trust Store (Specify if accessing MwS via SSL) box, enter the location of the
truststore file.
What you enter in this box is interpreted as a relative path off Metadata
Library_directory/library/server/library/conf/. Typically, the truststore file is placed
in the ../conf/security directory (in which case you would enter
/security/filename on a Windows system or./security/filename on a Unix‐
based system, where filename is the name of the truststore file).

Important! You must use Unix path syntax (for example, “/” instead of “\”) in the
this box even if you are on a Windows system.

webMethods Metadata Library User’s Guide Version 7.1.1 62

3. Configuring the Metadata Library

d For Trust Store Password, enter the password for the truststore file you specified
above.

e Click Save.
12 To enable the Metadata Library to act as SSL client to CentraSite:

Note: Completing this step allows the Metadata Library to securely connect to
CentraSite to extract metadata from it. If you do not want to enable the Metadata
Library to act as SSL client to CentraSite, skip to step 10 now.

a Use the Java keytool utility to import CentraSite’s certificate into the Metadata
Library’s truststore:
1 Obtain a certificate file from your system administrator for CentraSite.
2 Copy the CentraSite certificate file to
Metadata Library_directory\library\server\library\conf\security\
3 In a command prompt or console, navigate to Metadata
Library_directory\library\server\library\conf\security\
4 Execute the command:
keytool -keystore truststore -import -alias serverkeys
-file certificate

where truststore is the Metadata Library’s truststore file and certificate is

CentraSite’s certificate file.
5 When prompted, enter the password for Metadata Library’s truststore.
b Return to My webMethods.

webMethods Metadata Library User’s Guide Version 7.1.1 63

3. Configuring the Metadata Library

c Edit the protocol prefix to https for each of the following:

Registry Security URL
Registry Inquiry URL
Registry Publish URL
Registry Taxonomy URL
Registry Subscription URL
For example, Registry Security URL should read:
https://localhost:2020/registry/uddi/security
(if CentraSite is running on localhost, port 2020).

Note: Do not change anything else in these URLs.

Note: If Registry User is empty, metadata extraction from CentraSite is disabled. To

enable it, enter [email protected] as the user and manage as the
Registry Password. For more information, see “CentraSite Asset Publisher” on
page 34.

d Click Save.
13 Restart the Metadata Library.
For instructions, see “Restarting the Metadata Library” on page 13.
14 You are done enabling the Metadata Library as SSL server and/or client.
If you enabled the Metadata Library as an SSL server, be sure to enable Designer and
Integration Server to connect to it using SSL. See “To enable Designer to connect to the
Metadata Library using SSL” below and “To enable Integration Server to connect to
the Metadata Library using SSL” on page 65.

To enable Designer to connect to the Metadata Library using SSL

1 Copy the Metadata Library’s truststore file to the folder or directory in which
Designer is installed (by default C:\webMethods7\Designer in Windows).
This is the recommended location. However, the file can be placed anywhere.
2 Start Designer.
3 Select Window > Preferences > webMethods > Metadata Library.
4 Select Use SSL.
5 Click the Browse next to the Truststore File box.

webMethods Metadata Library User’s Guide Version 7.1.1 64

3. Configuring the Metadata Library

6 Navigate to the location of the truststore file you chose in step 1 and click Open.
7 For Truststore Password, enter the password for the truststore file (provided by your
system administrator).
8 Click Test Connection.
“Success!” should appear.

To enable Integration Server to connect to the Metadata Library using SSL

1 Copy the Metadata Library’s certificate file to

webMethods_directory\jvm\win150\jre\lilb\security\cacerts
2 Using the Java keytool utility to import the Metadata Library’s certificate into the
webMethods JDK’s truststore:
a Execute the command:
keytool -keystore cacerts -import -alias serverkeys -file certificate
where certificate is the file name of the Metadata Library’s certificate, for example,
server.cer.
b When prompted, enter the password for the JDK’s truststore (supplied by your
system administrator).

Note: If you have configured Integration Server to use another JDK instead of
webMethod’s default one, import the certificate into that JDK’s truststore.

3 Configure the Integration Server Asset Publisher to use SSL by changing the protocol
to HTTPS on it configuration page in the Integration Server Administrator.
See “Configuring Integration Server to Connect to the Metadata Library” on page 71.

To generate a self-signed keystore and truststore

These instructions are provided in case you want you create a self‐signed certificate and
generate a keystore and truststore from it. It is recommended, however, that you obtain a
certificate from a certificate authority (like VeriSign) rather than self‐sign one.
These steps use the Java keytool utility which should be installed on your system as part
of the JDK.
1 In a command prompt or console, generate a keystore by executing the command:
keytool -genkey -keyalg RSA -alias serverkeys -keystore server.jks -
storepass password -storetype jks -keypass password -dname CN=MDL,
O=webMethods Inc

2 Generate a self‐sign certificate by executing the command:

keytool -selfcert -alias serverkeys -keystore server.jks -storepass
password -storetype jks -keypass password

webMethods Metadata Library User’s Guide Version 7.1.1 65

3. Configuring the Metadata Library

3 Export the certificate by executing the command:

keytool -export -alias serverkeys -keystore server.jks -storepass
password -file server.cer

4 Generate a truststore that trusts the certificate by executing the command:

keytool -import -alias serverkeys -v -trustcacerts -keystore trust.jks
-storepass password -storetype jks -file server.cer

Configuring Designer to Connect to the Metadata Library

Typically, Designer should connect to the Metadata Library using the Developer user
name. How Designer connects to the Metadata Library is specified in the Metadata
Library section of Designer Preferences.

To configure Designer to Connect to the Metadata Library

1 In Designer, select Window > Preferences.

2 In the tree, expand webMethods and select Metadata Library.
3 If Disable Metadata Library Connection is selected, clear its check box.
4 The following table describes the options to be set.

For this option... Specify...

Host Host name or IP address of the server that hosts the Metadata
Library. Do not include the protocol prefix (for example,
“http://”).
Port Port number on which the Metadata Library listens for
incoming requests from. The Metadata Library is initially
configured to listen to 8090 by default.
User name Enter the name of a user authorized to access the Metadata
Library. Typically, you should enter Developer which is a
default user name built into the Metadata Library.
Password Enter the password the user specified above. The initial,
default password for Developer is develop.

Note: If you want to use SSL to connect to the Metadata Library, see “To enable
Designer to connect to the Metadata Library using SSL” on page 64.

5 Click Test Connection.

“Success!” should appear.
6 Click OK.

webMethods Metadata Library User’s Guide Version 7.1.1 66

3. Configuring the Metadata Library

Enabling CentraSite Metadata Extraction without Using Central

Configuration
Typically, you will use Central Configuration to enable metadata extraction from
CentraSite (see “CentraSite Asset Publisher” on page 34). However, it is possible to do so
outside of Central Configuration. Complete these steps if you want to enable metadata
extraction from CentraSite without using Central Configuration.

To enable metadata extraction from CentraSite without using Central Configuration

1 Open the following file for editing:

Metadata Library_directory\library\server\library\conf\uddi\
uddiextractor‐configuration.xml
2 Edit the following element in the file:
<entry key="webmethods.uddi.registry.login.id" type="String">
<rendering-properties>
<property name="type" value="textfield"/>
<property name="label" value="Registry User"/>
<property name="size" value="55"/>
</rendering-properties>
<value>[email protected]</value>
</entry>

In the <value></value> element, enter

[email protected] as shown here.
This specifies the CentraSite user.

3 Save and close the file.

4 Restart the Metadata Library.
See “Restarting the Metadata Library” on page 13.

Note: The password for the CentraSite user can be modified by using Metadata Library’s
Server Administration tool. See “To change the password for a built‐in user” on page 52.

Note: To disable metadata extraction from CentraSite, reverse the action you took in the
procedure above: remove the user name you entered in the <value></value> element. That
is, the line should read <value></value> with nothing in between the tags.

webMethods Metadata Library User’s Guide Version 7.1.1 67

3. Configuring the Metadata Library

webMethods Metadata Library User’s Guide Version 7.1.1 68

Chapter 4. Using the Metadata Library in Integration Server

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Starting the Integration Server Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Accessing Asset Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuring Integration Server to Connect to the Metadata Library . . . . . . . . . . . . . . . . . . . . . . 71

Selecting Assets for Metadata Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Deselecting Assets for Metadata Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Publishing Metadata to the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Retracting an Asset’s Metadata from the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

WmAssetPublisher.pub.asset:publish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

webMethods Metadata Library User’s Guide Version 7.1.1 69

4. Using the Metadata Library in Integration Server

Introduction
Integration Server can extract and publish metadata about user‐selected integration assets
to the Metadata Library.
These assets include most Integration Server namespace assets as well as webMethods
Trading Networks Document Types and Partner Profiles.
The extraction and publication of Integration Server and Trading Networks metadata is
performed by the Integration Server Asset Publisher, which is provided by the
WmAssetPublisher package. Using Integration Server Asset Publisher, you configure the
connection from Integration Server to the Metadata Library, select the assets whose
metadata you intend to publish, and perform manual publish operations. Once
configured, you can schedule public services to perform regular incremental publish or
retract operations.
For Integration server assets, the unit of publishing is the package. The first time a
package’s metadata is published, a complete publish of all its metadata is performed. In
subsequent publishes, only metadata that has changed is published.

Starting the Integration Server Administrator

You will use the Integration Server Administrator to publish package metadata. Almost
all of the procedures in this chapter are performed in the Integration Server
Administrator.
It is assumed the Integration Server is already running. For more information about
Integration Server and Integration Server Administrator, see the webMethods Integration
Server Administrator’s Guide.

To start the Integration Server Administrator

1 Start your browser.

2 Point your browser to the host and port where the Integration Server is running.
Examples
If the server were running on the default port on the same machine where you are
running the Integration Server Administrator, you would type:
http://localhost:5555

If the server were running on port 4040 on a machine called QUICKSILVER, you
would type:
http://QUICKSILVER:4040

webMethods Metadata Library User’s Guide Version 7.1.1 70

4. Using the Metadata Library in Integration Server

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

Important! Use the exact combination of upper‐ and lowercase characters shown
above; user names and passwords are case sensitive.

Accessing Asset Publisher

To access Asset Publisher, select Solutions > Asset Publisher from the main navigation panel
of the Integration Server Administrator.

Note: If you do not see Asset Publisher under Solutions, it might not be enabled. To enable it,
see “To enable Asset Publisher” below.

To enable Asset Publisher

1 Start the Integration Server Administrator if it is not already running.

For instructions, see “Starting the Integration Server Administrator” on page 70.
2 In the Packages menu of the Navigation panel, click Management.
3 In the Package List, find WmAssetPublisher.
4 For WmAssetPublisher, in the Enabled column, click the “No” link.
5 When you are asked if it is OK to enable the WmAssetPublisher package, click OK.
“WmAssetPublisher package enabled” appears at the top of the page.

Configuring Integration Server to Connect to the Metadata

Library

To configure Integration Server to connect to the Metadata Library

1 Start the Integration Server Administrator if it is not already running.

For instructions, see “Starting the Integration Server Administrator” on page 70.
2 In the Solutions menu of the Navigation panel, click Asset Publisher.

webMethods Metadata Library User’s Guide Version 7.1.1 71

4. Using the Metadata Library in Integration Server

3 Click Configuration.
4 Click Edit Configuration.
5 Enter the following information:

For this
parameter... Specify...
IS Host Name A name you assign to this Integration Server to identify it to
Designer. The default name is IntegrationServer.
Protocol Communication protocol. HTTP is the default. If you want to
use SSL to connect to the Metadata Library, select HTTPS.
Note: To use SSL, the Integration Server must be properly
configured so its truststore contains the Metadata Library’s
certificate. For more information, see “Using SSL” on page 57.
Host Host name or IP address of the server that hosts the Metadata
Library.
Port Port number on which the Metadata Library listens for
incoming requests from this Integration Server. The Metadata
Library is initially configured to listen to 8090 by default.

Note: You can find which port is currently used by the

Metadata Library by viewing the following file (on the
Metadata host server): Metadata Library_directory\library\
server\library\deploy\fabric‐tomcat.sar\server.xml.
In that file, the port attribute of the Connector element
specifies the port number.

User Name The name of the user account on the Metadata Library that
will be used for publishing and retracting metadata.
The default user name is Developer.
Password Password for User Name.
The default password is develop.

Note: Your webMethods system administrator might have

changed the Developer user’s password. For more
information, see “To change the password for a built‐in user”
on page 52.

6 Click Save Changes.

webMethods Metadata Library User’s Guide Version 7.1.1 72

4. Using the Metadata Library in Integration Server

Selecting Assets for Metadata Publishing

Before you can publish metadata to the Metadata Library, you must first identify
publishable assets. Publishable assets are those packages you want to publish metadata
about to the Metadata Library. You select from a list of packages on your Integration
Server.
If you have already identified publishable assets, you can proceed to “Publishing
Metadata to the Metadata Library” on page 74.

Note: If you perform publish operations by calling the pub.asset:publish service from a flow
service, you must still select packages in the Asset Selection and Publish screens, which
are described in this section and in “Publishing Metadata to the Metadata Library”. For
instructions on using the pub.asset:publish service to publish metadata, see
“WmAssetPublisher.pub.asset:publish” on page 78

To select assets for metadata publishing

1 Start the Integration Server Administrator if it is not already running.

For instructions, see “Starting the Integration Server Administrator” on page 70.
2 In the Solutions menu of the Navigation panel, click Asset Publisher.
3 Click Asset Selection.
Integration Server displays a list of all packages on this Integration Server. Any assets
you previously selected on this page will be displayed with a green check mark.
4 Click Edit Assets.
a If you want Integration Server to publish metadata for Trading Networks
Document Types and Partner Profiles, check the box to the left of Trading Networks
Assets.
b If you want Integration Server to publish metadata for new packages, click New
Packages. New packages are those that were added to Integration Server since the
last publish. Integration Server will automatically look for new packages and
display them in this list the next time you view this screen.
c Check the box to the left of each package you want to mark as a publishable asset.
5 Click Save.
The selections you make on this screen will be reflected in the Selected Assets list on
the Publish screen the next time you display it.
Now that you have identified publishable assets, you can publish their associated
metadata. For instructions, see “Publishing Metadata to the Metadata Library” on
page 74.

webMethods Metadata Library User’s Guide Version 7.1.1 73

4. Using the Metadata Library in Integration Server

Deselecting Assets for Metadata Publishing

Deselecting an asset removes it from the list of publishable assets, thereby preventing
publication of the asset’s metadata in the next publish operation.

Note: Deselection does not delete an asset’s metadata from the Metadata Library. For
instructions on deleting an asset’s metadata, see “Retracting an Asset’s Metadata from the
Metadata Library” on page 77.

To deselect an asset from metadata publishing

1 Start the Integration Server Administrator if it is not already running.

Publishing Metadata to the Metadata Library

The publish operation writes metadata to the Metadata Library. Before publishing
metadata, you must select the assets whose metadata you want to publish. For
instructions on selecting assets for metadata publishing, see “Selecting Assets for
Metadata Publishing” on page 73.
The first time metadata is published for an asset or package, all of its metadata is
published. Subsequent publishes only involve changes that have occurred since the last
publish operation. In other words, an initial publish of metadata for an asset or package is
a complete publish; subsequent publishes are incremental.

Note: The first time metadata is published for assets and packages, it might take
substantial time and computer memory. You can schedule publish operations to run at
off‐peak hours or at regular intervals. For instructions on scheduling jobs, see “Scheduling
Metadata Publish Operations” on page 76.

webMethods Metadata Library User’s Guide Version 7.1.1 74

4. Using the Metadata Library in Integration Server

Note: If you perform publish operations by calling the pub.asset:publish service from a flow
service, you must still select packages in the Asset Selection and Publish screens, which
are described in this section and in “Selecting Assets for Metadata Publishing” on page 73.
For instructions on using the pub.asset:publish service to publish metadata, see
“WmAssetPublisher.pub.asset:publish” on page 78

To publish metadata

1 Start the Integration Server Administrator if it is not already running.

Note: To see which assets had metadata published during the last publish operation,
click Latest Publish. For more information, see “To view information about the last
metadata publish operation” on page 76.

Integration Server displays a list of assets that were previously checked on the Asset
Selection screen. Packages disabled in the Integration Server are not displayed.
4 Select assets and packages:
If you selected Trading Network assets for metadata publishing, Doc Types, Partner
Profiles appear under Selected Trading Networks Assets. To publish metadata about these
assets, check the box to the right of Doc Types, Partner Profiles.
Under Selected Integration Server Packages, check the box to the right of each package
for which you want to publish metadata.

Note: If you do not see the assets or packages you want to publish metadata about, be
sure they have been selected for metadata publishing. See “Selecting Assets for
Metadata Publishing” on page 73.

5 Click Publish.
The Published Metadata screen appears. The Published Details section shows the status
(Status), number of assets being published (Assets), and elapsed time of the entire
publishing operation (Duration).
Below the Published Details section, the publishing status of individual packages or
Trading Network assets (TN Assets) is shown.
You can leave the Published Metadata screen at any time, even if the publish operation is
not complete. The publish operation will continue. You can check the status of the

webMethods Metadata Library User’s Guide Version 7.1.1 75

4. Using the Metadata Library in Integration Server

publish operation by returning to the Published Metadata screen. To return to this

screen, on the Publish screen, click Latest Publish. For more information, see “To view
information about the last metadata publish operation” on page 76.

Important! If you are using Internet Explorer, on the Internet Explorer menu: Tools >
Internet Options > General tab. Under Temporary Internet Files, click Settings. Under Check
for Newer Versions of Stored Pages, select Every visit to the page. If you do not adjust these
settings, the Published Metadata screen will not update the status of the publish
operation correctly.

To view information about the last metadata publish operation

1 Start the Integration Server Administrator if it is not already running.

For instructions, see “Starting the Integration Server Administrator” on page 70.
2 In the Solutions menu of the Navigation panel, click Asset Publisher.
3 On the Asset Publisher menu, click Publish.
The Publish screen appears.
4 Click Latest Publish.
The Published Metadata screen appears. This screen shows information about the last
publish operation. If a current publish operation is being performed, this screen
shows its progress.
The Published Details section shows the status (Status), number of assets published
(Assets), and elapsed time of the entire publishing operation (Duration).
Below the Published Details section, the publishing status of individual packages or
Trading Network assets (TN Assets) is shown.

Scheduling Metadata Publish Operations

An initial publish operation can consume substantial amounts of time and computer
memory. For this reason, consider scheduling them to run at off‐peak hours. In addition,
you can schedule subsequent, incremental publish operations to run automatically on a
regular basis.
To schedule a metadata publish operation, you must write a service that calls the
pub.asset:publish built‐in service, which is documented in
“WmAssetPublisher.pub.asset:publish” on page 78. This service takes as input a list of
assets for which you want to publish metadata.

webMethods Metadata Library User’s Guide Version 7.1.1 76

4. Using the Metadata Library in Integration Server

After you write your service, you can schedule it to run using the scheduling facility in
Integration Server Administrator. To prevent one publish operation from beginning
before the previous one has completed, be sure to select the Repeat from End of Invocation
option when scheduling the job. For more information about scheduling services to run,
see the “Managing Services” chapter in the webMethods Integration Server Administrator’s
Guide.

Retracting an Asset’s Metadata from the Metadata Library

The retract operation removes an asset’s metadata from the Metadata Library.

Note: The retract operation does not prevent the asset’s metadata from being published
during the next publish operation. To prevent the metadata from being published again,
see “Deselecting Assets for Metadata Publishing” on page 74.

Note: If a package’s metadata has been published to the Metadata Library and that package
is later removed from the Integration Server, its metadata still remains in the Metadata
Library. To remove the metadata from the Metadata Library, you must retract it even
though the package no longer exists in the Integration Server.

To retract an asset’s metadata from the Metadata Library

1 Start the Integration Server Administrator if it is not already running.

For instructions, see “Starting the Integration Server Administrator” on page 70.
2 In the Solutions menu of the Navigation panel, click Asset Publisher.
3 On the Asset Publisher menu, click Retract.
Integration Server displays a list of assets whose metadata currently exists in the
Metadata Library.
4 In the list of Published Integration Server Packages and Published Trading Networks
Assets, click the box to the right of each asset whose metadata you want to retract.
5 Click Retract.
The Retracted Assets screen appears. The Retract Details section shows the status (Status)
and elapsed time of the entire retract operation (Duration).
Below the Retract Details section, the retracting status of individual packages or
Trading Network assets (TN Assets) is shown.
You can leave the Retracted Assets screen at any time, even if the retract operation is
not complete. The retract operation will continue. You can check the status of the
retract operation by returning to the Retracted Assets screen. To return to this screen,

webMethods Metadata Library User’s Guide Version 7.1.1 77

4. Using the Metadata Library in Integration Server

on the Retract screen, click Latest Retract. For more information, see “To view
information about the last metadata retract operation” on page 78.

Important! If you are using Internet Explorer, on the Internet Explorer menu: Tools >
Internet Options > General tab. Under Temporary Internet Files, click Settings. Under Check
for Newer Versions of Stored Pages, select Every visit to the page. If you do not adjust these
settings, the Retracted Assets screen will not update the status of the retract operation
correctly.

To view information about the last metadata retract operation

1 Start the Integration Server Administrator if it is not already running.

For instructions, see “Starting the Integration Server Administrator” on page 70.
2 In the Solutions menu of the Navigation panel, click Asset Publisher.
The Asset Publisher > Publish screen appears.
3 On the Asset Publisher menu, click Retract.
4 Click Latest Publish.
The Retracted Assets screen appears. The Retract Details section shows the status (Status)
and elapsed time of the entire retract operation (Duration).
Below the Retract Details section, the retracting status of individual packages or
Trading Network assets (TN Assets) is shown.

WmAssetPublisher.pub.asset:publish
In addition to the Integration Server Administrator screens that allow you to configure
Integration Server to connect to the Metadata Library and to manage the publishing of
metadata, the WmAssetPublisher package provides a built‐in service that you can use to
automate metadata publishing operations. Use this service, instead of the Integration
Server Administrator, if you want to schedule publish operations. For more information
about this service, see the webMethods Integration Server Built‐In Services Reference.

Note: Before you can use this service, you must configure Integration Server to connect to
the Metadata Library; see the instructions in “Configuring Integration Server to Connect
to the Metadata Library” on page 71.

webMethods Metadata Library User’s Guide Version 7.1.1 78

DemoMaint Guide
No ratings yet
DemoMaint Guide
550 pages
SAP GRC - Post Installation Guide
No ratings yet
SAP GRC - Post Installation Guide
42 pages
QM Functions in Detail
75% (4)
QM Functions in Detail
91 pages
6-5-1 Webmethods Error Message Reference PDF
No ratings yet
6-5-1 Webmethods Error Message Reference PDF
1,020 pages
Metadata Manager Guide
No ratings yet
Metadata Manager Guide
140 pages
Webmethods Trading Networks Concepts Guide - Software AG PDF
No ratings yet
Webmethods Trading Networks Concepts Guide - Software AG PDF
124 pages
Tad 4 Z
No ratings yet
Tad 4 Z
212 pages
Developer Flat File Schema Developer's Guide: Title Page
50% (2)
Developer Flat File Schema Developer's Guide: Title Page
148 pages
Web Methods Integration Server JMS Client Developer's Guide 7.1
100% (2)
Web Methods Integration Server JMS Client Developer's Guide 7.1
122 pages
Webmethods Release Notes
No ratings yet
Webmethods Release Notes
36 pages
WebMethods Trading Networks Built-In Services Reference TNNN
0% (1)
WebMethods Trading Networks Built-In Services Reference TNNN
296 pages
WebMethods Trading Networks Administrator's Guide - Software AG ...
No ratings yet
WebMethods Trading Networks Administrator's Guide - Software AG ...
616 pages
Broker Admin Guide
100% (1)
Broker Admin Guide
248 pages
PL1 and DB2
No ratings yet
PL1 and DB2
17 pages
6-5-SP1 SAP Adapter Users Guide
No ratings yet
6-5-SP1 SAP Adapter Users Guide
320 pages
WebMethods SOAP Developer's Guide - Software AG Documentation
100% (1)
WebMethods SOAP Developer's Guide - Software AG Documentation
154 pages
Web Services Developers Guide
No ratings yet
Web Services Developers Guide
84 pages
DB2 Hadr
100% (1)
DB2 Hadr
35 pages
9-12 Web Services Developers Guide PDF
No ratings yet
9-12 Web Services Developers Guide PDF
358 pages
Webload Ide Guide
No ratings yet
Webload Ide Guide
294 pages
Webmethods Integration Server JMS Client Developer's Guide PDF
No ratings yet
Webmethods Integration Server JMS Client Developer's Guide PDF
122 pages
Guide To Downloading and Installing The Webmethods Free Trial Version
No ratings yet
Guide To Downloading and Installing The Webmethods Free Trial Version
13 pages
9-9 Integration Server Built in Services Reference PDF
No ratings yet
9-9 Integration Server Built in Services Reference PDF
1,100 pages
Configuring The MDM Administration Cockpit
No ratings yet
Configuring The MDM Administration Cockpit
30 pages
7-1 Getting Started With My WebMethods
No ratings yet
7-1 Getting Started With My WebMethods
75 pages
Peachtree
No ratings yet
Peachtree
354 pages
WebMethods Logging Guide 7.1 - Software AG Documentation
No ratings yet
WebMethods Logging Guide 7.1 - Software AG Documentation
54 pages
MM10.1 201608 SG
No ratings yet
MM10.1 201608 SG
189 pages
WebMethods Monitor User's Guide
No ratings yet
WebMethods Monitor User's Guide
142 pages
WebMethods Developer User's Guide - Software AG Documentation
50% (2)
WebMethods Developer User's Guide - Software AG Documentation
516 pages
9-8 Web Services Developers Guide
No ratings yet
9-8 Web Services Developers Guide
354 pages
7-1 Getting Started With Business Process Management
No ratings yet
7-1 Getting Started With Business Process Management
114 pages
p072 Sysmac Catalogue en
No ratings yet
p072 Sysmac Catalogue en
418 pages
XML Services Developer's Guide 7.1
No ratings yet
XML Services Developer's Guide 7.1
80 pages
SAP Functional Overview
100% (4)
SAP Functional Overview
18 pages
Web Services Developers Guide
No ratings yet
Web Services Developers Guide
350 pages
Business Analyst Resume
No ratings yet
Business Analyst Resume
5 pages
7 (1) 1architecture
No ratings yet
7 (1) 1architecture
26 pages
SAP Business One
100% (3)
SAP Business One
16 pages
9-12 Monitor Users Guide
No ratings yet
9-12 Monitor Users Guide
140 pages
MM10.1 201608 LG
No ratings yet
MM10.1 201608 LG
68 pages
Diff7 1vs6x PDF
No ratings yet
Diff7 1vs6x PDF
228 pages
Mahmoud Yassin Ali Moustafa
No ratings yet
Mahmoud Yassin Ali Moustafa
31 pages
10-5 Trading Networks Users Guide
No ratings yet
10-5 Trading Networks Users Guide
48 pages
Sap Netweaver® 7.0: Master Guide
No ratings yet
Sap Netweaver® 7.0: Master Guide
182 pages
RIA Tutorial
No ratings yet
RIA Tutorial
125 pages
Webmethods6 Introduction
No ratings yet
Webmethods6 Introduction
26 pages
xPM40 UpgrMasterGuideSP10
No ratings yet
xPM40 UpgrMasterGuideSP10
51 pages
Deep Security WebService SDK
No ratings yet
Deep Security WebService SDK
163 pages
WebMethods Deployer User's Guide 7.0 - Software AG Documentation
No ratings yet
WebMethods Deployer User's Guide 7.0 - Software AG Documentation
88 pages
Say What (Bind DBRM Package Plan)
100% (2)
Say What (Bind DBRM Package Plan)
11 pages
Web Services Developers Guide PDF
No ratings yet
Web Services Developers Guide PDF
84 pages
9-12 Trading Networks Users Guide
No ratings yet
9-12 Trading Networks Users Guide
40 pages
DB2 LUW For The Oracle DBA
No ratings yet
DB2 LUW For The Oracle DBA
46 pages
Abdul Mateen: More Than 10 Years of Software Development & Teaching Experience
No ratings yet
Abdul Mateen: More Than 10 Years of Software Development & Teaching Experience
4 pages
WebMethods Metadata Library - Software AG Documentation
No ratings yet
WebMethods Metadata Library - Software AG Documentation
70 pages
Ibm Webmethods Integration
No ratings yet
Ibm Webmethods Integration
3 pages
9-6 Working With Java Service Wrapper
No ratings yet
9-6 Working With Java Service Wrapper
18 pages
Enterprise Service
No ratings yet
Enterprise Service
14 pages
SAP Valid - Cert - Exams - 17 - 10 - 16
No ratings yet
SAP Valid - Cert - Exams - 17 - 10 - 16
8 pages
MetaQuery User Guide
No ratings yet
MetaQuery User Guide
15 pages
292618-Macromedia Flash MX 2004 Data Tutorials.2004.Macromedia
No ratings yet
292618-Macromedia Flash MX 2004 Data Tutorials.2004.Macromedia
20 pages
Web Services Integration
No ratings yet
Web Services Integration
3 pages
Comparison of Different SQL Implementations
No ratings yet
Comparison of Different SQL Implementations
25 pages
Qload
No ratings yet
Qload
24 pages
Web Services Assignment 221501174
No ratings yet
Web Services Assignment 221501174
4 pages
Best Practices For Deployment Planning
No ratings yet
Best Practices For Deployment Planning
27 pages
EBF Overview en
No ratings yet
EBF Overview en
30 pages
SAP NetWeaver - Introduction
No ratings yet
SAP NetWeaver - Introduction
4 pages
Rohit Mandge Resume
No ratings yet
Rohit Mandge Resume
2 pages
Senior COBOL Programmer Analyst in NYC Resume Leslie Hornstein
No ratings yet
Senior COBOL Programmer Analyst in NYC Resume Leslie Hornstein
2 pages
HTTP WWW - Saptechnical.com Tutorials Workflow WFTransactions1
No ratings yet
HTTP WWW - Saptechnical.com Tutorials Workflow WFTransactions1
2 pages
HTTP WWW - Saptechnical.com Tutorials Workflow WFTransactions2 PDF
No ratings yet
HTTP WWW - Saptechnical.com Tutorials Workflow WFTransactions2 PDF
2 pages
Usersguide-7 1 3 PDF
No ratings yet
Usersguide-7 1 3 PDF
994 pages
SQL For The System Administrator
No ratings yet
SQL For The System Administrator
71 pages
CV Ashmawy Mam
No ratings yet
CV Ashmawy Mam
13 pages
1 Vitaly Danilchenko 2023 Aug (CAI)
No ratings yet
1 Vitaly Danilchenko 2023 Aug (CAI)
4 pages
Qlik Odbc Connector Package
No ratings yet
Qlik Odbc Connector Package
10 pages
Rzahfpdf
No ratings yet
Rzahfpdf
34 pages
Biodun Oluwole - Business Analyst - Jconnect Infotech.
No ratings yet
Biodun Oluwole - Business Analyst - Jconnect Infotech.
9 pages
Enterprise Manager Release Notes
No ratings yet
Enterprise Manager Release Notes
5 pages
232 ERP605 Process Overview en
No ratings yet
232 ERP605 Process Overview en
7 pages
(FREE PDF Sample) IBM Certification Study Guide AIX Performance and System Tuning 1st Edition Ibm Redbooks Ebooks
100% (16)
(FREE PDF Sample) IBM Certification Study Guide AIX Performance and System Tuning 1st Edition Ibm Redbooks Ebooks
66 pages
PGT Resume 1
No ratings yet
PGT Resume 1
1 page