If you want to use a transactional ASE database service in a business process service, you must disable the Autocommit option in the database service editor, deploy the business process service, and then reconfigure the Connection Cache created in EAServer Manager. You can also select the ASE XA driver when creating a connection profile for ASE. This automatically sets the required properties.
You cannot set up an ASA database service to be transactional.
To set up a transactional database service:
To edit the ASE database service do the following:
Open the database service.
Deselect the Autocommit option in the Operations section of the service editor.
Save the service.
Deploy the business process service.
To reconfigure the EAServer Connection Cache properties:
Open EAServer Manager.
In the tree view, expand EAServer Manager and select the machine that runs the business process service.
Double-click Connnection Caches to display the cache list in the right pane.
Open the Connection Cache dialog box.
Double-click the <business process service name>.
Specify the following properties and then click OK:
Restart EAServer. Right-click Jaguar Manager and select Shutdown and Start.
Reconnect to EAServer using the connection profile in Enterprise Explorer.
To set up a transactional database service for other database types (Oracle), ensure the database is currently configured to handled XA transactions. You must also have the correct DLL or Class identified in EAS|Connection Cache Properties. See the EAServer product documentation on the Sybase WorkSpace bookshelf for more detailed instructions.
Setting Up a Nontransactional Adaptive Server Anywhere Database Service
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com