About Packages

A package contains a set of services and related files, such as specifications and document types. When a project is created, a package is created with the same name as the project. For example, if you create a project that is named FlowAny, an associated package is automatically generated in the system as FlowAnyProject. When you add a service, specification, or document type to the project, they are stored in the corresponding package. So, a package contains the assets that are used in the project. Thus, you can easily manage all the services and files in the package as a unit.

Apart from your project assets, you can add the integration packages that are stored in any external repositories to a project and use it along with other assets in the project. Currently, you can add packages that are stored in GitHub.

Important: webMethods packages that are referenced in your package are pulled from the web Methods Package Registry and like containers are secured by using an access token. This token is automatically generated and included in the runtime manifest file by your tenant. This token can become invalidated and result in errors when syncing. In which case you must do a resync from webMethods Integartion to get a refreshed token.

Packages offer many benefits such as

Modularity and Reusability - Organize and modularize your integration components and services, making it easy to reuse and share them across different projects.
Version Control - Maintain and manage package versions, which is crucial for tracking changes, ensuring compatibility, and rolling back to previous versions if needed.
Isolation and Security - Provide a level of isolation, helping you control access to specific integration assets. This improves security and safeguards against unauthorized modifications.
Ease of Deployment - Simplify the deployment process by bundling related integration components into a single unit. This reduces deployment errors and ensures consistency.
Enhanced Maintenance - Easier to maintain and manage integration assets, as changes can be localized within a package without affecting other parts of the system.
Customization - Create custom packages that are tailored to your organization's specific needs, promoting flexibility and adaptability to your requirements. Thus, packages offer a structured and efficient way to manage, deploy, and maintain integration components, promoting modularity, reusability, and security for efficient integration management.

Accessing Packages

Click Projects. All projects appear.
Click a project card for which you want to view the project package details.
Click Packages. The list of packages associated to the project appears in a tabular format.
Click the package for which you want to view the details. The package details appear, see Packages Tab.

Packages Tab

The Packages tab lists the packages that are used in your project. The main package created when the project was set up is highlighted in blue and appears on the first row. Custom packages that are imported from external repositories are listed beneath the main package. .

The Packages tab displays the following details about the packages that are used in a project.

Package Name - Displays the name of the package. You can click the package name to view complete details of a package in the Package Details view that consists of the following tabs: Package Information, Assets, Security, and Libraries.
Version - Indicates the version number of the package.
Load Status- Indicates that the package load status as follows.
- Yes if the package is loaded successfully.
- Partial if only some components were loaded.
- No if the loading process failed entirely.
For more information about how to reload a package, see How to Reload a Package.
Actions - Lists all actions that you can do on a package. Only when the package load status is No, you get the various options as follows.

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 - List of packages that are imported from other repositories to this project.
- 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 IBM® webMethods Integration.
Enabled Indicates whether a package is enabled in the cloud runtime.
Loaded - Indicates whether a package is loaded or not loaded in cloud runtime.
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 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. See, 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 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 the library by clicking the Delete icon. The library is deleted after you confirm.
Download the library by clicking the Download icon. The library is downloaded to your local system according to your browser's settings.
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 - 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 - 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.

View Project Package Variables

Variables that are used in Packages can be viewed under the Package Information page. The Variables column displays all relevant variables, from the imported packages, in one place.

Important: Password values are stored in an encrypted format for security reasons, so they cannot be viewed directly.

Note: Existing project package variables are not available in Packages. To use them in Deploy Anywhere Flow Services, you must create new variables.

How to Reload a Package

Key points to consider for Load status usage

Make sure that the dependencies are resolved before adding the package.
If a package is not loaded and the Load Status column displays No, then the option to reload, enable, and delete appears.
If a package is not enabled, then the user cannot view the assets, and the project do not work as expected.

Steps to reload a package

Go to Projects > Packages . The Load Status column reads No if a package with unresolved dependencies is added.
Click Reload. A confirmation message appears.
Click Reload. The package is reloaded.