Deploying and Testing the callLookupUser Application

You should be able to deploy and successfully run the callLookupUser application.

1. Deploy the callLookupUser project to the server where the EntityResolverService is running.
2. Log in to Openspace as user tibco-admin.
3. Using the Organization Browser, make sure that:
   • an LDAP container exists that uses the easyAs LDAP source. (See "Create an LDAP Container" in the Create, Deploy, and Run Your First BPM Application > How to Map Users to the WelcomeUsers Organization Model tutorial for more information.)
   • Clint Hill and at least one other user from this container are valid BPM users (that is, created as resources).
     Note: If Clint Hill is not a valid BPM user, the process will fail when the Call lookupUser operation task is invoked.
4. Click Business Services.
5. Select and start the callLookupUser/callLookupUser business service. The Get User’s Name form is displayed.
6. Enter Clint Hill’s login name and click Submit.

   The Display User’s GUID form is displayed, showing the name submitted and the GUID associated with that name.

7. Click Submit to finish the process.
8. Run the business service again with different data. The following table shows the expected results.

   User name	GUID Displayed	Notes
   a valid BPM user	user’s GUID	The lookup user call finds the user. The user’s GUID is displayed.
   this_string	unknown user	No matching user is found by the lookupUser call so no detail elements are returned. The default userGUID value is displayed.
   Clint*	unknown user	Wildcards are not supported by the lookupUser name parameter. The user name entered must be an exact match. No matching user is found by the lookupUser call so no detail elements are returned.