一 Profiles路径
SAP profiles are stored in a special file directory. This directory can be made accessible from all hosts depending on current needs:
UNIX systems : /usr/sap/<SID>/SYS/profile
Windows NT systems: \usr\<SID>\sys\profile\
( <SID> = SAP system name and <SAPGLOBALHOST> = name of the NT machine on which the global profile directory is physically located)
二 Profiles命名规则
In R/3 Releases 2.1x / 2.2x, the profiles were generated with the names:
START_<instancename> and <SID>_<instancename> .
From Release 3.0A, the profiles are generated with the names: START_<instancename>_<hostname> and <SID>_<instancename>_<hostname> .
The 'startsap' script first looks for profiles that end with _<hostname> . If these profiles do not exist, the names from the Releases 2.1x / 2.2x are used.
三 Profiles类型
3.1 Default Profiles Definition
If you want to assign the same parameter value for all application servers (such as the name of the database host, or the host on which the message server is running), enter it in the default profile. In general, you can list any parameter you like here.
SAP recommends that you use the following values:
Parameter Definition | Parameter Name in Profile |
Name of the database host | SAPDBHOST |
Name of the update server | rdisp/vbname |
Name of the enqueue server | rdisp/enqname |
Name of the server for handling background processing events | rdisp/btcname |
Name of the computer on which the message server is running | rdisp/msname |
Name of the TCP service under which the message server can be reached | rdisp/msserv |
Name of the computer on which the SNA Gateway is running | rdisp/sna_gateway |
Name of the TCP Service under which the SNA Gateway can be reached | rdisp/sna_gw_service |
You cannot choose a name for the default profile. It is always called DEFAULT.PFL . The default profile, like all other profiles, is located in the global profile directory of the SAP System. For example, under UNIX it is located in the directory /usr/sap/<SID>/SYS/profile ( <SID> = SAP System name). There is always one active default profile.
SAPDBHOST = hs0011
DIR_ORAHOME = /oracle/BIN
rdisp/mshost = hs0311
rdisp/vbname = hs0311_BIN_53
rdisp/enqname = hs0311_BIN_53
rdisp/btcname = hs0002_BIN_53
rdisp/sna_gateway = is0001
rdisp/sna_gw_service = sapgw00
3.2 Start Profiles
When you start an SAP instance on a host, the start profile defines which SAP services are started (message server, dialog, gateway or enqueue process. for example). The startsap program is responsible for starting these service processes,
The processes that can be started include:
Apart from the general profile parameters, such as the name of the SAP System ( SAPSYSTEMNAME ), instance number ( SAPSYSTEM ) and name of the SAP instance ( INSTANCE_NAME ), the only parameter names that are permitted in a start profile are:
Execute_xx (xx = 00-99) : To start operating system commands, which prepare the SAP System start. For example, you can use this parameter to start the SAP-related database or to set up links to executables on UNIX platforms.
Start_Program_xx (xx = 00-99): To start an SAP instance, for example, on an application server.
Stop_Program_xx (xx = 00-99): To start an operating system command or SAP program after the SAP instance was stopped. For example, the halting or removal of shared memory areas that were used by the SAP System.
The number xx defines the execution sequence. The programs specified in Execute_ parameters are executed before the programs listed in the Start_Program parameters. After the SAP instance has been stopped, the programs specified in the Stop_Program parameters are started. Here is an example of a start profile used to start a message server, an application server and an SNA gateway:
#.***************************************************************
#.* Start profile START_DVEBMG47
#.*
#.* Version = 000003
#.* last changed by = WATT
#.* last changed on = 21.03.1995, 15:05:19
#.***************************************************************
SAPSYSTEMNAME = K11
INSTANCE_NAME = DVEBMG47
#----------------------------------------------------------------
# start message server
#----------------------------------------------------------------
_MS = ms.sapK11_DVEBMG47
Execute_01 = local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS)
Start_Program_01 = local $(_MS) pf=$(DIR_PROFILE)/K11_DVEBMG47
#----------------------------------------------------------------
# start application server
#----------------------------------------------------------------
_DW = dw.sapK11_DVEBMG47
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/disp+work $(_DW)
Start_Program_02 = local $(_DW) pf=$(DIR_PROFILE)/K11_DVEBMG47
#----------------------------------------------------------------
# start SNA-Gateway
#----------------------------------------------------------------
3.3 Instance Profiles
Instance profiles provide an application server with additional configuration parameters to complement the settings values from 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.
To start application servers on several computers using identical parameter settings, you can use a single instance profile. It is generally not necessary for each application server to have its own instance profile. Instance profiles are also called system profiles.
Below is a typical instance profile:
#.*************************************************
#.* Instance profile BIN_DVEBMG53 *
#.* Version = 000005 *
#.* Generated by user = BLOCHING *
#.* Date generated = 04.08.1995, 11:10:35 *
#.*************************************************
INSTANCE_NAME = DVEBMG53
SAPSYSTEM = 53
SAPSYSTEMNAME = BIN
abap/buffersize = 40000
abap/programs = 600
ipc/shm_psize_10 = 15000000
ipc/shm_psize_14 = 0
ipc/shm_psize_17 = 0
ipc/shm_psize_18 = 0
ipc/shm_psize_19 = 0
ipc/shm_psize_40 = 17000000
rdisp/PG_MAXFS = 4096
rdisp/PG_SHM = 1000
rdisp/ROLL_MAXFS = 16384
rdisp/ROLL_SHM = 200
rdisp/btctime = 60
rdisp/wp_no_dia = 5
rdisp/wp_no_enq = 1
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 1
分享到:
相关推荐
SAP-Basis-日常维护(basis经典教程SAP-Basis-日常维护(basis经典教程SAP-Basis-日常维护(basis经典教程
根据提供的文件信息,我们可以深入探讨SAP Basis的相关知识点,包括其配置、技术问题以及与之相关的事务代码和表格。下面将详细介绍这些知识点。 ### SAP Basis 配置与技术相关问题 #### 1. SAP Basis 概述 SAP ...
collections-of-the-basis-of-compute-system-2nd.bin
《PyPI官网下载jtitor_basis-0.1.9.tar.gz——深入理解Python库与云原生技术》 PyPI(Python Package Index)是Python开发者的重要资源库,它提供了丰富的Python软件包,使得开发者能够方便地下载、安装和分享代码...
很实用的文档,对basis讲的很详细,并且内容非常全面
基础通用Binomial LLC 超压缩GPU纹理编解码器的绑定basis-universal功能可以分为两类: 编码:压缩和编码纹理(可选地在单个文件/二进制Blob中组合多个图像和Mipmap层) 转码:将纹理解压缩为GPU友好的压缩格式。...
在SAP系统中,BASIS授权维护是确保系统安全性和数据保护的关键环节。每个用户在每个客户端都拥有一个用户主记录(User Master Record),这个记录包含了用户的所有相关信息,包括他们可以使用的权限设置。这些权限...
本文探讨了一种新的计算机断层扫描(Computed Tomography, CT)方法——局部基函数法(Local Basis-Function Approach)。这种方法通过将重建图像表示为一组局部支持区域内的基函数线性组合来提高CT重建算法的计算...
基于基追踪(basis pursuit)对信号进行稀疏表示的算法
SAP BASIS 系统管理员的日常使用事务代码 SAP BASIS 系统管理员需要掌握的日常使用事务代码包括: 1. DB02:反省表空间状况,包含表跟索引的最大扩展跟下次扩展,反省丧掉的索引等。 2. DB12:反省全部备份形态...
标题中的“basis-matrix.rar”是一个压缩包文件,包含了与DCT(离散余弦变换)和压缩感知相关的矩阵资源。DCT是一种重要的数学工具,广泛应用于图像和音频的压缩,如JPEG和MP3编码中。它将信号或图像从原始空间转换...
Top 10 Matlab Do’s, Don’ts, and How Tos
官方版本,亲测可用
官方版本,亲测可用
官方版本,亲测可用
官方版本,亲测可用
官方版本,亲测可用
官方版本,亲测可用
官方版本,亲测可用
官方版本,亲测可用