Adding Packages to a Project

You can add your own integration packages that are stored in an external repository to a project and use it along with other assets in the project. Currently, you can add packages that are stored in GitHub.

Note:
  • It is not possible to import a webMethods Integration project package into another webMethods Integration project. Projects are considered top-level integrations and must be deployed independently. Create a custom package if you want to share code between projects and use messaging for intra project collaboration.
  • Only the recent versions of the CloudStreams Connector provider packages are supported.
  • Database, IBM® Power®, SAP® ERP, Kafka, IBM MQ, PeopleSoft, SharePoint, AS400, and HDFS accounts imported from Git are disabled. Update the password before enabling the accounts.
  • Global variables of the type password that is imported from Git are initially set to null. Update the global variables of type password before you run the flow services by using them.

Before you Begin

  • Make sure that you have the GitHub account details to access the GitHub repository where the packages are available.
  • Before exporting the packages created in webMethods Service Designer, make sure of the following details.
    • Enable auditing for each service that you want to monitor in the Monitor page. For more information about enabling auditing, see Enabling Monitoring for Package Services. Remember to only enable this where low-level monitoring is needed as it has a performance impact on your processing. Any errors that are propagated to a parent service are then shown up in Monitoring.
    • Update the package dependencies to reflect any packages that it depends on. This is an important step as during loading the dependent packages are automatically added to your target runtimes if not already present.
    • The Visible property is set to public to allow webMethods Integration workflows to use CloudStreams connectors or flow services that are created in webMethods Service Designer.
    • For packages created using the local development feature in webMethods Service Designer, make sure that the Enforce a single Git repository property is selected. To make sure that the webMethods package is automatically converted into a Git repository, aligning it with the native structure of IBM webMethods Integration packages. For more information, see Using the Local Service Development Feature in webMethods Service Development Help.

Basic Flow

  1. In the Projects tab, select a project.
  2. Click Packages. The details of packages, if any, assigned to that project appear.
  3. Click Add package. The Add Package page appears.
  4. Select Git. The options to enter Git details appear.
  5. Provide the following details.
    • In Git URL, enter the URL of the package repository where the package is hosted.
    • In Source Control, select the display name of the account that is associated with the repository. The drop-down list displays all Git accounts available to you.
      Note: You can add a new Git account by clicking Add. For more information about adding a new GitHub account, see Configuring Git Accounts.
  6. Click Next.
  7. Select a particular branch or tag of the repository to use as the source for the package in the Git branch/Tag field.
  8. Click Pull. A confirmation message appears after a successful addition of a package to a project. The assets such as flow anywhere services, connectors, and any other artifacts that are associated with in the package can now be used in your project.