Table of Contents

Search

  1. Preface
  2. Overview, Downloading, and Installing
  3. Administration API
  4. Identity Service API
  5. Screenflow Programming and SDK
  6. ActiveVOS WSHT API
  7. Embedding Request Forms in Standalone Web Pages
  8. XML-JSON for Process Central

7. APIs, SDKs, and Services

7. APIs, SDKs, and Services

Development Setup

Development Setup

In order to interact with the WSHT API using web services, make sure that the following are configured on your Process Server:
  1. Process Sever Identity Service is enabled and configured. For example, LDAP/Active Directory.
    If you are using the evaluation version, you can use the default settings, which is to use an XML file (similar
    tomcat-users.xml
    ) that contains list of roles/groups and users:
    Username
    Password
    Roles
    loanrep1
    loanrep1
    loanreps, abTaskClient
    loanrep2
    loanrep2
    loanreps, abTaskClient
    loanrep3
    loanrep3
    loanreps, abTaskClient
    loanmgr1
    loanmgr1
    loanmgrs, abTaskClient
    loanmgr2
    loanmgr2
    loanmgrs, abTaskClient
    loancsr1
    loancsr1
    loancsrs, abTaskClient
    Note: the task users (for example, loanrep1) also have the
    abTaskClient
    role in order access the secured service endpoint.
  2. The Web service endpoint to access the task operations is secured (for example, using HTTP Basic authentication). This can be done by un-commenting the appropriate section in the Process Server's
    web.xml
    file (located in
    active-bpel.war)
    . Here's an example of what the
    active-bpel.war web.xml
    file looks like:
    <security-constraint> <web-resource-collection> <web-resource-name>WS-HT BPEL for People Client</web-resource-name> <description>Endpoint that contains all of the operations for an WS-HT BPEL for People client application. These applications will provide an interface for people to interact with tasks that were created by people activities within a BPEL process.</description> <url-pattern>/services/AeB4PTaskClient-taskOperations</url-pattern> <url-pattern>/services/AeB4PTaskClient-aeTaskOperations</url-pattern> <url-pattern>/taskxsl/*</url-pattern> </web-resource-collection> <!-- TASKCLIENT Uncomment to restrict access to the task client services <auth-constraint> <role-name>abTaskClient</role-name> </auth-constraint> TASKCLIENT --> </security-constraint>
    Note
    : The Web container's authentication provider (for example,
    tomcat-users.xml
    in Tomcat file based provider) must use the same data (that is, list of usernames and roles) as does the Identity Service.