Workday

Configure the message flow nodes that are converted from the IBM App Connect Professional Workday activities.

About this task

You converted your orchestration into a message flow. See Table 1, for information on which nodes are used for each of the activities.

Steps are split into sections and are intentionally brief to get you started quickly on configuring the nodes in your message flow. See linked topics in the table for more comprehensive information on configuring the nodes.

Table 1. IBM App Connect Professional Web Services activities and the corresponding IBM App Connect Enterprise message flow nodes
IBM App Connect Professional activity IBM App Connect Enterprise node
Workday activities

SOAPRequest node and

Compute node
In this task, an example of the Get_Job_Families operation from the Human Resources service of Workday is used.
Figure 1. Example message flow
Image of a message flow with a SOAP Input, HTTP Request, Compute and Soap Reply nodes. The Compute node is highlighted.

Selecting a WSDL file

Procedure

  1. Select a SOAP node in the message flow. The Operation mode section opens in Properties, in the Basic tab.
  2. Click Browse to select the WSDL file. In the WSDL Selection window, click Import/Create New.
  3. Select the WSDL file from your local file system.

    Image of the interface for selecting the WSDL file.

  4. Select the binding or definition. Click Finish.
  5. In the WSDL Selection pop up, click the selected WSDL file, then click OK.
    The port type, service port, and other property fields are completed based on the WSDL file data. You can change them as required.

Compute node

Procedure

Provide the credentials:
Replace USERNAME, TENANTNAME and PASSWORD with your own credential values. 
DECLARE bsvc NAMESPACE 'urn:com.workday/bsvc';
set OutputRoot.Properties.IdentitySourceToken = 'USERNAME@TENANTNAME';
set OutputRoot.Properties.IdentitySourcePassword='PASSWORD';
set OutputRoot.Properties.IdentitySourceType = 'usernameAndPassword';
SET OutputRoot.XMLNSC.bsvc:Get_Job_Families_Request.(XMLNSC.Attribute)bsvc:version = 'v30.2';
SET OutputRoot.XMLNSC.bsvc:Get_Job_Families_Request.bsvc:Request_References.(XMLNSC.Attribute)bsvc:Skip_Non_Existing_Instances = true;
SET OutputRoot.XMLNSC.bsvc:Get_Job_Families_Request.bsvc:Request_References.bsvc:Job_Family_Reference.bsvc:ID[1].(XMLNSC.Attribute)bsvc:type = 'WID';
SET OutputRoot.XMLNSC.bsvc:Get_Job_Families_Request.bsvc:Request_References.bsvc:Job_Family_Reference.bsvc:ID[1] = '5f41e62057c944d3a8e60438a2465ca4';
SET OutputRoot.XMLNSC.bsvc:Get_Job_Families_Request.bsvc:Request_References.bsvc:Job_Family_Reference.bsvc:ID[2].(XMLNSC.Attribute)bsvc:type = 'Job_Family_ID';
SET OutputRoot.XMLNSC.bsvc:Get_Job_Families_Request.bsvc:Request_References.bsvc:Job_Family_Reference.bsvc:ID[2] = 'Executive Management';

An example of the code in the editor:Screenshot of the code in the editor.

SOAPRequest node

Procedure

  1. In the Basic tab of SOAPRequest node properties, select the operation mode as Invoke a specific webservice defined by a WSDL interfaceScreenshot of the SOAP Request node properties interface.
  2. Upload the WSDL file for the service you want to invoke in Workday. For example, the Human Resources service.
  3. Change the properties for Port type, Binding and Binding operation. For example: Screenshot of the SOAP Request node properties interface with WSDL properties shown.
  4. In HTTP Transport tab, the location of the Workday service is populated from the uploaded WSDL file. Screenshot of the SOAP Request node properties interface with HTTP Transport properties shown.
  5. Create a security profile for the Workday credentials. For more information on creating a security profile, see Authenticating incoming requests by using credentials stored in the vault.
    During the policy creation, make sure to set Propagation to true.
    In the linked instructions, create local credentials with the configured alias name. Make sure to provide the username as USERNAME@TENANTNAME. For example:
    Screenshot of the interface for creating a security profile.
  6. In the Policy project folder, right click to open the menu and select New, then WS Policy Sets and Bindings option. For example:Screenshot of the menu options for selecting WS Policy Sets and Bindings.
  7. In the pop-up that opens, click Add to create a new policy set. For example:Screenshot of the interface for creating a security profile.
  8. Select Policy_1 and name the policy. For example: Screenshot of the interface for setting up policy sets and policy set bindings.
  9. Click Add WS-Security.
  10. Add and name the authentication token. For example:Screenshot of the interface for adding an authentication token.
  11. Select Policy Set Bindings and click Add to create a new Policy Set Binding.
  12. Select Bindings_1 and give the name of your choice. In Associated Policy Set field, select the policy that you created in Step 5.
  13. Set the This Policy Set Binding configuration will be used with option to Consumer. For example:Screenshot of the interface for creating new policy set bindings.
  14. Click Finish.
  15. Right click the application name that contains your message flow and click New, then Select BAR file. For example: Screenshot of the interface for creating a new bar file.
  16. Open the bar file that you created, from the BARs folder.
  17. In the Prepare tab, select the application where your message flow is running.
  18. In the Build Options menu, select the Remove contents of the archive before building option and de-select all other options. For example: Screenshot of the interface for choosing build options.
  19. In the Manage tab, select your message flow. In Configure tab, provide the Consumer Policy Set and Consumer Policy Set Bindings with the Policy project in which you created the Policy Set and Policy Set Bindings in Step 5. and Step 6. in the following format: 
    {POLICY_PROJECT_NAME}:POLICY-SET_NAME 
{POLICY_PROJECT_NAME}:POLICY-SET_BINDING_NAME
    For example:Screenshot of the Manage interface for adding the policy and bindings.
  20. Select the SOAPRequest node and in \Configure tab, set the security profile to Default Propagation. For example: Screenshot of the Manage interface and setting the security profile.
  21. Deploy the policy project that you created to the integration server and build the BAR file by using the Build and Save option in the Prepare tab of the BAR file. Deploy it to the integration server.

What to do next

Run your flow. If you've made changes, you need to redeploy when you start your Flow Exerciser.