Comunication_Server.pdf

%&7KH6$3&RPPXQLFDWLRQV6HUYHU

5HOHDVH %

+

(

/

3

%

&

6

5

9

&

6

%&7KH6$3&RPPXQLFDWLRQV6HUYHU 6$3$*

-XQH

&RS\ULJKW Copyright 1998 SAP AG. All rights reserved.No part of this brochure may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed withoutprior notice.SAP AG further does not warrant the accuracy or completeness of the information, text, graphics,links, or other items contained within these materials. SAP AG shall not be liable for any special,indirect, incidental, or consequential damages, including without limitation, lost revenues or lostprofits, which may result from the use of these materials. The information in this documentation issubject to change without notice and does not represent a commitment on the part of SAP AG forthe future.Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.Microsoft, WINDOWS, NT, EXCEL and SQL-Server are registered trademarks ofMicrosoft Corporation.IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390,AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.OSF/Motif is a registered trademark of Open Software Foundation.ORACLE is a registered trademark of ORACLE Corporation, California, USA.INFORMIX-OnLine IRU6$3 is a registered trademark of Informix Software Incorporated.UNIX and X/Open are registered trademarks of SCO Santa Cruz Operation.ADABAS is a registered trademark of Software AG.SAP, R/2, R/3, RIVA, ABAP/4, SAP ArchiveLink, SAPaccess, SAPmail,SAPoffice, SAP-EDI, R/3 Retail, SAP EarlyWatch, SAP Business Workflow, ALE/WEB,Team SAP, BAPI, Management Cockpit are registered or unregistered trademarks of SAPAG.

,FRQV

,FRQ 0HDQLQJ

Caution

Example

Note

6$3$* %&7KH6$3&RPPXQLFDWLRQV6HUYHU

-XQH

&RQWHQWV

%&7KH6$3&RPPXQLFDWLRQV6HUYHU %&7KH6$3&RPPXQLFDWLRQV6HUYHU %DVLFV 1DPLQJ&RQYHQWLRQV &RPSDWLELOLW\ )XQFWLRQVRIWKH&RPPXQLFDWLRQV6HUYHU ,PSOHPHQWDWLRQ +RZWKH6$3&RPPXQLFDWLRQV6HUYHU:RUNV 7KH&RQILJXUDWLRQ)LOH 7KH8VHU,QWHUIDFH 7KH&RPPXQLFDWLRQV&RPSRQHQWV +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV 2SHUDWLQJ6\VWHPV 7KH&RQQHFWLRQWR6$36\VWHPV &RPPXQLFDWLRQV&RPSRQHQWV 7KH&RQWURO&RPSRQHQW LVN&DSDFLW\ ,QVWDOODWLRQ 2YHUYLHZ ,QVWDOODWLRQ8QGHU81,; ,QVWDOODWLRQ8QGHU26 0RGLI\LQJWKH&RQILJXUDWLRQDQG&RPPXQLFDWLRQV)LOHV ,QVWDOOLQJDQG&RQILJXULQJ&RPPXQLFDWLRQV6\VWHPV 3UHSDUDWLRQLQWKH6$36\VWHP 7KH&RQILJXUDWLRQ)LOH6$3&200&)* 2YHUYLHZ 6WUXFWXUHRIWKH&RQILJXUDWLRQ)LOH 75$&(3DUDPHWHU*URXS &KDQQHOV$FFHVVWRWKH&RPPXQLFDWLRQV&RPSRQHQWV +RZDUHRFXPHQWV$OORFDWHGWR 6$3FRPP6FKHGXOH6WDWHPHQWV 7HVWLQJWKH&RQILJXUDWLRQDWD &RQILJXUDWLRQ([DPSOHV &RQILJXUDWLRQ([DPSOHIRU2GH[3&DQG([SHGLWH &RQILJXUDWLRQ([DPSOHIRU723&$// &RQILJXUDWLRQLQWKH6$36\VWHP 2YHUYLHZ $FWLYDWLQJ/RJJLQJ7DEOH7$% &KHFNLQJ/RJRQ7LPHV7DEOH76.: &RQILJXULQJ7HOHFRPPXQLFDWLRQV$SSOLFDWLRQV


-XQH

7KH&RQWURO&RPSRQHQW6&% 2YHUYLHZ 6&%VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH 3(5)2503DUDPHWHU*URXS 7KH5RXWLQJ3DUDPHWHU*URXS 2SHUDWLQJWKH&RPPXQLFDWLRQV6HUYHU 6WDUWLQJWKH&RPPXQLFDWLRQV6HUYHU &ORVLQJWKH&RPPXQLFDWLRQV6HUYHU 1RWHVRQ7HVWLQJDQG3UREOHP$QDO\VLV &RQQHFWLRQWR6$36\VWHPV 2YHUYLHZ +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV6$36\VWHPV 7KH&RPPXQLFDWLRQV&RPSRQHQW6$3 6$3VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH &KDUDFWHU6HWVDQG&RGH3DJHV 7HVWLQJWKH&RQQHFWLRQ 1RWHVRQ3UREOHP$QDO\VLV &RQQHFWLRQWR2(; 7KH&RPPXQLFDWLRQV6\VWHP2(; +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWVIRU2(; 7KH&RPPXQLFDWLRQV&RPSRQHQW2; 2;VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH 6$3VSHFLILF$VSHFWVIRU2(;2SHUDWLRQ 1RWHVRQ7HVWLQJDQG3UREOHP$QDO\VLV2(; &RQQHFWLRQWR(;3(,7( 7KH&RPPXQLFDWLRQV6\VWHP(;3(,7( +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV(;3(,7( 7KH&RPPXQLFDWLRQV&RPSRQHQW(;3 (;3VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH 6$3VSHFLILF$VSHFWVIRU(;3(,7(2SHUDWLRQ 1RWHVRQ7HVWLQJDQG3UREOHP$QDO\VLV(;3(,7( %&7KH6$3&RPPXQLFDWLRQV6HUYHU 7KH&HQWUDO&RPPXQLFDWLRQV6\VWHP +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV 7KH&RPPXQLFDWLRQV&RPSRQHQW66: &3,&&RQILJXUDWLRQ 66:VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH 6$3VSHFLILF$VSHFWVRI6RIW6ZLWFK2SHUDWLRQ 1RWHVRQ7HVWLQJDQG3UREOHP$QDO\VLV6RIW6ZLWFK &RQQHFWLRQWR26,/,1.; 7KH26,/,1.;&RPPXQLFDWLRQV6\VWHP +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWVIRU26,/,1.; 7KH&;&RPPXQLFDWLRQV&RPSRQHQW &;VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH 6$3VSHFLILF$VSHFWVRI26,/,1.;2SHUDWLRQ


-XQH

1RWHVRQ7HVWLQJDQG3UREOHP$QDO\VLV26,/,1.; &RQQHFWLRQWR723&$// 7KH723&$//&RPPXQLFDWLRQV6\VWHP +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWVIRU723&$// 7KH&RPPXQLFDWLRQV&RPSRQHQW723 723VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH 6$3VSHFLILF$VSHFWVRI723&$//2SHUDWLRQ 1RWHVRQ7HVWLQJDQG3UREOHP$QDO\VLV723&$// &RQQHFWLRQWR*DPPD)D[ 7KH*DPPD)D[&RPPXQLFDWLRQV6\VWHP +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV 7KH*$0&RPPXQLFDWLRQV&RPSRQHQW *$0VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH ,QVWDOODWLRQ &RQQHFWLRQYLD$33/,&207 7KH)LOH,QWHUIDFH$33/,&207 +DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV &RPPXQLFDWLRQV&RPSRQHQW$33 ,QVWDOODWLRQ $33VSHFLILF(QWULHVLQ6$3FRPP&RQILJXUDWLRQ)LOH ,QWHUIDFH6SHFLILFDWLRQ $33/,&20LUHFWRULHV $33/,&205HTXHVWV 7UDQVPLVVLRQ5HTXHVWV &RPSOHWHG7UDQVPLVVLRQ5HTXHVWV 5HFHSWLRQ5HTXHVWV 7KH&RPPXQLFDWLRQV&RPSRQHQW767 %DVLFV 767VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH 6$3VSHFLILF$VSHFWVIRU7672SHUDWLRQ 767VSHFLILF/RJ(QWULHV 6$3FRPPHYHORSPHQW/LEUDU\ 2YHUYLHZ 6FRSHRI3ULFH/LVW&RPSRQHQW 7KH6WUXFWXUHDQG7DVNVRID&RPPXQLFDWLRQV&RPSRQHQW 0HVVDJH)ORZLQ6$3FRPP 0HVVDJHDQG6WDWXV3URFHVVLQJLQ6$3FRPP 3URJUDPPLQJ:LWKWKH6$3FRPPHYHORSPHQW/LEUDU\ ,QLWLDOL]DWLRQ 6(15(&(,9(DQG)81&7,215HTXHVWV 7HUPLQDWLRQ &UHDWLQJD6$3FRPP*UDPPDU)LOH 7HVWLQJD&RPPXQLFDWLRQV&RPSRQHQW HVFULSWLRQRIWKH6$3FRPP$3, )XQFWLRQVDQG3DUDPHWHUVRIWKH6$3FRPP$3,


-XQH

0HVVDJH$WWULEXWHV 6$35HWXUQ&RGHVIRU0HVVDJH7UDQVPLVVLRQ &RPSLOLQJDQG/LQNLQJWKH([DPSOH3URJUDP ([DPSOH&RQILJXUDWLRQ :RUNLQJ:LWKWKH*UDSKLFDO,QWHUIDFH 7KH*UDSKLFDO,QWHUIDFH%DVLFV LVSOD\LQJ&KDQQHOUHODWHG$FWLYLWLHV 8VLQJWKH6$3FRPP0HQX%DU 7KH6$3FRPPLUHFWRU\7UHH 2YHUYLHZ 7KH6$3FRPP5RRWLUHFWRU\ 7KH6$3FRPP6\VWHPLUHFWRU\ (7&LUHFWRU\ 7KH&RPSRQHQWLUHFWRULHV 7KH6$3FRPP$X[LOLDU\3URJUDPV 2YHUYLHZ $QDO\]LQJ6$3FRPP3DUDPHWHU)LOHVVFPDFWO 7HVWLQJD6HULDO,QWHUIDFHVFPDV\Q &KHFNLQJWKH&RQILJXUDWLRQDWDVFPFIJFF $QDO\]LQJ6$3FRPP/RJ)LOHVVFPORJ 6$3FRPP0RQLWRUVFPPRQ 0RYLQJ)LOHVVFPPRYH 3HUIRUPLQJ$FWLRQVVFPSHUIP 7HVWLQJWKH1HWZRUN/LQNWRWKH6$36\VWHPVFPSLQJ LVSOD\LQJ6$3FRPP)LOHVVFPTXHXH 5HRUJDQL]LQJ6$3FRPP)LOHVVFPUHRUJ 6WRSSLQJWKH&RPPXQLFDWLRQV6HUYHUVFPVWRS


-XQH




-XQH

%&7KH6$3&RPPXQLFDWLRQV6HUYHUThe SAP communications server allows EDI, Mail and telecommunications documents to beexchanged between SAP Systems (R/2 and R/3) and external communication partners.%DVLFV>3DJH@

+DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV>3DJH@

,QVWDOODWLRQ>3DJH@

7KH&RQILJXUDWLRQ)LOH6$3&200&)*>3DJH@

&RQILJXUDWLRQLQWKH6$36\VWHP>3DJH@

7KH&RQWURO&RPSRQHQW6&%>3DJH@

&RQQHFWLRQWR6$36\VWHPV>3DJH@

&RQQHFWLRQWR2(;>3DJH@

&RQQHFWLRQWR(;3(,7(>3DJH@

&RQQHFWLRQWR26,/,1.;>3DJH@

&RQQHFWLRQWR723&$//>3DJH@

&RQQHFWLRQWR*DPPD)D[>3DJH@

&RQQHFWLRQYLD$33/,&207>3DJH@

7KH&RPPXQLFDWLRQV&RPSRQHQW767>3DJH@

6$3FRPPHYHORSPHQW/LEUDU\>3DJH@

:RUNLQJ:LWKWKH*UDSKLFDO,QWHUIDFH>3DJH@

7KH6$3FRPPLUHFWRU\7UHH>3DJH@

7KH6$3FRPP$X[LOLDU\3URJUDPV>3DJH@


%DVLFV

-XQH

%DVLFV

1DPLQJ&RQYHQWLRQV>3DJH@

&RPSDWLELOLW\>3DJH@

)XQFWLRQVRIWKH&RPPXQLFDWLRQV6HUYHU>3DJH@

,PSOHPHQWDWLRQ>3DJH@

+RZWKH6$3&RPPXQLFDWLRQV6HUYHU:RUNV>3DJH@

7KH&RQILJXUDWLRQ)LOH>3DJH@

7KH8VHU,QWHUIDFH>3DJH@

7KH&RPPXQLFDWLRQV&RPSRQHQWV>3DJH@


1DPLQJ&RQYHQWLRQV

-XQH

1DPLQJ&RQYHQWLRQVThis guide distinguishes between the actual communications server and its respective auxiliaryprograms. Wherever this distinction is not necessary for comprehension purposes, the term"SAPcomm" is used to represent the "communications server", the respective auxiliary programs,and also all of the products connected with the communications server.The names of the files created by the communications server, the SAPcomm programs and alldelivered files contain only lowercase letters. This also applies even if the name is written inuppercase in this guide in order to indicate its importance.


&RPSDWLELOLW\

-XQH

&RPSDWLELOLW\5

All R/3 Releases as of 2.0B are supported. In R/3 Systems of Release 2.0, SAPcomm must beconnected to the R/3 System via an SAP Gateway of Release 2.1 or higher.5

SAPcomm Version 3.0 supports the entire SAPcomm-relevant functionality of R/2 Versions 4.4D-4.4F and 5.0B-5.0F, as well as the 4.3 Versions modified to correspond to these versions.Where necessary, please ask your SAP contact person which SAPcomm version supportsextended functionality of later R/2 versions.


)XQFWLRQVRIWKH&RPPXQLFDWLRQV6HUYHU

-XQH

)XQFWLRQVRIWKH&RPPXQLFDWLRQV6HUYHUThe SAP communications server links SAP Systems (R/2, R/3 or a combination of both) witheach other and with remote communications partners. Its tasks cover the facilitating of dataexchange via different communications paths (X.400, and so on) and the provision of a standardinterface to the SAP system for these different communications paths.The SAP communications server is the basis for the following functions:

exchange of EDI documents. exchange of mail documents. exchange of telecommunications documents (telex, teletex, telefax).

The SAP communications server also allows you to link components other than those supportedby the standard SAP system or non-SAP systems to the SAP communications server via the6$3FRPPHYHORSPHQW/LEUDU\, the interface of the SAP communications (see The SAPcommDevelopment Library [Page 183] ).For information on which of these functions are supported on an application level in which SAPSystems from which release levels, refer to the following product information (obtainable fromBasis Sales):

6$3FRPP&RPPXQLFDWLRQV6HUYLFHVLQWKH6$36\VWHPV


,PSOHPHQWDWLRQ

-XQH

,PSOHPHQWDWLRQThe SAP communications server is a system of independent programs. It is not part of an SAPsystem, but runs independently of SAP systems in a UNIX or OS/2 environment. Itcommunicates with one or more SAP systems via a CPI--C link.It consists of the following components:

component to control all activities (see The Control Component SCB [Page 71]). user interface component; communications components to connect the communications systems performing the

data transmission.The communications server can run on the same hardware as an R/3 application server and/oran R/3 database server, or also run independently of them on separate hardware.


+RZWKH6$3&RPPXQLFDWLRQV6HUYHU:RUNV

-XQH

+RZWKH6$3&RPPXQLFDWLRQV6HUYHU:RUNVThe sending and receiving of data is carried out via the SAP communications server using thestore-and-forward procedure.For example, to send a series of EDI documents, the communications server must establish thelink to the SAP system and "fetch" the EDI documents; they are loaded from the SAP system intothe "communications server environment" and stored there. The control component of thecommunications server passes the EDI documents to the communications component (orpossibly to several components in each case), which then sends the data at a date determined inthe "communications server time plan".Conversely, incoming documents are also first stored in the communications server environmentand passed on to the SAP system at a later date.The initiative for the data exchange between an SAP system and the communications server istherefore controlled by the communications server alone.Please note that the SAP Communications Server automatically carries out only those actions forwhich scheduling instructions have been entered in the configuration file.


7KH&RQILJXUDWLRQ)LOH

-XQH

7KH&RQILJXUDWLRQ)LOHThe communications server requires specific information for the data exchange activities(creation of the link to an SAP system, passing on documents to a responsible communicationscomponent, and so on).You must enter this information in the configuration file (see The Configuration FileSAPCOMM.CFG [Page 34]).You also enter information regarding the temporal sequence of all data exchange activities in theconfiguration file SAPCOMM.CFG. These statements are stored internally in a "time plan".


7KH8VHU,QWHUIDFH

-XQH

7KH8VHU,QWHUIDFHThe communications server supplies information on the status of the system via a graphical userinterface. This user interface allows you to initiate data exchange and to check the activities ofthe SAP communications server via a menu. (See Working With the Graphical Interface [Page223]). However, the communications server can also be operated without its graphical userinterface.


7KH&RPPXQLFDWLRQV&RPSRQHQWV

-XQH


&RPPXQLFDWLRQV6\VWHPV

The connection of the SAP communications server to the data networks and the actual datatransmission is carried out via special communications systems (for example, a file transferprogram with an adapter card or telefax box). The connection of such a communications systemto the communications server is carried out via the "communications components".A separate communications component is responsible for every communications system to beconnectedas part of the SAP communications server.This communications component consists of an independent program, which is started or endedby the control component of the communications server whenever the communications server isstarted or stopped.Example: The communications component SAP (see next topic) is implemented by program6&0,6$3 (or 6&0,6$3(;( under OS/2). Other communications components areimplemented analog by the corresponding programs (6&0,2;6&0,723, etc.).Various vendors have adapted their communications solutions to SAPcomm requirements. For alist of such vendors, see the SAP brochure Communication Services in SAP Systems, orderingnumber 50 010 054. This list is not guaranteed to be complete.Please note that basic SAPcomm functions must always be obtained from SAP even if you wantto use non-SAP communications components for SAPcomm.

R/2 only :Non-SAP communications components for SAPcomm require the following SAPcomponents:

837 (OS/2) 840 (UNIX)

/LQN:LWK6$36\VWHPV

The communications component "SAP" is responsible for data exchange between thecommunications server and one or more SAP systems.Data exchange is based on CPI-C - regardless of whether the communications server is installedon the same hardware as an R/3 presentation server, application server or database server or onseparate hardware.All communications subsystems participating in data exchange (for example VTAM...) must besuitably configured. The configuration of these communications subsystems is not covered inthis document. You will find configuration examples in 6$3&RPPXQLFDWLRQ&RQILJXUDWLRQ.Please also read the documentation supplied by each manufacturer./LQN:LWK5HPRWH&RPPXQLFDWLRQV3DUWQHUV

The SAP communications server supports different communications systems when linking upwith remote communications partners. You can check what these are in the individual sectionson the communications components.It is also possible to link other communications systems together via the communications serverinterface SAPcomm-API.



-XQH

The communications server can be operated with any combination of these communicationscomponents. A subsequent upgrade with further components is possible at any time.


+DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV

-XQH

+DUGZDUHDQG6RIWZDUH5HTXLUHPHQWV

2SHUDWLQJ6\VWHPV>3DJH@

7KH&RQQHFWLRQWR6$36\VWHPV>3DJH@

&RPPXQLFDWLRQV&RPSRQHQWV>3DJH@

7KH&RQWURO&RPSRQHQW>3DJH@

LVN&DSDFLW\>3DJH@


2SHUDWLQJ6\VWHPV

-XQH

2SHUDWLQJ6\VWHPVThe control component and the user interface of the communications server can be run on thefollowing operating systems:

AIX

HP-UX OS/2 (as of Version 2.1) SINIX OSF/1 Solaris (Sun)

Which of these operating systems meets your requirements depends largely on whichcommunications component(s) you wish to install. The control component must be installed onthe same hardware as all of the linked communications components.


7KH&RQQHFWLRQWR6$36\VWHPV

-XQH

7KH&RQQHFWLRQWR6$36\VWHPVThe connection of the communications server to SAP Systems (R/2 and R/3) is based on CPI-C.56\VWHPV

The hardware and software requirements are identical to those of a CUA server. For furtherdetails, please refer to the following SAP brochure: 6$3VXSSRUWHG1HWZRUN3URGXFWVConnecting the communications server to SAP systems requires the configuration of a logicalunit LU 6.2 reserved for the communications server.For more information, please refer to the following SAP documentation: 6$3&RPPXQLFDWLRQ&RQILJXUDWLRQ

56\VWHPV

The connection between SAPcomm and R/3 Systems is handled via the SAP Gateway (&3,&+DQGOHU). For more information, please refer to the following documentation:6$3&RPPXQLFDWLRQ&RQILJXUDWLRQ


&RPPXQLFDWLRQV&RPSRQHQWV

-XQH

&RPPXQLFDWLRQV&RPSRQHQWVFor information on which operating systems the individual communications components can rununder, refer to the sections on the communications systems.Information in this section only refers to the control component of the communications server andthe connection to SAP systems.The communications systems linked have more specific requirements - concerning, for example,the platform, operating system version or other hardware components. For further details, pleaserefer to the respective manuals of the manufacturers.


7KH&RQWURO&RPSRQHQW

-XQH

7KH&RQWURO&RPSRQHQWSpecial requirements concerning types of hardware, operating system version and main memorydepend on how you want to operate the communications server:

On a separate computer:The same reqirements apply as for R/2 Workstation Software. These requirementsare described in the SAP documentation S40.2 and in the brochure 6$36XSSRUWHG1HWZRUN3URGXFWV.

Together with an R/3 presentation server, an R/3 application server and/or an R/3database server on a shared computer:The same requirements apply as for the R/3 components.

26Please note that only Versions 2.1 and above are supported.


LVN&DSDFLW\

-XQH

LVN&DSDFLW\The disk capacity required mainly depends mainly on the following factors:

How large your message volume is. The time period during which messages are buffered.

How long must the communications server or other participating communicationssystems buffer messages?(This is determined, among other things, by the time plan of the communicationsserver.)

Whether you archive messages via the communications server. The extent to which you use the communications servers tracing options.

A useful disk capacity in practice is 50 MB, but this can of course only be an approximate value.


,QVWDOODWLRQ

-XQH

,QVWDOODWLRQ

2YHUYLHZ>3DJH@

,QVWDOODWLRQ8QGHU81,;>3DJH@

,QVWDOODWLRQ8QGHU26>3DJH@

0RGLI\LQJWKH&RQILJXUDWLRQDQG&RPPXQLFDWLRQV)LOHV>3DJH@

,QVWDOOLQJDQG&RQILJXULQJ&RPPXQLFDWLRQV6\VWHPV>3DJH@

3UHSDUDWLRQLQWKH6$36\VWHP>3DJH@


2YHUYLHZ

-XQH

2YHUYLHZThis section describes how to install the communications server on a workstation, which isalready linked to a network environment.Neither the installation and configuration of the network software nor the installation andconfiguration of the communications systems to be linked to the communications server aredescribed in this manual. For further information, please read the appropriate manufacturerdocumentation and the SAP documentation 6$3&RPPXQLFDWLRQ&RQILJXUDWLRQThis section describes a new installation. If you have already installed an older version of thecommunications server, note the following before installing a new version:

SAPcomm as of Version 2.1:Save your old configuration file VDSFRPPFIJ and the side info file.

All SAPcomm versions before 2.1:The files created in the "old" communications server environment cannot beprocessed by the "new" communications server. Please ensure that all old files(outgoing and incoming documents, status messages) are first processed before youinstall the new version of the communications server. It is recommended that youdelete the old version (including all files, after first making a data backup) before theinstallation or at the latest after starting up the new communications server.


2YHUYLHZ

-XQH

,QVWDOODWLRQ8QGHU81,;This topic describes how to install SAPcomm on a UNIX platform, which is linked to an R/2 or R/3System.The installation program creates the SAPcomm directory tree [Page 230] and copies the filesfrom the CD-ROM to the various directories.

8VHU$XWKRUL]DWLRQV

The directories, programs and non-executable files must be created so that the user, underwhich the communications server is started, can carry out the following actions:

start all executable files (the programs) of the SAPcomm call directory, read all the files of the profile directory, create directories in the SAPcomm root directory (write authorization), search for files in the SAPcomm root directory (read authorization for this directory).

Files created by the communications server are given the system-wide defined access mode(permissions). To restrict access authorizations to the files created by the server, use the UNIXcommand XPDVN for the user under which the communications server is started.

027,)3DUDPHWHUVIRU6$3FRPP

You can configure the SAPcomm user interface (the window which appears on the screen afterstarting the sapcomm program) using the procedure generally applicable to MOTIF programs.For example, if you want to use a font other than the default font for the SAPcomm window,insert the parameter

sapcomm*labelFontList: This parameter affects all texts in menus and pop-up windows.

sapcomm*FontList: This parameter affects all other SAPcomm texts.

You can change the size (sapcomm.height, sapcomm.width) and color of the window in exactlythe same way. For further details on this, please read your Motif manual.

,QVWDOODWLRQZLWKDQ56\VWHP

An installation program is provided to install SAPcomm on a UNIX platform, which is linked to anR/2 System. It can be found on the delivery CD.

,QVWDOODWLRQZLWKDQ56\VWHP

To install SAPcomm on a UNIX platform, which is linked to an R/3 System, you have thefollowing options:

Before R/3 Release 2.1DTo install SAPcomm on a UNIX platform, which is linked to an R/3 System earlier than Release2.1D, please contact your SAP support representative.

After R/3 Release 2.1DThe installation is described in a separate document, VDSFRPPLQVWDOOGRF.


2YHUYLHZ

-XQH

To install SAPcomm, use the script VDSFRPPLQVWDOO.Both of these files are included in the R/3 delivery package.

After R/3 Release 2.2BThe SAPcomm installation program can be called as an option in the R/3 installation menu.


2YHUYLHZ

-XQH

,QVWDOODWLRQ8QGHU26The installation program contained on the CD-ROM installs the SAP Communications Server.The installation program creates the SAPcomm directory tree [Page 230] under the root directoryVDSFRP.

It copies the files from the CD-ROM and modifies the OS/2 configuration file CONFIG.SYS.After installation, you will find the following files in the directory VDSFRPHWF:

The model configuration file VDSFRPPFIJCopy it to the SAPcomm profile directory, if a SAPcomm configuration file not yetexits.

Modifications to SAPcomm configuration only take effect if they are performed onthe configuration file stored in the profile directory.

Files that are not essential for operation of SAPcomm (sample source file, etc.)Instructions for using this program are contained in a separate guide, which is included.Please note that for certain communications systems (ODEX...), the communications server mustbe installed on the same drive as the communications system. Further details on this can befound in the sections for the respective communications components.


2YHUYLHZ

-XQH

0RGLI\LQJWKH&RQILJXUDWLRQDQG&RPPXQLFDWLRQV)LOHVThe installation program creates the ETC Directory [Page 233].This directory contains the example configuration file VDSFRPPFIJCopy this file to theSAPcomm profile directory if no VDSFRPPFIJ file exists there. In this directory you will also findfiles that are not directly required for the operation of SAPcomm (example source code, etc.).Modifications to SAPcomm configuration only take effect if they are performed on theconfiguration file located in the profile directory.After installation you must adapt the following files to suit your local requirements:

configuration file VDSFRPPFIJ, sideinfo file, profile file VDSFRPPSIO

You can now put the communications server into operation (the correct installation andconfiguration of all required network links as well as the linked communications programs is aprerequisite for this).Please also read the topic Starting the Communications Server [Page 83]&RQILJXUDWLRQ)LOHVDSFRPPFIJ

The configuration file must be located in the SAPcomm profile directory. Maintain this file asdescribed in the guidelines Configuration in the SAP System [Page 62]. Please also note"Testing the Configuration Data [Page 50] ".6LGH,QIR)LOH

The communications server needs certain network-specific information to establish a link to anSAP system. It extracts this information from the parameter SYSTEM of the SAPcommconfiguration file (communications component SAP), and from the side info file.For a description of side info files, refer to the documentation 6$3&RPPXQLFDWLRQ&RQILJXUDWLRQ

Example File for OS/2The installation program copies a side info example file called SIDEINFO to the ETC Directory[Page 233].The installation program also generates (in the CONFIG.SYS file) the environment variable SIDEINFO with the value /SIDEINFO. SAPcomm can only establish a connectionwith an SAP system if this environment variable correctly points to your side info file.If you change the name or the directory of your side info file, you must also change the definitionof the environment variable SIDE INFO accordingly.

If your system configuration file CONFIG.SYS already contains the definition ofthe environment variable SIDE INFO, this variable will be overwritten by theinstallation program.

The format of the side info example file corresponds to the description in the documentation 6$3&RPPXQLFDWLRQ&RQILJXUDWLRQ


2YHUYLHZ

-XQH

You can use the program CVSIDE to create a file with the new format from the "old"SAPCPIC.TBL file. To do this, enter the following command in the directory SAP:

CVSIDE sapcpic.tbl > sideinfo

(You may need to specify the full path for CVSIDE.)Please read the notes on the side info file in the section on the communications component SAP.

3URILOH)LOHVDSFRPPSIO

The profile file VDSFRPPSIO is needed both for the UNIX and OS/2 environments. It is includedwith the delivery of SAPcomm.OS/2:During installation, the file is copied to the profile directory. You do not need to change this file.UNIX:It contains the value for the SAP parameter SAPSYSTEM. This value must be unique toSAPcomm - it may not already be assigned in another SAP profile file. You can choose anyvalue you wish and replace the default with this new value.


2YHUYLHZ

-XQH

,QVWDOOLQJDQG&RQILJXULQJ&RPPXQLFDWLRQV6\VWHPVBefore you can exchange data with your communications partners, you must:

install your communications systems (ODEX, etc.) including the respective hardwareand driver software (EICON, etc.)

configure the installed communications systems.Please refer to the respective guides for guidelines on the installation and configuration of yourcommunications system and the respective adapter hardware and software.Operation of the communications server requires the correct installation and configuration of yourcommunications systems. Therefore, you must first test your communications system withoutstarting the communications server.The sections on the communications components explain how the communications server workstogether with your communications systems, and which SAP-specific aspects must be taken intoaccount before configuration.

9$1&RQQHFWLRQ

When connecting to a VAN, specific preparations must be made during SAP communicationsserver installation (registration, passwords, etc.). For further details on this, consult your VANsupplier and request the appropriate guides.


2YHUYLHZ

-XQH

3UHSDUDWLRQLQWKH6$36\VWHPYou must make a number of preparations in every SAP System, to which the communicationsserver is to be linked:

5 Create user

Create the user, under which the communications server logs on to the R/2 Systemas follows:- as a CPI-C user (as of Release 5.0)- with authorization to maintain Tables EDCT and SKWD- other authorizations depending on the application

Create Tables EDCT and SKWDCreate Tables EDCT and SKWD in the SAP System in all clients, with whichSAPcomm is to be linked. These tables exist only in client 0 in the standard delivery.

For EDI as of Release 5.0FThe SAPcomm-ID must be configured as a port (parameter IDSAPCOMM, see thesection Connection to SAP Systems [Page 87]).

5 Create user

Create the user, under which the communications server logs on to the R/3 Systemas follows:

as a CPI-C user with the profile S_SKOM_SRV, which is contained in the R/3 shipment


7KH&RQILJXUDWLRQ)LOH6$3&200&)*

-XQH

7KH&RQILJXUDWLRQ)LOH6$3&200&)*

2YHUYLHZ>3DJH@

6WUXFWXUHRIWKH&RQILJXUDWLRQ)LOH>3DJH@

75$&(3DUDPHWHU*URXS>3DJH@

&KDQQHOV$FFHVVWRWKH&RPPXQLFDWLRQV&RPSRQHQWV>3DJH@

+RZDUHRFXPHQWV$OORFDWHGWR7KHLU&KDQQHO">3DJH@

6$3FRPP6FKHGXOH6WDWHPHQWV>3DJH@

7HVWLQJWKH&RQILJXUDWLRQDWD>3DJH@

&RQILJXUDWLRQ([DPSOHV>3DJH@


2YHUYLHZ

-XQH

2YHUYLHZThe configuration file is used to configure the SAP communications server. The parameters thatyou enter here allow you to determine:

with which SAP systems the communications server can exchange data with which communications components you operate the communications server when the communications server carries out which activities

routing:which communications component "sends" a document and via which channel(Incoming messages: To which SAP system a document is forwarded.)

The configuration file is a text file. Maintain this file with an editor (for example, the SAP editor).Two examples of complete configuration files can be found at the end of this section.


6WUXFWXUHRIWKH&RQILJXUDWLRQ)LOH

-XQH

6WUXFWXUHRIWKH&RQILJXUDWLRQ)LOHIn the configuration file, parameters related by content are grouped together in parameter groupsof a certain category. The category of the parameter group determines which parameters andwhich other parameter groups (nesting) the group can contain.Only parameter groups of the category PROGRAM are permitted at the "upper" level. Thismeans that the entire configuration file consists exclusively of parameter groups with thefollowing structure:352*5$0LGHQWLILHU!

3DUDPHWHUVSHFLILFDWLRQ!

(1352*5$0

Parameter groups of other categories have different start and end lines.The parameter groups of the category PROGRAM enable you to specify the communicationscomponents with which the communications server is operated.You must include a separate parameter group in the configuration file for every communicationscomponent - each with its respective identifier. You can look up the identifiers in the sections onthe individual communications components.

7KH6&%3DUDPHWHU*URXS

You must also include a PROGRAM parameter group in the configuration file in which you enterparameters for the control component of the communications server. This parameter group hasthe identifier "SCB" (the identification code stands for 6APFomm %asis).The information in the following two sections "Parameter Specification" and "ReferencingParameter Groups" about syntax applies to the parameter group SCB and for all the parametergroups. However, the contents of the parameter group SCB differ from the remainingPROGRAM parameter groups. Parameter group SCB is therefore discussed separately in TheControl Component SCB [Page 71]3DUDPHWHU6SHFLILFDWLRQ

The parameters belonging to a parameter group are specified in the form of parameter lines:

3$5$0(7(51$0( 3$5$0(7(59$/8(or - when grouping several parameters into a block in the form of parameter groups (now as a"subgroup" of the current parameter group).Either "ON" or "OFF" must be entered as a PARAMETER-VALUE for a series of parameters orparameter groups. This value activates or inactivates the respective parameter or parametergroup.

5HIHUHQFLQJ3DUDPHWHU*URXSV

Reference to parameter subgroups can be made elsewhere in the configuration file (an exampleof this is the parameter group DESTINATION specified below). The reference is made for everyparameter whose PARAMETER-NAME is identical to the category of the parameter group whichis to be referenced.([DPSOH



-XQH

Referenced group: (67,1$7,21(67...............

(1(67,1$7,21...............

Additional subgroup: $127+(5B*5283 *5..............

Ref. to group DEST1: (67,1$7,21 (67..............

(1$127+(5B*5283

A referenced parameter group must always come BEFORE the parameter(s) that reference(s) itin the configuration file. Otherwise, the sequence of parameter lines and parameter groups isvariable.

7KH352*5$03DUDPHWHU*URXS

Parameter groups of the category PROGRAM have the following structure:352*5$0 LGHQWLILHU!

(67,1$7,21 GHVWLQDWLRQQDPH!GHVWLQDWLRQSDUDPHWHU!

(1(67,1$7,21

6(/(&7,21 VHOHFWLRQQDPH!VHOHFWLRQSDUDPHWHU!

(16(/(&7,21

3(5,2,& SHULRGQDPH!SHULRGSDUDPHWHU!

(13(5,2,&

3(5)250 SHUIRUPQDPH!VFKHGXOHVWDWHPHQWV!

(13(5)250

&+$11(/ FKDQQHOQDPH!3(5)250 SHUIRUPQDPH!

VFKHGXOHVWDWHPHQWV!(13(5)250FKDQQHOSDUDPHWHU!

(1&+$11(/

75$&( 21_2))!75$&(B$// 21_2))!,1,7 21_2))!3*0B)/2: 21_2))!$7$B)/2: 21_2))!&6B5(63216( 21_2))!),/(6 21_2))!,3& 21_2))!0(025< 21_2))!5287,1* 21_2))!48(8(B06* 21_2))!(9B&75/ 21_2))!6&,B&$// 21_2))!6&,B3$5$0 21_2))!6&,B$775 21_2))!6&,B3(5) 21_2))!



-XQH

(175$&(

2:16(66,21 21_2))!5(48(67B,17(59$/ 0LQXWHV!/2*),/(B(;3,5$7,21 1XPEHURIGD\V!$5&+,9( 21_2))!6$9(B5(63216(B,1)250$7,21 21_2))!6(15(48(67%/2&.6,=( 1XPEHURIILOHV!FRPSRQHQWVSHFLILFSDUDPHWHUV!

(1352*5$0

The basic structure shown above is common to all parameter groups of the category PROGRAM.However, not all the parameters or parameter groups listed above need exist. Multiple instancesof some of these groups - for example, CHANNEL, SELECTION - and also certain otherparameters can exist.The contents of the individual PROGRAM parameter groups can vary depending on thecommunications component. The following only describes the parameters which can or do occurin all PROGRAM parameter groups. The parameters specific to a certain communicationscomponent (these are the "component-specific parameters") are described in the section on therespective communications component.

,GHQWLILHU

Every communications component connected to SAPcomm is identified by a three-digit alphanumeric identifier. By specifying this identifier as the "name" of aPROGRAM parameter group, you establish the reference to the respectivecommunications component.

(67,1$7,213DUDPHWHU

Group together parameters that are required to create a link in parameter groups ofthe category DESTINATION. These parameters can then be referenced within therespective PROGRAM parameter group via the chosen destination name. Thedestination name consists of a maximum of ten alphanumeric characters and must beunique within its PROGRAM parameter group.The specification of a destination parameter group is not a necessary requirementand depends on the participating communications component anyway. When, and inconnection with which communications components, these parameter groups arenecessary is explained in the sections on the individual communications componentsthat are of interest to you.

6(/(&7,213DUDPHWHU

You define groups of selection criteria for retrieval of documents from a target systemor from a remote communications partner in parameter groups of the categorySELECTION (for example, selective retrieval of outgoing documents from an SAPsystem).The creation of a special SELECTION parameter group alone has no effect - only if itis referenced in a PERFORM parameter group with the action message RECEIVE dothe selection criteria defined in it take effect. Please read "SAPcomm ScheduleStatements [Page 47] ".Enter any - alphanumeric - name with up to ten characters as the selection name.The only requirement is that all the selection names you use must be unique withintheir PROGRAM group.



-XQH

6HOHFWLRQSDUDPHWHUThe actual selection parameters are specific to every communications component.Please read the individual sections on the communications components forinformation on which selection parameters you can specify in each case.

3(5,2,&3DUDPHWHU

You group together parameters for the execution times of action messages inparameter groups of the category PERIODIC. You can refer to these parametergroups from all PERFORM groups by specifying the period name. The contents ofthe PERIODIC parameter groups are explained in "SAPcomm Schedule Statements[Page 47] "

3(5)2503DUDPHWHU*URXS

Here you can use PERFORM parameter groups to specify the execution ofcommunication components which support administrative functions (reorganization,and so on), and the times at which they are to be carried .Please bear in mind that, in PERFORM groups that are direct subgroups of aPROGRAM parameter group, you can only enter statements for the execution ofADMINISTRATIVE functions. Statements for the execution of data transfer functionsare only possible within CHANNEL parameter groups (see below).Please read the sections on the communications components for details of whichadministrative functions are supported by which communications components.The contents of the PERFORM parameter groups are explained below in "SAPcommSchedule Statements [Page 47] ".

&+$11(/3DUDPHWHU

Allocate "channels" to the communications component using the parameter groups ofthe category CHANNEL. Assign every CHANNEL parameter group ( "every channel") a SAPcomm-wide unique channel name with a maximum of ten alphanumericcharacters.Please note: The channel name that you assign is also used as a directory name (seeThe SAPcomm Auxiliary Programs [Page 236]). If your file system does not allowdirectory names of ten characters, you must limit yourself to correspondingly shorterchannel names.As explained in the section "Channels - Access to the Communications Components[Page 43] ",outgoing documents can only be forwarded to communicationscomponents via the channels configured here and incoming documents can also onlybe fetched from the communications components via channels.Specify when these actions - forwarding and fetching of documents - are to be carriedout in the PERFORM parameter groups.The contents of the PERFORM parameter groups are explained in "SAPcommSchedule Statements [Page 47] ".The structure of a CHANNEL parameter group is described in "Channels - Access tothe Communications Components [Page 43] ".

75$&(3DUDPHWHU*URXS

The TRACE parameters are described in the section TRACE Parameter Group [Page41].



-XQH

2:16(66,213DUDPHWHU

This parameter is only relevant if you use SAPcomm-API to develop your owncommunications component (only for the OS/2 version of SAPcomm).Specify OWNSESSION ON to start your component in a separate OS/2 session.

5(48(67B,17(59$/3DUDPHWHU

Optional. Enter here at what time intervals the communications component is to bequeried for status confirmations and incoming messages received by the connectedcommunications system (in the SAPcomm user interface: "Local Request"). Default:5 minutes.

/2*),/(B(;3,5$7,213DUDPHWHU

Optional. Enter here after how many days old log files created by the respectivecomponent are to be automatically deleted. If you do not enter this parameter, therespective log files are not deleted.

$5&+,9(3DUDPHWHU

Optional. If this parameter is entered, the files sent via the respectivecommunications component are not deleted but left on the workstation hard disk -under different names. These files are not deleted by the communications server.

6$9(B5(63216(B,1)250$7,213DUDPHWHU

Optional. If this parameter is entered, "responses" created by the connectedcommunications system (to the statements created by the communications server)are saved. Corresponding log file entries allow these archived responses to beretrieved for later analysis. These files are not deleted by the communications server.

6(15(48(67B%/2&.6,=(3DUDPHWHU

You can use this parameter to instruct a communications component to interrupt thetransmission of outgoing messages to the connected communications system after aparticular number of files.After the interruption, the communications component is available for other tasks (e.g.the fetching of status messages). The transmission of outgoing messages isresumed once other activities (that may be waiting in a queue) have been processed,irrespective of schedule configuration.

&RPSRQHQWVSHFLILF3DUDPHWHUV

Other PROGRAM parameters specific to the respective communications componentcan exist in addition to the stated parameters of the parameter group PROGRAM.Please read the sections on the communications components for information onwhich individual parameters these are.



-XQH

75$&(3DUDPHWHU*URXSIf you specify the parameters of this optional group, information on run-time will be logged. Youcan use this information to fine-tune the SAPcomm schedule (see "Log Directory" in TheSAPcomm Auxiliary Programs [Page 236]).You can activate this group by specifying "ON" (default) or deactivate it by specifying "OFF". Youcan enter any combination of the following parameters (you can switch every individualparameter on by specifying ON or turn them off by specifying OFF. Specifying OFF has thesame effect as if you had not entered the parameter at all).75$&(B$// 21_2))!If this parameter is specified (with ON), all the trace functions are activated. The specification ofother trace parameters is then unnecessary.,1,7 21_2))!If this parameter is entered, then information on the initialization phase of the communicationscomponent is logged.3*0B)/2: 21_2))!If this parameter is specified, then detailed information on the program execution of thecommunications component is logged.$7$B)/2: 21_2))!This parameter is only important for communications components that use a non-file-based typeof interface to exchange data with their target system or the connected communications program.In this case, you can trigger the logging of exchanged data (or a part of it) by using the parameterDATA_FLOW.&6B5(63216( 21_2))!If this parameter is entered, then information (for example on confirmations) supplied by theconnected communications system is logged.),/(6 21_2))!If this parameter is entered, information on the file-related activities of the communicationscomponents is entered into the log file.,3& 21_2))!If this parameter is entered, then information on the use of functions for process-to-processcommunication is entered into the log file by the communications component. This is onlyprovided for internal SAP purposes.0(025< 21_2))!If this parameter is entered, information on the administration of the memory (allocation, ..) isentered into the log file.5287,1* 21_2))!If this parameter is entered, information on the assignment of documents to the channelsresponsible for sending these documents is entered into the log file. Use this parameter if, forexample, incoming documents are allocated to an "incorrect" SAP System - the log entries couldhelp you to find an incorrect entry in the routing entries (the PROGRAM parameter group SCB).48(8(B06* 21_2))!If this parameter is entered, SAPcomm-internal messages are logged. This is only provided forinternal SAP purposes.



-XQH

(9B&75/ 21_2))!If this parameter is entered, information on the control of external devices (for example modems)is logged.6&,B&$// 21_2))!By specifying this parameter, you cause every call of one of the functions related to the activationof a communications component to be logged.6&,B3$5$0 21_2))!By specifying this parameter, you cause every transfer of a parameter to the respectivecommunications component (or from it) to be logged.6&,B$775 21_2))!By specifying this parameter, you cause every transfer of a message attribute to the respectivecommunications component (or from this) to be logged.6&,B3(5) 21_2))!If you specify this parameter, information on the duration of individual (PERFORM) activities orperiods of SAPcomm inactivity is entered in the log file of the respective SAPcomm component.


&KDQQHOV$FFHVVWRWKH&RPPXQLFDWLRQV&RPSRQHQWV

-XQH

&KDQQHOV$FFHVVWRWKH&RPPXQLFDWLRQV&RPSRQHQWVThe transfer of data from the control component to a communications component and from acommunications component to the control component always takes place via the channelsconfigured in the configuration file.

6HQGLQJ0HVVDJHV

A document is not assigned directly to the communications component that is to send it, but to achannel. The allocation of a document to a channel determines the following:

the communications component that is responsible for sending; the time at which the document is transferred to the communications component for

sending; parameters required by the communications component (dependent on the respective

communications component); assignment to a destination configured for the respective communications component

(dependent on the respective communications component).5HWULHYLQJ0HVVDJHV

You insert statements into the configuration file, with which you trigger the communicationsserver to retrieve messages from external communications partners (for example a VAN or SAPSystem to which the communications server is linked). This kind of statement does not referdirectly to the communications component responsible, but to a channel. The channeldetermines the following:

the communications component that is to retrieve the messages; the time at which these requests are to be carried out; the address from which the messages are to be retrieved (dependent on the

respective communications component); selection parameters

&RQILJXULQJ&KDQQHOV

You configure one or more channels for every communications component - that is, you enterone or more CHANNEL parameter groups within every PROGRAM parameter group in theconfiguration file.

&+$11(/3DUDPHWHU*URXS

A CHANNEL parameter group has the following structure:&+$11(/ FKDQQHOQDPH!

3(5)250 SHUIRUPQDPH!VFKHGXOHVWDWHPHQWV!

(13(5)250

(67,1$7,21 GHVWLQDWLRQQDPH!

FRPSRQHQWVSHFLILFSDUDPHWHU!(1&+$11(/


&KDQQHOV$FFHVVWRWKH&RPPXQLFDWLRQV&RPSRQHQWV

-XQH

The parameters of the CHANNEL parameter group are explained below:3(5)2503DUDPHWHU*URXS

For every channel, you specify in one or more PERFORM parameter groups the timeat which documents allocated to this channel are to be sent and, if necessary, thetime at which data is to be retrieved.The contents of the PERFORM parameter groups are explained in "SAPcommSchedule Statements [Page 47] ".

(67,1$7,213DUDPHWHU

By specifying this parameter, you can link the current channel to a DESTINATIONparameter group defined within the current PROGRAM group (for example, an SAPSystem). This assignment has the following effect: messages that are to be sent viathis channel, and for which there is no recipient address (or at least none that issufficient for sending), are sent to the address entered in the DESTINATION group.The specification of this parameter is only useful for certain communicationscomponents (it is, for example, mandatory for the communications component SAP).Please read the sections on the communications components in question forinformation on whether this parameter must be specified.

&RPSRQHQWVSHFLILF&+$11(/3DUDPHWHUV

Other component-specific CHANNEL parameters can be entered in addition to thestated parameters. Details on the parameters can be found in the sections on thecommunications components.


+RZDUHRFXPHQWV$OORFDWHGWR7KHLU&KDQQHO"

-XQH

+RZDUHRFXPHQWV$OORFDWHGWR7KHLU&KDQQHO"Every document to be sent is allocated to a channel (see previous topic "Channels - Access tothe Communications Components [Page 43] "). This assignment is made by the communicationscomponent that receives the document "from outside" (from the externally linked communicationssystem or from an SAP System).The (receiving) communications component determines the channel responsible for sending adocument in one of the following two ways:

the communications component is informed of the channel name by the (external)system from which the received document originates.This way of determining the channel name is only used for SAP-EDI and SAPTelecommunications outgoing documents. For further details on this, please read"SAP-EDI" and "Telecommunications from SAP Applications" below.

The channel name is determined for every individual message using the routingstatements stored in the SCB parameter group in the configuration file.. For furtherdetails, please read "The Routing Parameter Group [Page 76] ".

You must store certain information in the SAP System so that SAP outgoing messages areallocated to the "correct" channels (either directly or via the routing statements in theconfiguration file). The following text explains how to do this in the areas EDI, Mail andTelecommunications.The following topics describe how to assign the correct channel to a message to be exchanged inthe following applications:

SAP-EDI R/2 R/Mail andR/3 Office Telecommunication services for SAP documents

6$3(,

In the "partner communications addresses" of the SAP-EDI System, you allocate one or more"communications services" to every partner with whom you want to exchange EDI messages.Please enter the name of the channel via which you want to send the documents in question as acommunications service.In the case of incoming messages, the communications service allocated to the message,together with the name of the sender contained in the EDI message, serve to uniquely identifythe sender. The communications service of the respective sender must therefore also always betransferred to the SAP-EDI System together with an incoming message.Please read the guidelines in the sections on the communications components for details of howto allocate the communications service to an incoming message.

550DLODQG52IILFH

On the transmission screen in the SAP mail system, you enter a "transmission type" for everymessage that you want to send to an external recipient. The transmission type determines theSERVICE parameter group (in the routing statements of the PROGRAM parameter group SCB),in which the responsible channel is determined (for example, "SSW" for Soft*Switch(SNADS) ->SERVICE parameter group is SSW, "X40" -> SERVICE parameter group is X400 ).


+RZDUHRFXPHQWV$OORFDWHGWR7KHLU&KDQQHO"

-XQH

For further details on this, please read the topic "The Routing Parameter Group [Page 76] " in thesection on the control component.

7HOHFRPPXQLFDWLRQV6HUYLFHVIRU6$3RFXPHQWV

Documents that are created by SAP applications and are to be sent via the telecommunicationsservices (telefax, telex, teletex) are transferred to the SAP spool system.In the course of this, they are assigned a logical destination. For details on how the selection ofthe destination is carried out, refer to Telecommunications Tables in SAPcomm Administrationin the SAP System.The identification of this destination (for example, "TF01" for telefax) also directly determines thename of the channel in the SAP communications server. An indirect assignment destination -->channel is not (currently) possible - that is, the SAPcomm channels for telecommunicationsservices must have identical names to the logical destinations in SAP.


6$3FRPP6FKHGXOH6WDWHPHQWV

-XQH

6$3FRPP6FKHGXOH6WDWHPHQWVYou specify when the communications server is to carry out which activities using the PERFORMparameter groups - if necessary, together with PERIODIC parameter groups. The parametersentered in these groups are stored internally as a "SAPcomm schedule".PERFORM parameter groups can be placed in two positions within a PROGRAM parametergroup:

$VDGLUHFWVXEJURXSRIWKH352*5$0SDUDPHWHUJURXSThis triggers the execution of PROGRAM-specific administrative functions, providingthese are supported by the respective communications component.

$VVXEJURXSVRIWKH&+$11(/SDUDPHWHUJURXSVThis triggers the transfer of documents to the respective communications component(to send) and the transfer of statements to the communications component to retrievedocuments from remote communications partners.


A PERFORM parameter group has the following structure:

3(5)250 SHUIRUPQDPH!

$&7,21 IXQFWLRQ!

$< ZHHNGD\!

7,0( WLPHRIH[HFXWLRQ!

3(5,2,& SHULRGQDPH!

6(/(&7,21 VHOHFWLRQQDPH!

(13(5)250

The specifications TIME and PERIODIC are not mandatory. If they do not appear in aPERFORM group, the actions specified in them are not carried out automatically, but can bestarted from the graphic SAPcomm user interface.The parameters of the PERFORM parameter group are explained below:

1DPHRIWKH3(5)2503DUDPHWHU*URXS

Enter a name for the PERFORM group with a maximum of twenty characters. Thisname must be unique within its respective PROGRAM or CHANNEL main group.When starting actions from the graphic SAPcomm user interface, the list of "performnames" is displayed for you to select an action. It is therefore recommendable toassign meaningful names for selection purposes.

$&7,213DUDPHWHU

You enter the function that the communications server is to carry out here. You mustinsert at least one ACTION parameter into a PERFORM parameter group. Severalsuch parameters can be specified, depending on the communications component.The functions which you can specify within a CHANNEL parameter group are:6(16&+(8/(Transfers the documents to the communications component that are not marked fornight dispatch. The communications server checks at the times specified in the



-XQH

PERFORM group whether there are documents allocated to the present channel. Ifthis is the case, these documents are transferred to the connected communicationssystem. Once the transfer begins, it is the responsibility of the connectedcommunications system to handle the sending of the documents. Please note that"sending" (from the view of the communications server) for the communicationscomponent SAP means transferring incoming documents to the SAP System!6(11,*+7Transfers the documents marked for night dispatch to the communicationscomponent. Caution: these documents are only passed on for sending due to a"SEND-NIGHT" statement. If you have not specified such a statement for a certainchannel, then documents allocated to this channel and marked for night dispatchremain in the communications server environment and are not sent! If you do notwork with documents selected especially for night dispatch, then you need not enter a"SEND-NIGHT" statement.5(&(,9(Creates the link to the remote communications partner and fetches supplieddocuments. If the connection setup of the respective communications system iscarried out asynchronously (relative to the communications component), the incomingdocuments are initially only transferred to the environment of the communicationscomponent. In a second step, the communications component is asked whetherincoming documents exist. If this is the case, these incoming documents aretransferred and allocated to "their" channel. The specification of this function is ofcourse only useful in connection with communications components that can fetchactive documents from a remote communications partner.The functions that can be specified, if the PERFORM group is a direct subgroup ofthe PROGRAM parameter group, depend on the respective communicationscomponent. For details of which administrative functions (reorganization, and so on)are supported in each case, please read the sections on the individualcommunications components.

$



-XQH

documents from the SAP System that only contain certain message types). You caninclude several references to a SELECTION parameter group in a PERFORMparameter group.

3(5,2,&3DUDPHWHU*URXS

You refer to PERIODIC parameter groups in the PERFORM parameter groups if you want tomake SAPcomm carry out an action not only once a day (parameter TIME), but also periodically.In PERIODIC parameter groups, you can enter the intervals (specification in minutes) and inwhich part of the day the respective action is to be carried out.You create the PERIODIC parameter groups as direct subgroups of the respective PROGRAMparameter group. The parameters of these parameter groups are explained below.3(5,2,& SHULRGQDPH!

,17(59$/ OHQJWKLQPLQXWHV!)520 VWDUWLQJWLPH!817,/ ILQLVKLQJWLPH!

(13(5,2,&

1DPHRIWKH3(5,2,&3DUDPHWHU*URXS

You enter a name here with a maximum of twenty characters. You can refer to thisname by specifying the PERIODIC parameter within the PERFORM groups.

,17(59$/3DUDPHWHU

You enter here the intervals at which SAPcomm is to carry out a certain action("whose" PERFORM group refers to the current PERIODIC group).

)5203DUDPHWHU

Optional. You can limit the period to which the PERIODIC statement refers to a part ofthe day. If you want to do this, enter the starting time here in the format HH:MM(hours:minutes).

817,/3DUDPHWHU

Specify the end time here in the format HH:MM (hours:minutes). The finishing timecan also be "smaller" than the starting time - that is, a period of a day from 20:00 to7:00 is permitted.


7HVWLQJWKH&RQILJXUDWLRQDWD

-XQH

7HVWLQJWKH&RQILJXUDWLRQDWDThe configuration parameters stored in the configuration file sapcomm.cfg are not read directlyfrom the control component of the communications server, but must first be checked, thenconverted into an SAPcomm-internal format and finally stored in the file sapcomm.bcf (binaryconfiguration data). These functions are carried out by the SAPcomm auxiliary programVFPFIJFF.

The control component of the communications server starts the auxiliary program independentlyif required - that is, if the binary configuration file sapcomm.bcf does not exist or the configurationfile sapcomm.cfg has been changed.On the other hand, you can also start this auxiliary program directly without starting thecommunications server - for example, to check a change made to the configuration filesapcomm.cfg, particularly if the following error message appears when starting SAPcomm:Binary configuration file cant be generated.For more information on scmcfgcc and problem analysis, see SAPcomm auxiliary programsunder Checking the Configuration Data (scmcfgcc) [Page 240]


&RQILJXUDWLRQ([DPSOHV

-XQH


&RQILJXUDWLRQ([DPSOHIRU2GH[3&DQG([SHGLWH>3DJH@

&RQILJXUDWLRQ([DPSOHIRU723&$//>3DJH@



-XQH

&RQILJXUDWLRQ([DPSOHIRU2GH[3&DQG([SHGLWHExample of a SAPcomm configuration file with Odex and Expedite. If one of these componentsare not installed, you must delete the corresponding PROGRAM parameter group (ODX or EXP).Refer also to the configuration example for the TOPCALL connection.

352*5$06&%

HOHWH6&%ORJILOHVDIWHUGD\V

/2*),/(B(;3,5$7,21

5RXWLQJSDUDPHWHUJURXS

5287,1*6$3&200

6(59,&(2)73

72&+$11(/&+6$36



-XQH

6



-XQH

HILQHDFWLRQ*HWDOORXWJRLQJ(,PHVVDJHV

([HFXWHIURP0RQGD\WR7KXUVGD\DW

3(5)2505&9$//6(/(&7,216($//$&7,215(&(,9($



-XQH

()B&2006(59,&(21

75$&(2175$&(B$//2))3*0B)/2: 21$7$B)/2:21&6B5(63216(21),/(6 215287,1*21(175$&(

HILQHGHVWLQDWLRQVIRUFROOHFWLQJPHVVDJHV

IURPD9$1RUGLUHFWO\IURPDSDUWQHU

(67,1$7,21/)

6XSSOLHUDVVLJQHGWKH/RFDO&RGH/2&LQ2GH[

/2&$/&2(/2&(1(67,1$7,21

3(5,2,&SDUDPHWHUJURXSV

3(5,2,&30,1,17(59$/(13(5,2,&

3(5,2,&30,1,17(59$/(13(5,2,&

&UHDWHDIDVWDQGDVORZFKDQQHO

&+$11(/)$67

$OOFROOHFWLRQDFWLRQVYLDWKLVFKDQQHO

UHIHUHQFHWKHIROORZLQJGHVWLQDWLRQ

(67,1$7,21/)

3(5)250 6(1$&7,216(16&+(8/(3(5,2,&30,1(13(5)250

3(5)250 5(&9/)$&7,215(&(,9(7,0($



-XQH

(1&+$11(/

&+$11(/6/2:

$OOGRFXPHQWVWUDQVIHUUHGYLDWKLVFKDQQHOWR

2GH[DUHJLYHQWKHSULRULW\

35,25,7<

3(5)250 6(1$&7,216(16&+(8/(3(5,2,&30,1(13(5)250

(1&+$11(/

(1352*5$0

352*5$0SDUDPHWHUJURXS(;3&RQQHFWLRQWR(;3(,7(

352*5$0(;3

/2*),/(B(;3,5$7,21$5&+,9(216$9(B5(63216(B,1)250$7,2121

HILQLWLRQRIDPLQXWHLQWHUYDO

3(5,2,&3,17(59$/(13(5,2,&

HILQLWLRQRIWKH6(/(&7,21SDUDPHWHUJURXS

&/$666$3WRFROOHFWPHVVDJHVIURP

,QIRUPDWLRQ([FKDQJHZKRVH&/$66DWWULEXWHLV

VHWWR&/$666$3

6(/(&7,21&/$666$35&9&/$665&9&/$66(16(/(&7,21

75$&(2175$&(B$// 2))3*0B)/2:21$7$B)/2:21),/(6 215287,1*21(175$&(

&+$11(/(;3$&&17

6HWWKH,(&/$66DWWULEXWHRIDOORXWJRLQJPHVVDJHV

VHQWYLDWKHFKDQQHO(;3(,7(WR6$3(;3



-XQH

3$7+GLHDFFQW61&/$666$3(;3

6HQGDQGUHFHLYHGRFXPHQWVRQ)ULGD\VDW

PLQXWHLQWHUYDOV

3(5)2506(15(&(,9($&7,215(&(,9($&7,216(16&+(8/($< )5,$3DJH@

$FWLYDWLQJ/RJJLQJ7DEOH7$%>3DJH@

&KHFNLQJ/RJRQ7LPHV7DEOH76.:>3DJH@

&RQILJXULQJ7HOHFRPPXQLFDWLRQV$SSOLFDWLRQV>3DJH@


2YHUYLHZ

-XQH

2YHUYLHZThis section shows you how to configure SAPcomm in the SAP System (R/2 or R/3).It also shows you how to test the configuration in the R/3 System.A number of tables are important here, which effect all or some of the applications:

All applications (EDI, Mail and telecommunications):Tables T164B and TSKWD

Telecommunications applications:T164A, T164B, T1640, T164P, T164U, TMLVW, T164C and T164Y


$FWLYDWLQJ/RJJLQJ7DEOH7$%

-XQH

$FWLYDWLQJ/RJJLQJ7DEOH7$%In R/3: You maintain table T164A.From Release 5.0C of R/2: You maintain table T164B.In this table you can activate the HEXJJLQJ parameter. This parameter lets you control whetherthe CPI-C data exchange between SAPcomm and the SAP system is logged. Please note thatyou should only activate logging for analysis purposes.In this case, only information on the newest CPI-C link between SAPcomm and the SAP Systemis written to table TEDCT.


&KHFNLQJ/RJRQ7LPHV7DEOH76.:

-XQH

&KHFNLQJ/RJRQ7LPHV7DEOH76.:Table TSKWD exists in R/2 as of Release 5.0C, and in R/3 as of Release 1.1.It maintains a separate record for different functions (EDI, mail, and so on) of when SAPcommlast logged on to the SAP system.If you know the times, at which SAPcomm should log onto the SAP system (in accordance withthe SAPcomm time plan in the configuration file), you can use table SKWD to check whetherSAPcomm is keeping to its schedule.You distinguish between different SAPcomm installations via the SAPcomm ID (see Overview[Page 88])


&RQILJXULQJ7HOHFRPPXQLFDWLRQV$SSOLFDWLRQV

-XQH

&RQILJXULQJ7HOHFRPPXQLFDWLRQV$SSOLFDWLRQVThe behavior of the SAP system when dispatching and receiving telecommunication messages(telefax, telex, teletex) is controlled by a group of tables (164A, 164B, 164C, 164O, 164P, 164U,164Y and MLVW).Menu functions are available in R/3 to maintain these tables. These functions are in the menu&RQILJXUDWLRQ, which you can call via transaction code SCOM or the following path:$GPLQLVWUDWLRQ&RPPXQLFDWLRQ6$3FRPP

The configuration options can be divided into 2 categories: Sending:

Automatic selection of logical destination (and an SAP communications server) for thedispatch of a message and the automatic modification of the recipients number.R/3 menu options: 7HVW6HUYHUORFDWLRQ6HUYHUVHOHFWLRQ6HUYHUH[FHSWLRQV&RXQWU\FRGH6\VWHPSDUDPHWHUV.

Receiving:Automatic assignment of an incoming message to a user in the SAP system.R/3 menu options: 6\VWHPSDUDPHWHUVLVWULEXWLRQOLVW.These R/3 menu options and the tables which form their basis (the parameters ofwhich are valid for both R/3 and R/2) are described in detail in the sections whichfollow.

6\VWHP3DUDPHWHUV7$DQG7%

In Tables T164A and T164B (R/2 and R/3-Releases 2.x only), you can make basic settings forsending and receiving messages:

retention period of the messages in the spool format check of recipients numbers (R/2 and R/3-Releases 2.x only) check code page (R/2 and R/3-Releases 2.x only) type of dispatch status report (R/3 only) process incoming messages (R/2 only) search area in incoming messages substitute recipient for incoming messages Test aid Spool formatting in the SAP System (R/3-Release 3.0 only)

6HUYHU/RFDWLRQ72

Each logical destination, that you want to use for the dispatch of telecommunications messagesmust be defined here. A channel with the same name must also be created on an SAPcommunications server for every destination. For more details, refer to "How are DocumentsAllocated to Their Channel? [Page 45] ".Enter the country ID of the location of the respective SAP communications server for everydestination. This is used for automatic country code generation.



-XQH

You can provide a comment for every destination.

6HUYHU6HOHFWLRQ73

This table determines which destination is to be selected for message dispatch. The selectiondepends on:

Telecommunications service (e.g. telefax; In R/3: TELEFAX, in R/2: TF) Document type (currently not supported, always leave the field blank, R/3 only) Country of the recipient (e.g. GB, R/3 only) Area code of the recipients number (e.g. 071) Communication device group (user group-specific, defined by parameter CDG, R/3

Release 3.0 only)When dispatching a message, the entries are processed top down and the specified destinationis used for the first matching entry.The sort ID is used to sort the entries into the order you want.

6HUYHU([FHSWLRQV78

Special cases for automatically adapting the connection can be stored in this table.This allows a local area code to be removed if, for example, it is the same as the local area codein which the SAP communications server is situated, or a special cost-saving abbreviated dialingcode is used in local areas.Depending on the destination and the telecommunications service, the following are specified:

Initial digits of a recipients number to be replaced A series of digits to replace the deleted digits (it can also be empty).

When dispatching a message, the entries are processed top down and the initial digits of arecipients number are replaced at the first match.The field "Key" is a sort indicator and is used to sort the entries into the order you want.

&RXQWU\&RGH70/9:7.7,7-

In R/2 and in R/3 Releases 2.x, the country codes for telefax, telex and teletex are contained intable TMLVW. From Release 3.0 of R/3, these dialling codes are contained in tablesT005K/T005I/T005J.You carry out maintenance as follows: $GPLQLVWUDWLRQ Communication 6$3FRPP,&RQILJXUDWLRQ &RXQWU\FRGH or - from 3.0 also - &RXQWU\FRGHH[FHSWLRQVWHOAll combinations derived from the location countries of SAP communications servers and all thecountries of the possible message recipients must be entered here.When dispatching a message, the country code found under the respective sending and targetcountries - depending on the service - is set before the recipient's user number. The telefaxservice contains a special feature: an area code for the target country can be entered in field "1".If the recipient's number starts with this number, it is removed when inserting the country code.(for example: "0" in Germany, "9" in Spain ... )$VVLJQPHQW 7&5RQO\



-XQH

Output devices (destinations) can be assigned to SAP communications servers in this table.On each server, you can make the following specifications in the SAPcomm configuration:

Server indicator (Parameter IDSAPCOMM) Selection of DESTINATION (including generic)The assignment of destinations to a SAPcomm server is as follows: If you specify a DESTINATION, the server only receives messages for this

destination.

If a DESTINATION is not selected, the server receives messages for all destinationsentered for its indicator (IDSAPCOMM) in table T164C.

If this server indicator is not listed in T164C, the server receives messages for alldestinations beginning with T.

All destinations assigned to a SAPcomm server must also be created as theCHANNEL of a fax/telex component in the configuration of this server.

LVWULEXWLRQ/LVW7



-XQH

Unlike normal printing to paper, the application does not directly specify the requiredoutput device for fax/telex dispatch; It only determines the device type i.e. TELEFAXor TELEX. A suitable output device is automatically determined via special tables. These tablesmust be maintained. Additional tables are required to modify the fax/telex number according to thelocal details of the SAPcomm location (country code, area code etc.) For this, use transaction code SCOM, or choose$GPLQLVWUDWLRQ&RPPXQLFDWLRQ6$3FRPP

Choose the menu options of the &RQILJXUDWLRQ menu to maintain the various tables.A description of these tables is given above.

&UHDWH6$36SRRO2XWSXWHYLFH

To determine a spool output device, use transaction code SPAD.Please note the following:

Choose any name you like for the output device, e.g. TF01.

If the name does not begin with the letter 7 (=telecommunications), or if there areother output devices with begin with 7 and are not fax/telex output devices, youmust also enter the name of this output device in Table T164C.

HYLFHW\SH: It must correspond to the communications subsystem used withSAPcomm. If, in Table TSP09, you marked the field ABAP/4 for the driver TELE (seethe following section "Set SAPscript Printer Driver "), you must always stateTOPCALL for the device type.

)RUPDWWLQJKRVW: Any, it is not analyzed, e.g. host on which SAPcomm is installed. +RVWSULQWHU: Any, it is not analyzed, e.g. 6$3FRPP or 723&$//. HYLFHFODVV: ) for telefax, 7for telex.

$FFHVVPHWKRG: X (=SAPcomm) /34IRUPDW: Any, it is not analyzed, e.g. B &RQYHUVLRQIODJ: Select NO /RFDWLRQDQGPHVVDJH: Any entries 6$3WLWOHSDJH6$3ORFNSULQWHURSHUDWLQJV\VWHPSURPSW: Select NO.After pressing enter, an additional field appears: HVWLQDWLRQKRVW: Any, it is not analyzed, e.g. host on which SAPcomm is installed.

6HW6$3VFULSW3ULQWHUULYHU

To set the SAPscript printer driver, maintain Table TSP09.For this, use Transaction code SM31 or choose6\VWHP 6HUYLFHV 7DEOH 0DLQWHQDQFH.



-XQH

In R/3 Releases 2.x, there must be a X for the entry TELE in the ULYHU column in the $%$3column.In R/3 Release 3.0, there should be an empty field ( , SPACE) for the entry TELE in the ULYHUcolumn in the $%$3 column. This is the prerequisite for format processing of fax documentsdefined by the device type. You should mark the $%$3 field for the driver 7(/( only ifminimum formatting (end of line, line feed) suffices for your purposes. The device type must thenbe TOPCALL (or a defined type with another name).7HVWLQJWKH7HOHFRPPXQLFDWLRQV&RQILJXUDWLRQLQ5

To test the configuration, proceed as follows:1. Check the consistency of the table entries:

Choose$GPLQLVWUDWLRQ &RPPXQLFDWLRQ 6$3FRPP, 8WLOLWLHV &KHFN.2. Test the device assignment and number modification:

For this, choose transaction code SKRT or the menu paths$GPLQLVWUDWLRQ CRPPXQLFDWLRQ 6$3FRPP, 5RXWLQJ 7HVW.After you specify a recipients number and a country ID, an output device (destination)must be found, and the number to be dialled must be modified accordingly.

3. Create a simple message:

Choose $GPLQLVWUDWLRQ &RPPXQLFDWLRQ 6$3FRPP, 8WLOLWLHV 6HQGWHVWID[4. Create a test message

- Choose 2IILFH 2XWER[, RFXPHQW &UHDWH- Create a type RAW document and save it.

Specify target country and recipient number.

- Choose 0DLO 6HQG, RFXPHQW 6HQGGLUHFWH[W )D[.... Fax the message.

- There must now be a new entry in the spool database. To check it, choosetransaction code SP01 or6\VWHP 6HUYLFHV 3ULQW5HTXHVWV

- The output status of the new entry is:DLWLQJ


7KH&RQWURO&RPSRQHQW6&%

-XQH

7KH&RQWURO&RPSRQHQW6&%

2YHUYLHZ>3DJH@

6&%VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH>3DJH@

3(5)2503DUDPHWHU*URXS>3DJH@

7KH5RXWLQJ3DUDPHWHU*URXS>3DJH@

2SHUDWLQJWKH&RPPXQLFDWLRQV6HUYHU>3DJH@

1RWHVRQ7HVWLQJDQG3UREOHP$QDO\VLV>3DJH@


2YHUYLHZ

-XQH

2YHUYLHZThe control component is the central component of the SAP communications server:

It is the first component activated after the start of the communications server. It handles the starting of the individual communication components. It carries out the orderly system shutdown.


6&%VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH

-XQH

6&%VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOHThe identifier of the control component is SCB. You configure the control component in the sameway as the other components of the communications server (the communications components).You therefore insert (just) one SCB parameter group into the configuration file SAPCOMM.CFG.This parameter group has the following structure:352*5$06&%

,*125(B&&B$%257 21_2))!,*125(B7,0(B3/$1 21_2))!23(1B/2*B:,12: 21_2))!

3(5)250 3URJUDP!

7,0(

7,0(

$&7,21XVUVDSFRPVWDUWVFPTXHXH

(13(5)250

5287,1* 6$3&2006(59,&( 1DPH!

6(59,&(3DUDPHWHU!(16(59,&(

(15287,1*

75$&( 21_2))!75$&(3DUDPHWHU!

(175$&(

(1352*5$0

The individual parameters in sub-groups of this group are explained below:,*125(B&&B$%257

Optional. If this parameter is entered (with ON), then the termination of an activatedcommunications component does not automatically result in the termination of all theactivities of the communications server. This parameter is only used for problemanalysis and should not be entered into normal operation.

,*125(B7,0(B3/$1

Optional. If this parameter is entered (with ON), all entries in the SAPcomm time planare ignored. The communications server then only carries out actions based on theuser input via the user interface. This parameter is only used for testing purposesand must not be activated in productive operation.

23(1B/2*B:,12:

Only OS/2: If this parameter is entered and you start the communications server viathe user interface, then the log window is opened automatically at the start of thecommunications server.

3(5)250

The PERFORM parameters are described in PERFORM Parameter Group [Page 75].5287,1*


6&%VSHFLILF(QWULHVLQWKH6$3FRPP&RQILJXUDWLRQ)LOH

-XQH

The ROUTING parameters are described in The Routing Parameter Group [Page 76].

75$&(

The TRACE parameters are described in TRACE Parameter Group [Page 41] .



-XQH

3(5)2503DUDPHWHU*URXSYou can instruct the control component to start any programs controlled by the time plan. Forthis, you create one or more PERFORM parameter groups in the SCB program parameter group,in which you specify the names of the programs to be executed as ACTION parameters.The program is executed asynchronously by the control component. Program start is entered inthe SCB log file, however program output and program termination code are not.If the program to be called generates screen output, and you want to store this output in a file,start the program indirectly: The control component starts a shell script, which in turn starts theprogram to be called, and in the course of this redirects the program output to a file (see examplebelow).Note that the program to be executed must not require any user input.

You would like to print out the number of files waiting for processing withinSAPcomm twice a day, and store the printout in the file XVUVDSFRPORDGFirst, you create the shell script XVUVDSFRPVWDUWVFPTXHXH. It contains, forexample, the following two lines (HP-UX):GDWH!!XVUVDSFRPORDG

VFPTXHXHO!!XVUVDSFRPORDG

Add the following parameter group to parameter group PROGRAM SCB in theSAPcomm configuration file VDSFRPPFIJ3(5)25067$576&048(8(

7,0(

7,0(

$&7,21XVUVDSFRPVWDUWVFPTXHXH

(13(5)250

OS/2:As the program specified as the ACTION parameter is executed from a separatecommand interpreter (cmd.exe), SAPcomm cannot recognize whether it couldeven be started. Even in this case, no error message in entered in the SCB logfile.


7KH5RXWLQJ3DUDPHWHU*URXS

-XQH

7KH5RXWLQJ3DUDPHWHU*URXSThe assignment of an incoming or outgoing document to a channel is made in the 5287,1*parameter group in the 352*5$06&% group of the configuration file SAPCOMM.CFG(exceptions: SAP EDI and SAP telecommunications outgoing documents).In addition to the fundamental purpose of channel assignment, the ROUTING parameter group isalso used to determine the category of incoming documents (MAIL or EDI) for which no type hasbeen determined a priori (such as documents received via X400).The problem of assigning a document to its responsible channel - the routing - has already beendiscussed in the topic How are Documents Allocated to Their Channel? [Page 45] in the sectionon the configuration file. This topic describes the details of the routing statements that have to bemaintained in the configuration file.

([DPSOHRID5287,1*3DUDPHWHU*URXS

The following example illustrates the principle of default channel assignment and specialization(override). For an explanation of the APPLICATION parameter, refer to Classification Groups(SERVICE X400) under the section SERVICE Parameter Groups below.5287,1* 6$3&200

6(59,&( ;

25*$1,=$7,21 6$/(628 (,

72&+$11(/ 6$3$33/,&$7,21 (,

(12872&+$11(/ 6$3$33/,&$7,21 0$,/

(125*$1,=$7,21

28 (,72&+$11(/ 6$3(,$33/,&$7,21 (,

(128

72&+$11(/ 6$3$33/,&$7,21 0$,/

(16(59,&(

6(59,&( 2)7372&+$11(/ 6$3(,

(16(59,&(

(15287,1*

The following assignments are defined for X400 and OFTP documents by these routingstatements.

X400 documents are assigned to different channels: All X400 documents which have the component "Organization" set to "SALES" in the

recipient address are allocated as follows:- If their "Organizational Unit 1" (OU1) is set to "EDI", the application EDI is

allocated to them and they go to channel SAP1.



-XQH

- Otherwise, they are allocated the application MAIL (and they are forwarded to thesame channel "SAP1").

It is not necessary to start component specification with the component with thehighest rank (COUNTRY) (followed by the next lower, and so on; if the components ofa higher rank are missing, then they are taken to be matches during allocation.)

All other X400 documents, in which the component "Organizational Unit 1" (OU1) isset to "EDI" in the recipient address, are allocated to the channel "SAP-EDI".

All other X400 documents are allocated to the channel "SAP2".All incoming documents (OFTP documents) received via the communications component ODXare allocated to the channel "SAP-EDI".

6(59,&(3DUDPHWHU*URXSV

The ROUTING parameter group consists of one or more SERVICE parameter groups. Each ofthese parameter groups contains the routing statements that refer to "their" service.This means that you, for example to forward incoming ODEX messages to one or more SAPsystems, must set up a parameter group SERVICE OTP. The parameter group SERVICE SAP isnot responsible for these messages.Valid SERVICE parameter groups and their application fields are:

SERVICE X400 documents with recipient addressesin X400 format (communicationscomponents X40, SSW...).

SERVICE SNADS documents with recipient addressesin SNADS format.

SERVICE SAP documents with recipient addressesin the SAP format (for example,mail messages between SAP systems).

SERVICE OFTP documents sent or received via theODX communications component.

SERVICE EXPEDITE documents sent or receivedvia IBM Expedite.

SERVICE BCS documents received via the BCScommunications component.

SERVICE FAX fax documents.SERVICE TLX telex documents.

SERVICE TTX teletex documents.Every SERVICE parameter group consists of the following elements:

Optional parameter groups (classification groups):They define subsets of addresses for all messages belonging to the current SERVICEand allocate channels to these subsets for further processing. These parametergroups are called classification groups.

The classification groups have SERVICE-dependent types (that is: address



-XQH

components - COUNTRY, ADMD, PRMD, ORGANIZATION, and so on for SERVICEX400) and can also contain sub-classification groups themselves.

Reference to a default channel. All messages belonging to the current SERVICE thatare not entered by one of the above parameter groups are forwarded to this channel.Example of a classification group:&28175< (

$0 %372&+$11(/ &+$1$33/,&$7,21 0$,/

(1$072&+$11(/ &+$1$33/,&$7,21 0$,/

(1&28175 COUNTRY -> ADMDand so on for X400) and allocating them to a (possibly different) channel.

A more specific channel assig