Build it yourself

First, we access the WSDL file. Do the following steps:

1. Make sure that your WebSphere Process Server is started.
2. In Microsoft Visual Studio, select Project > Add Web Reference.



3. The wizard for adding a web reference opens.
4. Into the URL field, paste the URL which you determined previously, for example, http://localhost:9080/BFMIF_widNode_server1/sca/com/ibm/bpe/api/sca/BFMWS/wsdl.

Note: If you want to run the .NET client application and WebSphere Process Server on different machines, you may want to use the server's unique internet address rather than "localhost". As well, you can use "localhost" for the moment and change the service endpoint later.



5. Click Go. WebSphere Process Server will return the details for the BFMWS service.
6. As Web reference name, enter MyBFMAccess and click Add Reference.

Now a C# proxy is created in the file Reference.cs.

In this section we modify the proxy so the proxy can support secure Web services. Do the following steps:

1. Select Project > Add Reference. The Add Reference window opens.
2. Select Microsoft.Web.Services2 from the list and click OK.



3. Select View > Object Browser. The tree view opens.
4. Expand WebServiceClient > WebServiceClientMyBFMAccess.



5. Right-click BFMWSService and select Go To Definition. The file Reference.cs is opened.
6. Replace the string System.Web.Services.Protocols.SoapHttpClientProtocol by the string Microsoft.Web.Services2.WebServicesClientProtocol.



This code change alters the superclass of the proxy; the new class is part of the Microsoft WSE component and allows to call the method RequestSoapContext(...) which we will use in the implementation below.

7. On the toolbar, click the Save button .

Note: The change described in this section must be repeated whenever the proxy code is newly generated. Be aware that this code generation may happen automatically, for example, when you change the Web Reference URL via Solution Explorer > WebServiceClient > Web References > MyBFMAccess > Properties.

Complete the following steps:

1. In the Design view, enlarge the Window Form1 like shown below so the several control elements will fit.



2. In the Toolbox view, select TextBox and click inside the empty Form1 window.



3. This creates a text box control element. Right-click this text box and select Properties.
4. In the Properties view, change the Name from textBox1 to textBoxUserid.



5. In the Toolbox view, select TextBox again and click inside the Form1 window, below the previously created text box.



6. Right-click the second text box and select Properties.
7. In the Properties view, change the Name to textBoxPassword.
8. Change the value for UseSystemPasswordChar from False to True.



9. In the Toolbox view, select Button and click inside the Form1 window, below the second text box.



10. This creates a push button control element. Right-click on the button1 push button and select Properties.
11. In the Properties view, this time do not change the Name but rather the Text value to the new text List Process Templates.



12. Inside the Form1 window, resize the push button to make the new label completely visible.



13. In the Toolbox view, select RichTextBox and click inside the Form1 window. Then enlarge the new element resize as this will contain the output later on.



14. Optionally add two labels Userid: and Password: to the window. In addition, the screenshots for this sample will show a heading on the left-hand side which is a multiline label using enlarged font.



15. On the toolbar, click the Save button .

In this section, we program the push button so it takes the userid and password values and makes the C# proxy call the WebSphere Process Server. Complete the following steps:

1. In the Design view for the Form1 window, move the mouse over the List Process Templates push button and double-click.



2. The file Form1.cs opens, and caused by the double-click the empty method button1_Click(...) is included.



3. Add the following two lines after the last using ... and before the namespace ... statement:

using WebServiceClient.MyBFMAccess;
using Microsoft.Web.Services2.Security.Tokens;

These statements allows to use the short names rather than fully qualified names for several classes (BFMWSService, ProcessTemplateType, UsernameToken, PasswordOption) in the following lines of code.

4. To implement the body of the method button1_Click, add the following lines between the curly braces:

  try
  { // Get userid and password values and wrap it as UsernameToken:
    UsernameToken token = new UsernameToken(textBoxUserid.Text, textBoxPassword.Text, PasswordOption.SendPlainText);

    // Instantiate the proxy and attach the UsernameToken to the instance
    BFMWSService myService = new BFMWSService();
    myService.RequestSoapContext.Security.Tokens.Clear();
    myService.RequestSoapContext.Security.Tokens.Add(token);

    // Create an empty input object and run the query
    queryProcessTemplates queryInput = new queryProcessTemplates();
    richTextBox1.Text = " ... computing ..."; this.Refresh();
    ProcessTemplateType[] templateTypes = myService.queryProcessTemplates(queryInput);

    // Render the result: for each template, show three properties
    richTextBox1.Clear();
    if (0 == templateTypes.Length)
      richTextBox1.Text = "No process templates found on server.";
    for (int i = 0; i < templateTypes.Length; i++)
    {
      richTextBox1.AppendText("Name: " + templateTypes[i].name +
          ", Auto-delete: " + templateTypes[i].autoDelete +
          ", Long running: " + templateTypes[i].executionMode +
          "\n");
    }
  }
  catch (Exception exc)
  { // Whenever an error occurred, let the user know the details
    MessageBox.Show(exc.Message, "Error running sample",
            MessageBoxButtons.OK, MessageBoxIcon.Error);
    richTextBox1.Text = " ... sample failed with exception: " + exc.GetType();
  }

This code creates a UsernameToken from the values in the text boxes for userid and password. Then it uses the proxy to query all process templates. Finally, it displays some of the properties.
To keep the code simple, all potential runtime errors are mapped to one small code snippet.

The top of your editor window will now look similar to this:



5. On the toolbar, click the Save button .