Start of Content Area

Object documentation Instance Profiles  Locate the document in its SAP Library structure

Definition

Instance profiles provide an application server with additional configuration parameters that complement the settings in the default profile. Typically, these parameter settings adapt the instance according to the desired resources. They also define the available instance resources (main memory, shared memory, roll memory, and so on), and how to allocate memory to the SAP application buffers.

Example

Example of a typical instance profile for a double-stack instance:

#.***************************************************************
#.*                                                             *
#.* Instance profile PMN_DVEBMGS00_WDFN00148651A                *
#.*                                                             *
#.*       Version                 = 000011                      *
#.*       Generated by User       = NAKE                        *
#.*       Date of Generation      = 04.01.2007 , 13:31:26       *
#.*                                                             *
#.***************************************************************
SAPSYSTEMNAME = PMN
#parameter created                          by: NAKE    27.12.2005 17:20:32
rsdb/ntab/entrycount = 10000
#parameter created                          by: NAKE    27.12.2005 17:20:04
rsdb/ntab/ftabsize = 10000
SAPGLOBALHOST = WDFN00148651A
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
DIR_PROFILE = $(DIR_INSTALL)\profile
_PF = $(DIR_PROFILE)\PMN_DVEBMGS00_WDFN00148651A
jstartup/trimming_properties = off
jstartup/protocol = on
jstartup/vm/home = C:\j2sdk1.4.2_09
jstartup/max_caches = 500
#parameter created                          by: NAKE    27.12.2005 17:27:38
alert/MONI_SEGM_SIZE = 20000000
jstartup/release = 700
jstartup/instance_properties = $(jstartup/j2ee_properties);$(jstartup/sdm_properties)
j2ee/dbdriver = C:\sapdb\programs\runtime\jar\sapdbc.jar
PHYS_MEMSIZE = 128
#old_value: 3                             changed: KRIEGER 27.04.2006 15:59:26
rdisp/wp_no_dia = 4
#old_value: 2                             changed: KRIEGER 19.12.2006 11:26:35
rdisp/wp_no_btc = 3
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_libpath = $(DIR_EXECUTABLE)
exe/j2ee = $(DIR_EXECUTABLE)\jcontrol$(FT_EXE)
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
icm/server_port_0 = PROT=HTTP,PORT=80$$
#----------------------------------------------------------------
# SAP Messaging Service parameters are set in the DEFAULT.PFL
#----------------------------------------------------------------
ms/server_port_0 = PROT=HTTP,PORT=81$$
rdisp/wp_no_enq = 1
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 0
rdisp/wp_no_spo = 1
rsdb/dbid = PMN
dbs/ada/schema = SAPPMN
#------------------------------------------------------------
# Jcontrol: Migrated Profile Parameter
#      create at Wed Nov 30 16:29:57 2005
#------------------------------------------------------------
j2ee/instance_id = ID0037994
#------------------------------------------------------------
alert/cache/size_MB = 10
mpi/buffer_size = 32768
mpi/total_size_MB = 20
abap/buffersize = 100000
alert/GREEN_ALERTS = 1

icm/keep_alive_timeout = -1
icm/host_name_full = wdfn00148651a.wdf.sap.corp

#------------------------------------------------------------------
# Copy SAP Executables
#------------------------------------------------------------------
Start_Program_00 = immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)
#------------------------------------------------------------------
# Start ABAP database
#------------------------------------------------------------------
_DB = $(DIR_CT_RUN)\strdbs.cmd
Start_Program_01 = immediate $(_DB) PMN
#------------------------------------------------------------------
# Start SAP messaging service
#------------------------------------------------------------------
_MS = $(DIR_EXECUTABLE)\msg_server$(FT_EXE)
Start_Program_02 = local $(_MS) pf=$(_PF)
#------------------------------------------------------------------
# Start application server
#------------------------------------------------------------------
_DW = $(DIR_EXECUTABLE)\disp+work$(FT_EXE)
Start_Program_03 = local $(_DW) pf=$(_PF)
#------------------------------------------------------------------
# Start internet graphics server
#------------------------------------------------------------------
_IG = $(DIR_EXECUTABLE)\igswd$(FT_EXE)
Start_Program_04 = local $(_IG) -mode=profile pf=$(_PF)
rsdb/dbid = PMN
dbs/ada/schema = SAPPMN

You can choose any name for an instance profile. The SAP naming convention has the following structure: <SID>_<instance name>_<host name>.

This graphic is explained in the accompanying text Profiles start page

 

End of Content Area