Connectors and Developer Tools

Where to find the list of supported connectors and information on the Account configuration fields?

You can find the list of predefined connectors that are supported by IBM® webMethods Integration under the Categories section. You can also create custom connectors using the Node.js CLI-based Connectors or by using the Connector Builder - IBM webMethods CloudStreams Connectors. See Troubleshooting tips on Account configurations for some of the most common scenarios you might come across while configuring an Account. See Account configuration fields for information on the connection configuration fields.

What is the maximum size for object storage in Flow Store, Memory Store, and Account Store?

The maximum data size for a single object in Flow Store, Memory Store, and Account Store is 16 MB.

Call one workflow from another workflow

You can call one workflow from another workflow by using the Run Flow action.

"The provided hostname is not valid. Provide a valid hostname" error while configuring the SOAP connector despite allow listing the required IP addresses in the SAP system?

This issue is observed due to the usage of a WSDL URL associated with a private host that IBM webMethods Integration cannot access from AWS DE (Amazon Web Services Development Environment). To address this issue, expose the WSDL through a Public IP or host, ensuring accessibility from AWS.

You are redirected to the Test action window, where you can check whether the action is working as expected before running the workflow. After this step, click Done. This will redirect you to the canvas.

Developed an integration that creates a compressed file, serializes it, and sends it to Azure Blob Storage through an HTTP request. However, the receiving service is rejecting the file stream we are trying to send, claiming it is corrupted. What is the resolution?

IBM webMethods Integration supports two distinct integration platforms that are named workflow and Flow service, and file streaming between these platforms is not supported. Your current integration uses the SFTP action, which is part of the workflow, and an HTTP operation, which is part of the Flow service. This incompatibility is the reason that you are encountering the problem. Use the SFTP and HTTP operations within the Flow service to resolve this issue.

403 Forbidden error when passing a folder path with "/" delimiter as the folder separator for the Amazon S3 connector?

The 403 Forbidden error occurs when using a folder path with "/" delimiter as the folder separator in the Amazon S3 connector. This issue arises due to the specific handling of double slashes in the resource path by the S3 application. When a folder path is passed with "/" as the separator, it results in a resource URI with double slashes, which is not allowed and leads to the 403 Forbidden error. This behavior aligns with the RFC specification (See RFC 3986 Section 3.3) and cannot be handled generically.

To resolve this error, avoid "/" as the folder separator at the beginning of the input or follow the guidelines that are provided in the documentation to ensure compatibility with the Amazon S3 connector.

How to change the GUID for a custom connector?

To change the GUID for a custom connector, follow these steps:

  1. Replace the GUID key in your configuration with the correct value found in the index.json file.
  2. Log in with the owner credentials and run the command wmio deploy to update the existing connector with the new GUID values.
  3. If the GUID for the actions is not updated initially, redeploy the connector.

What happens to the file created by the Write File action in a workflow?

The file that is created by the Write File action is temporary. It exists only during the workflow execution and is automatically deleted once the execution is complete.

Is there a separate Delete File action?

No, there is no separate Delete File action, as the temporary file that is created during the workflow is automatically deleted at the end of the execution.

Update an existing file in a workflow

There is no dedicated Update File action. Instead, use the File Append action to add content to an existing file.

Are there any limitations on file storage in workflows?

Yes, the storage capacity for file actions is determined by the container size that is assigned to the workflow.

Retrieve the temporary file created during the workflow execution

Once the workflow execution is complete, the temporary file is deleted and cannot be retrieved.

Why does the Read file action fail with a File not found error after resuming a workflow that has a Write file action?

When a workflow with a Write file action runs successfully, but an action in between fails and is resumed, the subsequent Read file action might fail with a File not found error. This is because the file path generated by the Write file action becomes invalid after the workflow is resumed from the failure point. The file that is created during the initial execution is no longer available when the workflow resumes, as the file path might not be preserved or accessible after resumption. This behavior is by design, as file-related actions should be completed within the same execution cycle to ensure that the file path remains valid for the Read file action.