Starting Service Manager without Java Web-Start
OSSera Service Manager is built using the Java programming language. It can run on any operating system supporting JRE1.5 version or later. On Microsoft Windows, you can start the system by either clicking on the ServiceManager icon or by typing in ServiceManager in a DOS command window. Before starting the system, please make sure that orbd is running. Please use the orbd.bat file located under the installation directory’s bin subdirectory to ensure that the proper orbd database is used. If an incorrect orbd database is used, the system will most likely not be able to operate properly. It is strongly suggested to put the orbd.bat in the system startup list so that it will be executed during the startup process. There is also a script to install the Service Manager server as a persistent CORBA server to avoid any manual startup of the server. Please make sure you have executed it once after the orbd is started. Once it is running, the Service Manager server will be registered in the orbd. As long as the orbd is running with the correct database, it will not need to be registered again therefore the script only needs to be executed once.
Before starting the system, please make sure the database server is running properly.
Start system on Microsoft Windows
- Change the current directory to the installation directory’s Service Manager subdirectory
- Type in “ServiceManager” in the DOS command window or double click on the “ServiceManager” icon in Windows Explorer.
Start system on Linux or Unix
- Change current directory to the installation directory’s Service Manager subdirectory
- Type in “ServiceManager” in shell or double click on “ServiceManager” icon in the file browser.
To log into the system, type in the User Name, Password and Server Name if the server name is incorrect.
Note there is a default user name and password which is not printed here.
We strongly suggest you configure your own administrator user name and password then delete the default one. OSSera and the partner/distributer of OSSera products are not responsible for any security issues due to the default user.