Starting the tmboaserver through ASM

To create a new Service type and Service Instance use the procedure as described in Configuring ASM.

The sessions which are used most to start:

• Multiple occurrence, runs forever unless killed:
  • tmboaasmserver
• Unique occurrence:
  • job daemon (ttaad5206m000/ttaad5207m000) with start and stop function.
  • job (ttaad5203m000), only with start function.
  • tmboaserver, with start and stop function.

This table shows the information for the tmboaserver:

Service Type properties tab specify the name tmboaserver
On the Start Attributes tab
Executable Name	${BSE}/bin/bshell6.2
Executable Parameters	-server
Session Code	tmboaserver
Session Parameters	-d
On the Stop Attributes tab
Executable Name	/usr/bin/java
Executable Parameters	-Xrs -cp ${BSE}/java/ow.jar:${BSE}/java/ow3p.jar:${BSE}/java
Session Code	com.baan.owtools.BackendControl
Session Parameters	-d

This table contains the information for the server instance:

Service Instance Properties
Instance Name	Specify the appropriate instance name
Service Type	tmboaserver
Occurrence	Unique
Startup	Manual
User Name	bsp
Password	Specify the OS password of the user that you specified in the User Name field.
On the Start Attributes tab
Overrule Executable Parameter	Do not select
Extra Executable Parameter	-dbgjvmi
Overrule Session Parameter	Do not select
Extra Session Parameter	-busc <Buscomponent> -l log.tmboa -s
On the Stop Attributes tab
Overrule Executable Parameter	Do not select
Extra Executable Parameter	Do not select
Overrule Session Parameter	Do not select
Extra Session Parameter	-busc <Buscomponent> -action deactivate