<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    javaGrowing

      BlogJava :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理 ::
      92 隨筆 :: 33 文章 :: 49 評論 :: 0 Trackbacks

    ?

    一?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:

    • Application server
    • Message server
    • SNA Gateway
    • System log send demon
    • System log receive demon

    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

    posted on 2008-02-27 08:46 javaGrowing 閱讀(628) 評論(0)  編輯  收藏 所屬分類: sap
    主站蜘蛛池模板: 成年丰满熟妇午夜免费视频 | 亚洲成人午夜电影| 一区二区3区免费视频| 国产一区二区三区在线免费| 亚洲中文字幕日本无线码 | 最新免费jlzzjlzz在线播放| 77777亚洲午夜久久多喷| 曰批全过程免费视频网址| 亚洲国产日韩在线成人蜜芽| 18禁黄网站禁片免费观看不卡| 久久久久亚洲av无码专区导航| 无码国产精品一区二区免费3p | 亚洲精品国产肉丝袜久久| 91精品免费高清在线| 亚洲日韩国产精品无码av| 97免费人妻无码视频| 亚洲免费综合色在线视频| 国产精品va无码免费麻豆| 免费视频成人国产精品网站 | 亚洲永久永久永久永久永久精品| 午夜视频在线免费观看| 亚洲18在线天美| 日本一道综合久久aⅴ免费| 一级毛片免费在线播放| 国产亚洲精品国产| 亚洲无砖砖区免费| 久久久久亚洲国产| 亚洲第一黄片大全| 中国一级全黄的免费观看| 久久亚洲AV成人无码国产 | 全部免费毛片在线| 国内永久免费crm系统z在线| 亚洲国产精品网站久久| 国产精品成人四虎免费视频| 巨胸喷奶水视频www免费视频| 亚洲国产成人久久精品影视| 免费无码精品黄AV电影| 日韩免费高清一级毛片| 亚洲一区二区在线视频| 国产又大又粗又硬又长免费| 99久久免费国产精精品|