Building Your Event-Driven Architecture : Integration Server Administrator’s Guide : Managing Packages : Using Packages : Predefined Packages
Predefined Packages
The following packages are predefined and installed by default on each Integration Server instance. They are also included in the package repository.
Package
Description
Default
Integration Server looks in this package if a user accesses the server without specifying a package name (for example, by using the URL http://localhost:5555). You can also use it to store elements you create without first creating a package.
Note:  
Integration Server searches the pub directory in the Default package for an index.dsp or index.html file. As shipped, the pub directory contains an index.html file that points the user to an index.dsp file in the WmRoot package. This index.dsp file loads the Integration Server Administrator. To prevent a user from inadvertently accessing the Integration Server Administrator, you can edit the index.html file in Default/pub and change it to point to an innocuous page. To prevent a user from seeing or accessing all DSP files on Integration Server, you can use the watt.server.displayDirectories server configuration parameter. See Stage 7: Setting Up Security for more information.
WmPublic
This package contains services that you can call from your client applications and services. See the webMethods Integration Server Built-In Services Reference for more information.
WmRoot
This package provides core Integration Server functionality and auxiliary files.
Important:  
Do not alter or delete this package.
WmTomcat
Deprecated - The WmTomcat package is deprecated as of Integration Server 9.10. Existing web applications based on the WmTomcat package can be migrated to webMethods Application Platform.
This package contains the Tomcat servlet container and JSP Engine developed by the Apache Software Foundation (http://www.apache.org/). Using this engine, developers can deploy and execute JavaServer Pages, Java servlets, and their supporting files within the Integration Server environment or incorporate web applications into new or existing webMethods packages.
Note:  
The WmTomcat package is installed by default, but is no longer enabled by default. The WmTomcat must be disabled if you want to use webMethods Application Platform with this Integration Server.
WmART
This package supports webMethods 6 or later adapters.
Important:  
Although the WmArt package is installed by default, if you are not fully licensed to use this package, it will be hidden from view, and you will not be able to build or run custom adapters, or use any transaction services.
WmVCS
Deprecated - The WmTomcat package is deprecated as of Integration Server 9.9. Use the local service development feature (Local Version Control Integration) to check package elements and their supporting files into and out of a version control system (VCS) directly from Designer.
This package contains services that enable you to use the VCS Integration feature to store Integration Server elements in a version control system (VCS). See the Configuring the VCS Integration Feature for information about configuring the VCS Integration feature. For information about using Designer with a source control system, see webMethods Service Development Help.
WmXSLT
This package contains services that you use to transform XML data from one format or structure to another. See the webMethods Integration Server Built-In Services Reference and webMethods Service Development Help for more information.
The packages in the table below provide services that enable you or other webMethods products to perform certain tasks.
This package...
Contains services that...
For more information...
WmARTExtDC WmISExtDC WmTNExtDC
Infrastructure Data Collector uses to discover and monitor adapters installed on Integration Server, Integration Server itself, and Trading Networks Server, respectively.
Administering webMethods Optimize
WmAssetPublisher
Integration Server uses to extract and publish metadata about its services to CentraSite Metadata.
webMethods BPM and CAF Workspace Metadata Help
WmCloud
Integration Server uses to share services with webMethods Integration Cloud.
Configuring On-Premise Integration Servers for webMethods Cloud
WmDesigner
Support business processes modeled in Software AG Designer.
Software AG Designer Online Help
WmFlatFile
Flow services or the File Polling processing service can call to initially accept and consume inbound flat files.
webMethods Integration Server Built-In Services Reference
WmMobileSupport
Contains services that support data synchronization solutions between mobile devices and backend applications.
Developing Data Synchronization Solutions with webMethods Mobile Support
WmOptimize
Support business processes monitored using webMethods Optimize.
Optimize documentation
WmPRT
Support business processes executed using the webMethods Process Engine.
Administering webMethods Process Engine
WmTaskClient
Support tasks developed using the webMethods Task Engine.
webMethods Task Engine User’s Guide
WmWin32
You can use for Integrated Windows authentication on Integration Server.
Note:  
This package is deprecated in Integration Server 7.1
If you want to streamline Integration Server (for example, because you are using it only to host adapters), you can disable many of the packages described in above.
Important:  
Do not disable, delete, or alter the following packages: Default, WmPublic, WmRoot.
You can disable the following packages:
Package
Restriction
WmART
Important:  
Do not disable this package unless you are also going to disable WmARTExtDC, or WmARTExtDC will not load.
WmAssetPublisher
None.
WmARTExtDC WmISExtDC WmTNExtDC
Important:  
Do not disable the WmISExtDC package unless you are also going to disable WmTNExtDC and WmARTExtDC, or those packages will not load.
WmFlatFile
None.
WmPRT WmDesigner WmTaskClient
None.
WmMobileSupport
Before disabling the WmMobileSupport package, suspend all mobile sync components that are enabled.
WmOptimize
None.
WmTomcat
None.
WmVCS
None.
WmXSLT
None.
For instructions on disabling a package, see Disabling a Package.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback