Static data in a Mediation Flow

How can we store static content not specific to a single transaction in a
Mediation FLow.<br />
<br />
Details:<br />
<br />
   My mediation flow transmits SOAP requests from one EndPoint to other.<br
/>
<br />
   Each SOAP request needs some static data before accessing the target
Endpoint.  Where do I store this static data?  Is there something like a session
or Mediation FLow context that can hold static objects accessible by multiple
SOAP requests?<br />
<br />
  Can I use SMO Context in this scenario? In my view, we cannot as, SMO is
request specific.<br />
<br />
Thanks,<br />

There are a number of potential solutions to this with varying degrees of
functionality, complexity and elegance.<br />
<br />
The first one that comes to mind is to create a "caching service".  
This is something with a Service Interface that when called can create,
retrieve, updated and delete data.  The service could be implemented by an EJB
or POJO using JDBC or other Database technology to persist the data.  The
service can then be invoked in the middle of a Mediation Flow using the Service
Invoke primitive.<br />
<br />
If you have WPS available to you, the service might be implemented as a Business
Rule.<br />
<br />
If you don't want to create a service, consider using a Custom Mediaition to
make JDBC calls from within the Java code of the Custom Mediation.<br />
<br />
How "static" is the content you need?  Is it read-only for days,
weeks, months?  How often does it change?  How would you like it to be changed? 
What size is the size of the data?  Is it one piece of static content or many
pieces?<br />
<br />