To save the states of business objects, the E2E Persistent State engine needs a database. This page explains the preliminary steps to get started with E2E Persistent State databases.

...

In its default configuration, E2E Persistent State does not need any additional components or installation steps. SQLite, an embedded, small footprint, relational database is provided with the Base firmware package. The database model is automatically initialized upon start-up and updated if a new firmware version should require it.

With SQLite, a separate database file is kept in the home directory of the deployed service instance. The filename is pstate.db and the command shell provided by the SQLite project (http://www.sqlite.org) can explore its contents. There are also several free or inexpensive visual management tools. We recommend SQLite2008 Pro Enterprise Manager of OsenXPSuite (http://www.osenxpsuite.net/?xp=3).

Other RDBMS

E2E Persistent State does work with any other RDBMS platform that is supported by the Bridge using the <<SQLAdapter>>. The following RDBMS are tested and supported: Oracle, Microsoft SQL Server and MySQL (since xUML Runtime 6.0.91.1).

Like with normal use of RDBMS in E2E the Bridge, the connection parameters to the database are configured as part of the component diagram. A database user and an empty instance/schema have to be created on the RDBMS before it can be accessed.
With these preconditions, the database model is automatically initialized upon start-up and updated if a new firmware version should require it.

...

In the specification dialog of the E2E CompositexUML service composite, you can configure the persistent state engine.

Figure: Specification of E2E xUML Service Composite PurchaseOrderExample

...

A new alias can be created during the Creation of a Component Diagram or manually, as described on Backend Components.