Configuring the ASM Server

Host name:

Specify the name of the server which applications you want to control with the ASM.

Port number

Specify the port number on which the server’s ASM receives commands. The search path determines the server’s ASM port number:

• The port number you specify at startup of the ASM.
• If you do not specify a port number at startup, ASM uses the port number defined for the logical name BaanASM, in the file etc/services.
• If no port number is specified, ASM uses the default port number 7250.

  If the value you enter in this field does not correspond to the server’s ASM port number, the MMC cannot command the server’s ASM.

Time-out value(s)

Specify the MMC’s time-out value, in seconds, for communication with the ASM daemon. The default value is thirty seconds. For wide area networks, or if your ASM runs on a heavily loaded server, you must increase this value.

• Generic service types: Usable for every environment.
• Specific service types: Limited to a single environment.

In this example, a service is created to stop and start the printer daemon.

Specify the executable that starts an LN application service, for example, a command to start the printer daemon.

Executable Name

The name of the executable that starts the application service, for example, the command to start the printer daemon, ${BSE}/bin/pdaemon6.2

Executable Parameters

The service or session starts with the parameters you specify here. You can also leave this field blank.

Session Code

Specify the session code of the session that the ASM must start. For example, the Activate Job Daemon (ttaad5206m000) session, to start the job daemon.

Session Parameters

Overrules the default start parameters. The service or session will be started with the parameters you specify here. You can also leave this field empty.

Specify this information:

Executable Name

The name of the executable that stops the application service, for example, the command to stop the printer daemon, ${BSE}/bin/pdaemon6.2

Executable Parameters

The service or session stops with the parameters you fill in here. You can also leave this field blank. To stop the printer daemon specify -k.

Session Code

Specify the session code of the session that the ASM must start to stop.

Session Parameters

Overrules the default stop parameters. You can also leave this field empty.

The specific service types are limited to a single environment and have precedence over generic service types if both exist with the same name. You do not have to specify the Stop Attributes.

You have now predefined in XML files the application services that the ASM can start, and sometimes, stop. The services that you defined to be started, and for unique instances only, stopped by the ASM, are called instances. To work with the services, you must configure the service instances.

• The environment Name. This name is shown in the left pane of the MMC console.
• The correct path name to the LN environment where you want the service type to start.

Instance Name

Specify the appropriate instance name

Service Type

Select a service type.

Occurrence (Multiple)

Select the Multiple occurrence, when you can have multiple occurrences of the instance’ s application service running simultaneously. The ASM can start a multiple occurring instance’ s application service when requested by a user of an external software module. The user, and not the ASM, stops the application service using the external software module. To communicate back to the ASM server, Multiple instances must have an integration with ASM.

Occurrence (Unique)

Select the Unique occurrence, when you can only run one occurrence of the instance’ s application service at a time. You can use the ASM to start or stop a unique occurring instance’ s application service. For example, the ASM can start and stop a job daemon.

Stop and disable the Infor manager’s control of the job daemon service in the BSE when using the ASM to start and stop a job daemon.

Startup (Automatic)

When you start the ASM, the ASM automatically starts the instance’s application service. You can still manually command the ASM to stop and restart the instance’s application service.

Startup (Manual)

When a user sends the start command to the ASM, the instance’s application service starts.

User Name

Specify the OS name of the user to whom the system registers the instance’s application service, when started by the ASM. If this user name is not a valid user name on the system, the ASM will not start the application service.

Password

Enter the OS password of the user that you entered in the User Name field. If the password is not valid, the ASM will not start the application service. Ensure to update this field whenever the OS password changes.

Retype Password

Re-enter the OS password of the user that you entered in the User Name field.

To check the data before you send the data directly to the server, you can use the consistency check. In this case, you can test the data and decide whether to save the data to the server.

Otherwise the server content is always refreshed without testing. On the shortcut menu that appears, point to All Tasks and click Verify Consistency.

If you decide to save the data to the server, choose to save all your settings. Select the host name and right-click the mouse. On the shortcut menu that appears, point to All Tasks and click Save Service Types and Instances to ASM Server.

After you change the configuration settings, you must always restart your ASM Server to let the changes take effect. You can stop and restart the server on UNIX with the rc.stopasm and rc.startasm scripts.

You can also use these commands:

# <home directory>/bin/asm_srv -home <home directory> -k

# <home directory>/bin/asm_srv -home <home directory>

On Windows, you can restart the ASM Service with Microsoft’s Services Manager. Click Start > All Programs > Control panel > Administrative Tools > Services.

For more information, see Starting the ASM server.