Using the sample server
Operational Decision Manager comes with a sample server. The server provides a preconfigured default execution environment for samples and tutorials.
The sample server is a WebSphere® Liberty server instance. You build it in the Liberty application server that you indicated when you installed Operational Decision Manager. It uses the JDK that comes with Operational Decision Manager. You can find the JDK in <InstallDir>/jdk. The sample server uses the H2 database.
When you deploy a RuleApp from the Samples Console, you get a message to use the same JDK for Rule Designer and the application server. The same JDK is used for the Samples Console and the sample server.
You can install the sample server on distributed platforms only. You use it with samples and tutorials that require an application server. You do not require the server for most Rule Designer samples and tutorials. Some Rule Execution Server samples include instructions for using them on other application servers.
You can start and stop the sample server by using start menu shortcuts, a command prompt, or commands in the Samples Console in Rule Designer. The Samples Console also displays trace messages that are sent by the sample server.
Single sign-on (SSO) authentication is activated in the sample server. With SSO, a user can log in once and use several applications without having to log in again. For example, you can work as an administrator in Decision Center and Rule Execution Server by logging in with odmAdmin as your user name and password.
If you use different login credentials for the applications on the sample server to do certain samples and tutorials, for example, you can get an error message when you switch applications. To avoid this problem, you must sign out of one console to sign in to another.