Sun N1 Advanced Architecture for SAP Solutions 5.2.1 User's Guide

Customizing

This section describes additional customizing necessary for the N1 AA Deployer.


Note –

The necessary SPS parameterisation should have already been done during the general N1 AA setup. The parameters none.general.sps.* have been specified. For more information, see General Customizing.


SAP RFC Parameter

Purpose

Settings for SAP RFC communication.

Menu

Administration ⇒ Deployer ⇒ Customizing

Tasks for an initial basic setup

Mandatory

While creating or removing SAP Application Instances, the existing Logon and RFC Servers Groups of the SAP System might be modified. The action of creating adds the instance to the SAP Systems Logon or RFC Server Groups. The action of removing deletes the instance from the SAP Systems Logon or RFC Server Groups.

N1 AA uses the RFC parameters to communicate with the SAP system. This is true for all SAP systems in your N1 AA landscape. You have to provide the same user ID and password in every SAP system.

Table 5–1 SAP RFC Parameters

Parameter 

Description 

Example value 

none.deployment.saprfc.client

Logon client for RFC communication. 

000 

none.deployment.saprfc.password

Logon password for RFC communication. Password is stored encrypted in the N1 AA database. 

n1aapwd 

none.deployment.saprfc.timeout

Timeout value, in minutes, for RFC communication 

2 

none.deployment.saprfc.user

User for RFC communication. SAP user type communications (CPI-C) is sufficient.

n1aauser 


Note –

Regarding the previous parameters. You can add additional optional parameters by replacing none with servergroup. For example, servergroup.deployment.saprfc.user, where servergroup is the name of an existing server group. This overwrites the parameter value within the specified server group.


Timeout Parameter

Purpose

Settings the timeout values for Deployer actions

Menu

Administration ⇒ Deployer ⇒ Customizing

Tasks for an initial basic setup

Optional

This is where timeout values for Deployer actions are customized. The naming convention for these parameters is: none.deployment.generaltimeout.resourcetype.action. With:


Note –

You can customize timeouts for a dedicated resource by adding parameters while replacing resourcetype with the dedicated resourcename. For example, none.deployment.generaltimeout.P01CI.start defines the start timeout for the resource P01CI. It overwrites the generic type–specific start timeout for SAP Central Instances none.deployment.generaltimeout.SAPCentralInstance.start.


Table 5–2 Timeout Parameters

Parameter 

Description 

Example Value 

none.deployment.generaltimeout.GDS.isoffline

Timeout values, in minutes, for resources of type GDS.

1 

none.deployment.generaltimeout.GDS.isonline

 

1 

none.deployment.generaltimeout.GDS.start

 

5 

none.deployment.generaltimeout.GDS.stop

 

5 

none.deployment.generaltimeout.HAStoragePlus.isoffline

Timeout values, in minutes, for resources of type HAStoragePlus.

1 

none.deployment.generaltimeout.HAStoragePlus.isonline

 

1 

none.deployment.generaltimeout.HAStoragePlus.start

 

10 

none.deployment.generaltimeout.HAStoragePlus.stop

 

10 

none.deployment.generaltimeout.LogicalHost.isoffline

Timeout values, in minutes, for resources of type LogicalHost.

1 

none.deployment.generaltimeout.LogicalHost.isonline

 

1 

none.deployment.generaltimeout.LogicalHost.start

 

5 

none.deployment.generaltimeout.LogicalHost.stop

 

5 

none.deployment.generaltimeout.NfsMount.isoffline

Timeout values, in minutes, for resources of type NFSMount.

1 

none.deployment.generaltimeout.NfsMount.isonline

 

1 

none.deployment.generaltimeout.NfsMount.start

 

5 

none.deployment.generaltimeout.NfsMount.stop

 

5 

none.deployment.generaltimeout.NfsShare.isoffline

Timeout values, in minutes, for resources of type NFSShare.

1 

none.deployment.generaltimeout.NfsShare.isonline

 

1 

none.deployment.generaltimeout.NfsShare.start

 

5 

none.deployment.generaltimeout.NfsShare.stop

 

5 

none.deployment.generaltimeout.Oracle.isoffline

Timeout values, in minutes, for resources of type "Oracle".

1 

none.deployment.generaltimeout.Oracle.isonline

 

1 

none.deployment.generaltimeout.Oracle.start

 

10 

none.deployment.generaltimeout.Oracle.stop

 

10 

none.deployment.generaltimeout.SapAppServer.Install

Timeout values, in minutes, for resources of type AppServer.

10 

none.deployment.generaltimeout.SapAppServer.isoffline

 

1 

none.deployment.generaltimeout.SapAppServer.isonline

 

1 

none.deployment.generaltimeout.SapAppServer.start

 

10 

none.deployment.generaltimeout.SapAppServer.stop

 

10 

none.deployment.generaltimeout.SapCentralInstance.isoffline

Timeout values, in minutes, for resources of type CentralInstance.

1 

none.deployment.generaltimeout.SapCentralInstance.isonline

 

1 

none.deployment.generaltimeout.SapCentralInstance.start

 

10 

none.deployment.generaltimeout.SapCentralInstance.stop

 

10 

none.deployment.generaltimeout.SapEnqueueServer.isoffline

Timeout values, in minutes, for resources of type EnqueueServer

1 

none.deployment.generaltimeout.SapEnqueueServer.isonline

 

1 

none.deployment.generaltimeout.SapEnqueueServer.start

 

5 

none.deployment.generaltimeout.SapEnqueueServer.stop

 

5 

none.deployment.generaltimeout.SapMessageServer.isoffline

Timeout values, in minutes, for resources of type MessageServer.

1 

none.deployment.generaltimeout.SapMessageServer.isonline

 

1 

none.deployment.generaltimeout.SapMessageServer.start

 

5 

none.deployment.generaltimeout.SapMessageServer.stop

 

5 


Note –

Change all *.isonline and *.isoffline parameter values from 1 to 5. This is a absolutely necessary. Make these changes immediately after installation and before you use N1 AA.

If you see messages like ... Got timeoutout from db ..., you might have to adjust the related timeout parameters.