Package services
Services that are part of packages that are imported to your project are known as Package Services.
Package services are the actual integration logic or functional units that do tasks such as data transformation, system integrations, processing business rules, or message routing.
For example, if you have a package that is called OrderProcessing, it might contain services such as OrderProcessing:createOrder, OrderProcessing:validateOrder, or OrderProcessing:sendConfirmation. Each of these services is a package service.
You can create the package services by using webMethods Service Designer. To use in runtime, you must import this package through an external Git repository. After importing the packages, you can use the services in your integrations.
Key points to note
- Make sure that auditing is enabled for packages before you export them from webMethods Service Designer.
- If you export a project that depends on a custom package and attempt to import it into another project, which does not include that custom package, the import fails. To resolve the issue, you must restore the dependency by explicitly adding the custom package to the target project.
- In the Monitor page, to view the package service executions, you must select the appropriate runtime.
- Audit logging is not supported for the sync and restart operations that are part of deployments.
- By default, integrations that use package services are not visible in the
Monitor section. To monitor, you need to enable auditing in Designer before
you export the services.
For more information on how to enable audit for a service, see Enabling Audit in the Designer in End-to-End Monitoring documentation.
- Package services used within deploy anywhere integrations must be carefully designed to avoid circular dependencies in their signatures. A circular dependency in this context refers to a situation where a service’s input or output structure references another service that, directly or indirectly, depends on the original service, creating a loop. Circular references in service signatures can break runtime execution, make debugging harder, and cause unpredictable behavior.
- For package services that include recursive document references in the input or output signatures, the Flow Editor displays up to five levels of recursive document structures. This limit is fixed and cannot be changed. The five‑level limit helps maintain clarity and prevents excessive visual complexity.