Operational Guidelines

This section provides information that you need to work with IBM webMethods Integration.

Usage Notes

General

IBM webMethods Integration is supported on the latest version of Google Chrome web browser (v110 or later).
Every time you upgrade IBM webMethods Integration, ensure that you clear the cache manually before logging in to IBM webMethods Integration. This is because the older browser’s cache and cookies are not cleared automatically and the page content may not display correctly.
IBM webMethods Integration is best experienced when the scale and layout settings are as follows:
IBM webMethods Integration supports Transport Layer Security (TLS) version 1.1 and version 1.2 for connectivity.
Any time stamp displayed in IBM webMethods Integration is based on the user’s registered time zone specified in IBM webMethods iPaaS. Not all the time zones in IBM webMethods iPaaS are supported in IBM webMethods Integration. If a time zone in IBM webMethods iPaaS is not supported, then the time stamp in IBM webMethods Integration defaults to the Pacific Standard Time (PST) time zone. To change the time zone for a user profile, using the App Switcher, go to IBM webMethods iPaaS and in IBM webMethods iPaaS, click Administration. On the Administration > Users page, edit the user profile. Under Locale information, select the required Time zone. Save the changes, log out, and then log in again to see the changes.
IBM webMethods iPaaS products are available in several geographical regions, operated by different infrastructure providers. Go to the IBM webMethods iPaaS Regions website for information on the available products, IP addresses, and also the underlying infrastructure provider in each region.
See the Tenant URL and IBM webMethods iPaaS Region section for more information.
For information on major releases, hotfixes, and patch releases including the latest statistics on the availability of cloud environments, incident history, and planned maintenance events, see the Service Status page.
IBM webMethods Integration v10.16 uses the regular expression pattern as described in the java.util.regex.Pattern class. Earlier, IBM webMethods Integration used Perl 5 compiler and pattern matching while evaluating regular expressions. Some Perl 5 constructs are not supported by java.util.regex.Pattern which can result in unexpected behavior, such as a java.util.regex.PatternSyntaxException during expression evaluation. If your Flow services use regular expressions based on Perl 5 constructs, it is recommended to review the regular expressions to ensure compatibility with the behavior described in the java.util.regex.Pattern class API documentation available here:
https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html
Review the contents of the Comparison to Perl 5 section, which identifies Perl constructs that are not supported by java.util.regex.Pattern. Regular expressions that rely on these Perl 5 constructs must be modified to work correctly with java.util.regex.Pattern.
Note: The replace and tokenize built-in String services accept a regular expression as an input. If execution of one of these services results in the java.util.regex.PatternSyntaxException, change the syntax of the supplied pattern. For example, if your regular expression has a value of , change it to . This change is required because characters like { or } need to be escaped with \ in the expression.
IBM webMethods Integration does not honor the following headers and their values will be ignored:
- X-Forwarded-Host
- X-Forwarded-For
- X-Forwarded-Proto
- X-Forwarded-By

Although the Workflow to flow service or on-premises application mapping of the following data types is allowed in IBM webMethods Integration, such workflows, flow services, or on-premises applications may not run as expected:
- String type in workflows to Num (Double/Float/Int/Short/Long) type in on-premises applications
- String type in workflows to Byte type in on-premises applications
- Boolean type in workflows to Byte type in on-premises applications
- Object type in workflows to Byte type in on-premises applications
- Number type in workflows to Byte type in on-premises applications
- Array type in workflows to Num type in on-premises applications
- Number type in workflows to Boolean type in on-premises applications
- Boolean type in workflows to Num type in on-premises applications
- Object type in workflows to Num type in on-premises applications
- String of String Array type in workflows to Boolean type in on-premises applications
- Float type in workflows to Num type in on-premises applications
- If the data type of a Flow service is set to Object in the I/O signature, then it is considered as a String type in the associated workflow. Such workflows may not run as expected.
Connectors
- For SOAP and REST connectors, if you have created an account while creating a flow service, then that account:
  - cannot be edited or deleted from the Connectors page.
  - cannot be used in Workflows. The pre-existing accounts are not available in the Connectto drop-down list while creating a Workflow.
  - cannot be used in migrated REST applications.
    You have to create a new account in all the above mentioned scenarios.
- After changing a REST-based connector’s document type, ensure that you update the operation using that doctype. This updates the operation signature, and the doctype changes reflect correctly in the connector.
- After creating a SOAP connector, if you immediately try to update it’s description, the updation process takes longer than usual. Update the SOAP connector by going to the Connectors page.
- Some pre-defined operations in the Salesforce® CRM REST connector may not work if you are using an account configured with the JWT flow authentication type.
- Click here to see some of the most common scenarios you may come across while configuring an Account, as well as troubleshooting tips on Account configurations. Information on the connector Account configuration fields can be found here. For information on custom actions, custom fields, field lookups, business objects, business parameters, and interactions, click here. Browse through the IBM Tech Community tutorials related to connectors here.
- The FTP connector used in a Flow service is different from the FTP connector used in a workflow. So if you create an FTP account in a Flow service, the FTP account will not be available inside a workflow. Similarly, if you create an FTP account in a workflow, the same FTP account will not be available inside a Flow service.