Resources

Resources represent users who log into BPM applications and receive work items that they need to work on.

Resources are obtained from LDAP sources, which are separate servers to which the Organization Browser connects to get a list of candidate resources. Before a resource can log into a BPM application, the candidate resource must be made a BPM resource by using the Add Resource function in the Organization Browser.

Resources can be mapped to groups or positions in the organization model; resources receive work items in their work list because of being mapped to certain groups or positions. If you map a candidate resource to a group or position, the Add Resource function is executed prior to the mapping, making the resource a BPM resource before it is mapped.

If you just "add" a resource, without mapping the resource to a group or position, it allows the resource to log in to BPM applications, but the resource will not receive work items until after being mapped to a group or position in the organization. Resources can also be deleted, preventing them from logging in.

Resources can log into the BPM application using the “Resource Name” assigned to the resource (which can be modified), and a password specified in the LDAP source.

Note: By default, BPM applications recognize the user name “tibco-admin” with a password of “secret” as the System Administrator (although these names may be changed). This is the only user authorized to log in until another user is configured using the Organization Browser. By default, the tibco-admin resource is located in the System Admin container.