How to use the Web Services tester
Web Services tester is HTTP based tool that allows you to test both IFS
activities/services and
external Web Services.
Contents
Web Services tester is located in Solution Manager / Integration folder.
- Target Applications
The applications you want to test separated with semicolon. The formats
host:port and host:port/module is allowed.
Note: Tester of Web Services is one of the internal systems and as
such implies some limitation, e.g. doesn’t work with single-sign-on. By
default the Target Application field is filled with the web server name and
port configured for client accesses that not necessarily is the same as the
one configured for internal systems. If your system is defined with two
different web servers, use the one configured for internal systems here.
- Create Request buttons
There is 3 possibilities to create the xml request.
1) Create Activity Request:
By selecting an activity or service and a operation is the soap xml request
automatically created.
All activities and services in Target Applications is listed.
2) Create BizApi request:
By selecting a BizApi, transformer and envelope is the request automatically created.
All BizApi's in Target Applications is listed.
3) Create Request from File:
By browsing to a file can any format be used as request.
- Url
Defines where the message should be sent to.
Is automatically created when using
- Create Activity Request
- Create BizApi Request and Use SOAP Action checkbox checked.
Note: If the system is configured with separate web
servers for client accesses and internal systems, the URL must point to the
server configured for internal systems. See the note above about
target application.
- SOAP Action
Defines the SOAP Action which is included to the HTTP header.
Is automatically created when using
- Create Activity Request
- Create BizApi Request and Use SOAP Action checkbox checked.
- User ID and Password
A user and password that have authorities to run the Web Service.
Note: Only Basic authentication supported.
- Invoke button
Starts the HTTP request by using the request from the Request window
- Request window
Shows the request
- Response window
Shows the response from the HTTP invocation
- Press the button Create BizApi Request
- - Select the actual BizApi
- Select envelope = SOAP_SIMPLE
- Mark the checkbox Use SOAP Action
Press OK
- Url, SOAP Action and a proposal to Request is now automatically created.
Edit the Request to some relevant values.
- Enter User ID and Password
- Make the HTTP invocation.
The Request will now be sent to the SOAP Gateway that will execute the
BizAPI direct.
The Response from the BizApi will be shown in the Response window.
If a response error will a System Exception Error window popup.
Using IFS XML format
- Press the button Create BizApi Request
- - Select the actual BizApi
- Select envelope = SOAP_IFS or leave this field blank
- Unmark the checkbox Use SOAP Action
Press OK
- Enter the Url.
Make sure that SOAP Action is blank. Then will the message be directed to
IFS Connect.
Edit the Request to some relevant values.
- Enter User ID and Password
- Make the HTTP invocation.
The Request will now be sent to
IFS Connect which will try to match it to a routing rule.
The Response from IFS Connect will be shown in the Response window.
If a response error will a System Exception Error window popup.
Using another formats
- Press the button Create Request from File
Browse and select the actual file.
- Enter the Url.
Make sure that SOAP Action is blank. Then will the message be directed to
IFS Connect.
Edit the Request to some relevant values.
- Enter User ID and Password
- Make the HTTP invocation.
The Request will now be sent to
IFS Connect which will try to match it to a routing rule.
The Response from IFS Connect will be shown in the Response window.
- Press the button Create Activity Request
- - Select the actual Activity
- Specify the Operation
Press OK
- Url, SOAP Action and a proposal to Request is now automatically created.
Edit the Request to some relevant values.
- Enter User ID and Password
- Make the HTTP invocation.
The Request will now be sent to the SOAP Gateway that will execute the
Activity.
The Response from the Activity will be shown in the Response window.
An asynchronous BizApi that is posted to Connectivity outbox can starts to
process by
following the sequence below.
Note! If this should work must the scheduled tasks for outbound BizApi's
be suspended.
If not then will the scheduled task fetch the message.
- Press the button Create Activity Request
- - Select Activity ConnectivityProcessingHandler
- Set operation to ProcessOutboundBizapi
Press OK
- Url, SOAP Action is now automatically created.
Edit the Request.
- Set BIZAPI_NAME
- Set MEDIA_CODE (CONNECT if message is created from PLAP)
- Set CLASS_ID (CONNECT_MSG if message is created from PLAP)
- Enter User ID and Password
- Make the HTTP invocation.
Following will now be processed:
- The message is fetched from Connectivity Outbox
- The outbound BizApi will be invoked with input from the content of
Connectivity Outbox
- The response from the BizApi will be posted to some queue.
To the OUT1 queue if a matching routing rule is find and to the ERROR queue
if no matching rule is found.
- Search for the ApplicationMessageID
- Open the message and look at the Request in the Message Body.
- Press the button Create BizApi Request
- - Select the actual outbound BizApi
- Select some envelope if it should be used
- Select some transformer if it should be used for transformation to another
format
- Unmark the checkbox Use SOAP Action
Press OK
- Enter Url and SOAP Action for the external Web Service.
- Enter User ID and Password
- Make the HTTP invocation.
The Request will now be sent to
the external Web Service.
The Response will be shown in the Response window.