Tests are stored in test projects. If your workspace does not contain a test project, the test creation wizard creates one, enabling you to change its name. To store a test in a specific project, verify that the project exists before you record the test.
If you are using Secure Sockets Layer (SSL) authentication, ensure that you have any required key files in your workspace.
If you are using Java™ Message Service (JMS), ensure that you have configured the environment with the correct libraries and configuration files. Ensure that the WSDL files use the correct syntax for the test environment.
If you are using SOAP security, ensure that you have configured the environment with the correct libraries and configuration files.
BPEL models must be synchronous. Asynchronous BPEL models are not supported.
<bpws:import importType="http://www.w3.org/2001/XMLSchema" location="foo.wsdl" namespace="http://foo"/>
Relative
file paths, such as: "../../foo.wsdl" are not supported.<bpws:invoke name="myOperation" operation="myOperation" partnerLink="IServicePartner" portType="ns3:IService" wpc:displayName="myOperation" wpc:id="20">
Only BPEL invoke activities are considered for generating tests. Any BPEL receive and reply activities are ignored.
Websphere Integration Developer does not generate the required soapAction attributes for the soap operations in the WSDL files. Please edit the generated WSDL files, as follows for every operation: <soap:operation soapAction=""/>.
To create a service test from a BPEL model:
Under each test that will be generated, the Operations list displays the WSDL operations that are bound to multiple ports.
If no WSDL operations are displayed under the tests, this means that all operations are bound to a single port. In this case, skip step 6.