Currently the following services are available

  • Memory / Session service be.securit.trustbuilder.util.TimedBlockingHashMap
  • MemCached / Session service be.securit.trustbuilder.service.MemcachedService
  • DateService be.securit.trustbuilder.service.DateService
  • EncryptionService be.securit.trustbuilder.service.EncryptionService
  • Radius Endpoint Service be.securit.trustbuilder.service.RadiusService
  • Ldap Endpoint Service be.securit.trustbuilder.service.LdapService
  • Domtai Service be.securit.trustbuilder.service.DomTai
  • Redis Service be.securit.trustbuilder.service.RedisService

The Service section can be used to call different services, for example a memory store.

<stb:Service stb:id="urlStore" stb:type="be.securit.trustbuilder.util.TimedBlockingHashMap" stb:singleton="true">
   <stb:property stb:name="ttl">30000</stb:property>
<stb:Service stb:id="objectStore" stb:type="be.securit.trustbuilder.util.TimedBlockingHashMap" stb:singleton="true">
  <stb:property stb:name="ttl">30000</stb:property>

In this example we configure 2 memory stores, this can be used to store a session, send information between threads and so on. The ttl property specify's how long a key exists in the store in milliseconds.

Getting access to a service from within the workflow can be done via the following


NOTE in order to enable / change session service provider the trustbuilder application needs to be restarted on application server level.

You can create your own service by setting the type to the fully qualified name of your java class. Requirements for this class are:

  • It should have a public constructor
  • Functions that need to be called in the workflow should work with primitives and return primitives.
  • Setters and getters can be used to change the internal state of the service.
Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.