Viewing packages

View the packages added to a project from the Packages tab under Projects.

Procedure

  1. From the navigation pane, click Projects.
    All projects appear.
  2. Click a project card for which you want to view the project package details.
  3. Click Packages.
    The list of packages associated to the project appears in a tabular format.
  4. To view further details about a package, click any package.
    The Package Information tab appears.

Results

You can view the packages added to your project.

What to do next

You can click on any package name to view details about that package.
Package Information
The Package Information tab lists the following details:
Git branch/tag
Indicates a specific branch or tag in the repository where the package is saved.
Pull
Retrieve the recent changes from the remote repository.
Version
Indicates the version number in the package's manifest file.
Build number
Unique number that a developer assigns to a package each time it is generated.
Git URL
Repository path where the package exists.
Used by
List of the packages that are using this package.
Dependent Package
A dependent package refers to a package that relies on another package to function correctly. This dependency typically arises when services, shared resources, or classes from one package are used in another. The Dependent Package section lists all dependent packages with the following details:
  • Version - Indicates the version number in the package's manifest file.
  • Actions - Lists the actions that you can do on a package.
Package Load Errors
Displays information about issues that occurred during package load. The Cause column indicates what caused the error and the Reason column provides a brief explanation of why the package failed to load properly.
Note: You cannot import packages that are created in webMethods Integration.
Enabled
Indicates whether a package is loaded and active in the runtime. For more information, see Enabling packages
Loaded
Indicates whether a package is loaded or not loaded in the runtime. Package loading refers to the process by which the runtime loads a package into memory during startup or when the package is manually enabled. This makes the services and resources within the package available for execution. For more information, see Reloading packages.
Startup Services
List of services that are identified as essential for proper functioning of a package.
Shutdown Services
List of services that are identified as essential for the proper closing of services.
Assets

Assets are files or resources that are used by various services in your project. The Assets tab lists all the integration resources that are related to flow services within the package.

The following asset details are displayed:
Name
Name of the asset.
Type
Type of the asset, for example, Java service, flow service, reference data, document type, or any other service.
Namespace
Full name of the asset for identification.
Visibility
Specifies whether a service is Private or Public. Services marked as Public are available in integrations for use. Services marked as Private are hidden and are not available in integrations by default.
Note: You cannot modify the visibility of a service in the cloud. You need to set its Visible property to true in the Properties view of webMethods Service Designer.
Dependent Assets
Displays the integrations in which the asset is being used. For more information, see Viewing dependent assets.
Security

The Security tab in the Packages page shows a list of services that are denied by default within a package with the following details:

Note:
  • You can modify the service information only if you have the write access for that project.
  • Modifications to a restricted service or Java service for a package in a runtime affects all packages in that environment. That is, the change applies to all packages, not just the one you are working on.
Restricted Services
Displays all denied services within the package.
  • Name - Displays services marked as denied by default.
  • Used In - Lists flow services where the denied service has been used.
  • Restrictions - Displays an option to specify the access status of a service within the integration. You can set one of the following values by toggling the button.
    • Select Allowed to allow a service to be used in integrations.
    • Select Denied to restrict a service.
Java™ Services
Displays all Java services within the package. By default, Java services are not supported to run in the runtime environment. However, if you need to run these services, you have the following options:
  • Allow Java Services - Set with one of the following values:
    • Restricted - Specific Java services are allowed to run.
    • All - All Java services to run without individual selection.
    • None - Restrict all Java services from running.
Name
Name of the Java service.
Restrictions
  • Option to specify the access status of a Java service within the integration. You can set one of the following values by toggling the button:
    • Select Allowed to allow a service to be used in integrations.
    • Select Denied to restrict a service.
Libraries
The Libraries tab provides a list of all third-party libraries such as JAR or Shared Object (SO) files that are uploaded in the project. The basic library details such as name, and class path type appear. You can do the following operations on these libraries:
Delete
Delete the library by clicking the Delete icon. The library is deleted after you confirm.
Download
Download the library by clicking the Download icon. The library is downloaded to your local system according to your browser's settings.
Add Library
Upload the library by clicking the Add Library icon. In the Add library page, select the library to upload by clicking the Browse icon and then choose the Classpath type as one of the following values.
  • Server - The library is available for use to all the packages in the runtime. Restart the runtime for the changes in the libraries to take effect.
  • Package - The library is available for use in the current package only and the package is reloaded automatically after the library is uploaded to the package.
Note:
  • You can upload, download, and delete libraries in a project package only.
  • You cannot upload a file that exceeds 50 MB.
  • You can select multiple files to upload.
  • You can upload libraries with the same name if the Classpath type is different.
  • For the PeopleSoft Connector, convert the compressed compiled Component Interface .class files into .jar format to include in libraries.
Variables
All variables added to a project through a package are displayed in the Variables page. The variables can be either global or package-specific. These variables are accessible at the project-level and not across projects in a tenant.
Important: Password values are stored in an encrypted format for security reasons, so they cannot be viewed directly.