sap bc administration guide

6$3�%XVLQHVV�&RQQHFWRU$GPLQLVWUDWLRQ�*XLGH

5HOHDVH ��

6$3��$*��é 1HXURWWVWU��é '��:DOOGRUI

��

6$3�6<67(0

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH 6$3�$*

LL 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

&RS\ULJKW

©Copyright 1999 SAP AG. All rights reserved.

No part of this description of functions may be reproduced or transmitted in any form orfor any purpose without the express permission of SAP AG. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft®, WINDOWS® and EXCEL®, NT® and SQL-Server® are registeredtrademarks of Microsoft Corporation.

IBM®, OS/2®, DB2/6000®, AIX®, OS/400® and AS/400® are registered trademarks ofIBM Corporation.

OSF/Motif® is a registered trademark of Open Software Foundation.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

webMethods® is a registered trademark of webMethods Incorporated, Virginia, USA.

INFORMIX®-OnLine for SAP is a registered trademark of Informix SoftwareIncorporated.

UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation.

SAP®, R/2®, R/3®, RIVA®, ABAP/4®, SAPaccess®, SAPmail®, SAPoffice®, SAP-EDI®, SAP Business Workflow®, SAP EarlyWatch®, SAP ArchiveLink®, R/3 Retail®,ALE/WEB®, SAPTRONIC® are registered trademarks of SAP AG.

All rights reserved.

2UGHU�LQIRUPDWLRQ

Please specify the following number to order this manual: 51007899.

6$3�$* 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH iii

7\SRJUDSKLFDO�&RQYHQWLRQV

7\SH�6W\OH 'HVFULSWLRQ

,QWHUIDFH�7H[W Words or characters that appear on the screen. Thisincludes field names, screen titles, pushbuttons, menunames, and menu options.

'RFXPHQW�7LWOH Cross-references to other documentation.

8VHU�(QWU\ Words and characters that you enter exactly as theyappear in the documentation.

�9DULDEOH�8VHU(QWU\!

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

NAME Names of elements in the SAP System. These includeprogram names, transaction codes, table names, ABAPkey words, file names, and directories.

Name File names, path names, program names, user names,parameters, file contents and operating system output.

.(< Keys on the keyboard. These include the function keys,e.g. )�, or the (17(5 key�

,FRQ 'HVFULSWLRQ

1RWH A note. Notes contain important information, e.g.exceptions or special cases.

([DPSOHAn example. Examples illustrate complex procedures orthe syntax for user entries.

&DXWLRQA caution. Cautions help users avoid errors which can,for example, lead to loss of data.


LY 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH


6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH v

&RQWHQWV

&KDSWHU�� ,QWURGXFWLRQ ��

:HOFRPH��

Program Code Conventions...................................................................................1-2

5HODWHG�'RFXPHQWDWLRQ ��

&KDSWHU�� $Q�2YHUYLHZ�RI�WKH�6HUYHU ��

7KH�5ROH�RI�WKH�6HUYHU ��

$UFKLWHFWXUH ��

SAP BC Services ...................................................................................................2-3

Retrieving Data for Services ..................................................................................2-3

+RZ�WKH�6HUYHU�([HFXWHV�6HUYLFHV��

6HFXULW\�)HDWXUHV ��

$XGLW�7UDLO�/RJJLQJ ��

&DFKLQJ ��

/RDG�%DODQFLQJ��

&KDSWHU�� 7KH�5ROH�RI�WKH�$GPLQLVWUDWRU ��

:KDW�'RHV�D�6$3�%&�$GPLQLVWUDWRU�'R" ��

7\SLFDO�$GPLQLVWUDWLYH�5HVSRQVLELOLWLHV ��

The Server Administrator .......................................................................................3-3

5HFHLYLQJ�$GPLQLVWUDWLYH�0HVVDJHV�IURP�WKH�6HUYHU ��

7KH�$GPLQLVWUDWRU�8VHU ��

The Administrator’s Password ...............................................................................3-3

$GGLQJ�%DFNXS�$GPLQLVWUDWRUV ��

&KDSWHU�� 6WDUWLQJ�DQG�6WRSSLQJ�WKH�6HUYHU��

6WDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU��

To start the SAP Business Connector Server ........................................................4-2

Starting the Server from the Command Line..........................................................4-2

To start the SAP Business Connector Server from the command line ..................4-2

:KDW�+DSSHQV�:KHQ�<RX�6WDUW�WKH�6HUYHU"��

How to Tell if the Server is Running Correctly .......................................................4-4

6KXWWLQJ�'RZQ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU��

To shut down the server.........................................................................................4-5

Viewing Active Sessions ........................................................................................4-5

To view active sessions..........................................................................................4-5


YL 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

5HVWDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU��

To restart the server .............................................................................................. 4-6

6HUYHU�5HFRYHU\ ��

Site-Specific Services............................................................................................ 4-6

Recovery and the Log File..................................................................................... 4-6

&KDSWHU�� 8VLQJ�WKH�6HUYHU�$GPLQLVWUDWRU ��

:KDW�LV�WKH�6HUYHU�$GPLQLVWUDWRU" ��

6WDUWLQJ�WKH�6HUYHU�$GPLQLVWUDWRU��

To start the Server Administrator........................................................................... 5-2

%DVLF�2SHUDWLRQ ��

Getting Help........................................................................................................... 5-3

/RJJLQJ�2XW�RI�WKH�6HUYHU�$GPLQLVWUDWRU��

To log out of the Server Administrator................................................................... 5-4

7KH�&RQILJXUDWLRQ�)LOH��

&KDSWHU�� &RQILJXULQJ�WKH�6HUYHU ��

9LHZLQJ�DQG�&KDQJLQJ�/LFHQVLQJ�,QIRUPDWLRQ ��

The License Key.................................................................................................... 6-2

Viewing or Changing the License Key................................................................... 6-2

To view the License Key........................................................................................ 6-3

To change the License Key................................................................................... 6-3

Renewal Reminders .............................................................................................. 6-3

Renewing a Key..................................................................................................... 6-3

Licensed Seats ...................................................................................................... 6-3

To view the current number of active seats and the seat limit .............................. 6-4

&RQILJXULQJ�/LVWHQLQJ�3RUWV ��

Configuring the Primary Listening Port.................................................................. 6-4

To configure the primary listening port .................................................................. 6-4

Adding Listening Ports........................................................................................... 6-5

To add an additional listening port......................................................................... 6-5

Deleting a Listening Port ....................................................................................... 6-6

To delete a listening port ....................................................................................... 6-6

Enabling/Disabling a Listener ................................................................................ 6-7

To disable a listening port...................................................................................... 6-7

To enable a listening port ...................................................................................... 6-7

&RQILJXULQJ�:HE�$XWRPDWLRQ�6HWWLQJV ��

Overview of the Web Automation Settings............................................................ 6-8


6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH vii

Specifying Web Automation Settings .....................................................................6-9

To set the Web Automation Defaults .....................................................................6-9

6SHFLI\LQJ�D�3UR[\�6HUYHU ��

To specify a Proxy Server ....................................................................................6-10

Bypassing a Proxy Server ....................................................................................6-10

To bypass a proxy server .....................................................................................6-11

6HWWLQJ�WKH�7LPHRXW�/LPLW ��

To set the Timeout Limit.......................................................................................6-12

:RUNLQJ�ZLWK�/RJ�)LOHV ��

What Kind of Log Files Does the Server Maintain? .............................................6-12

Where are the Log Files?.....................................................................................6-13

How Much Information is Recorded? ...................................................................6-13

To configure the contents of the server.log file ....................................................6-14

How Long Does the Server Maintain its Logs?....................................................6-14

Configuring Log File Rotation...............................................................................6-15

To configure log file rotation.................................................................................6-15

Specifying Error Message Recipients ..................................................................6-16

To specify the error message recipients ..............................................................6-17

&KDSWHU�� 0DQDJLQJ�8VHUV�DQG�*URXSV ��

8VHUV�DQG�*URXSV ��

Purpose of Users and Groups................................................................................7-2

'HILQLQJ�D�8VHU�$FFRXQW��

Predefined User Accounts .....................................................................................7-4

Adding User Accounts............................................................................................7-5

To add a user account to the server ......................................................................7-5

Removing User Accounts.......................................................................................7-5

To delete a user account from the server ..............................................................7-5

Changing Passwords .............................................................................................7-6

To change a password ...........................................................................................7-6

'HILQLQJ�*URXSV ��

Predefined Groups .................................................................................................7-7

Adding Groups .......................................................................................................7-8

To add a new group to the server ..........................................................................7-8

Removing Groups ..................................................................................................7-8

To delete a group from the server..........................................................................7-8

Viewing or Changing Group Membership ..............................................................7-9


YLLL 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

To view or change the group membership for a group.......................................... 7-9

&KDSWHU�� 0DQDJLQJ�6HUYHU�6HFXULW\ ��

2YHUYLHZ�RI�6HFXULW\ ��

&RQWUROOLQJ�:KR�&DQ�&RQILJXUH�DQG�0DQDJH�WKH�6HUYHU ��

Granting administrative privileges to a user .......................................................... 8-2

&RQWUROOLQJ�:KR�&DQ�&UHDWH��0RGLI\��DQG�'HOHWH�6HUYLFHV��

Granting developer privileges to a user................................................................. 8-3

6HFXULQJ�&RPPXQLFDWLRQV�ZLWK�WKH�6HUYHU ��

Background About SSL ......................................................................................... 8-4

SSL and the SAP Business Connector Server...................................................... 8-5

Checklist for Using SSL......................................................................................... 8-6

Items You Need Before Configuring SSL.............................................................. 8-7

Using OpenSSL project SSL toolkit to obtain items required for SSL................... 8-8

Configuring the Server to Use SSL ....................................................................... 8-9

To configure the server to use SSL for secure communications........................... 8-9

&RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�DQG�)LOHV�ZLWK�$&/V��

About ACLs and the Precedence Setting............................................................ 8-10

Setting the Precedence ....................................................................................... 8-12

To change the Precedence ................................................................................. 8-12

Predefined ACLs.................................................................................................. 8-12

Creating ACLs ..................................................................................................... 8-13

To create an ACL................................................................................................. 8-13

Updating ACLs..................................................................................................... 8-13

To update an ACL................................................................................................ 8-13

Deleting ACLs...................................................................................................... 8-14

To delete an ACL................................................................................................. 8-14

How ACLs Work with Interfaces and Services .................................................... 8-15

When No ACL is Assigned to a Service—Default ACL....................................... 8-15

When You Assign an ACL to an Interface........................................................... 8-15

When You Assign an ACL to a Service............................................................... 8-16

Summary of ACL Inheritance .............................................................................. 8-16

Assigning ACLs to Services and Interfaces ........................................................ 8-16

To assign an ACL to a Service or Interface......................................................... 8-16

To remove an ACL from a Service or Interface................................................... 8-17

Assigning ACLs to Files the Server Can Serve................................................... 8-17


6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH ix

&RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�%\�/LVWHQLQJ�3RUW��

To control access to SAP BC services by port.....................................................8-18

To remove interfaces and services from the Interface/Service List .....................8-20

To reset a port to the default ................................................................................8-20

$XWKHQWLFDWLQJ�&OLHQWV ��

Client Certificates .................................................................................................8-21

Checklist for Using Client Certificates ..................................................................8-22

Items You Need Before Configuring the Server to Request Client Certificates...8-22

Configuring the Server to Request Client Certificates .........................................8-22

To configure the server to request client certificates ...........................................8-22

Basic Authentication (User Names and Passwords) ...........................................8-23

&KDSWHU�� 8VLQJ�DQ�([WHUQDO�'LUHFWRU\��/'$3�RU�1,6��

2YHUYLHZ�RI�8VLQJ�([WHUQDO�'LUHFWRULHV��

How the Server Uses Externally-Defined Information............................................9-2

When the Server Accesses Externally-Defined Information ..................................9-3

&RQILJXULQJ�WKH�6HUYHU�WR�8VH�DQ�([WHUQDO�'LUHFWRU\ ��

Configuring the Server to Use LDAP .....................................................................9-4

To configure the server to use LDAP.....................................................................9-4

Configuring the Server to Use NIS.........................................................................9-7

To configure the server to use NIS ........................................................................9-7

Stopping Use of an External Directory ...................................................................9-8

To stop using an external directory ........................................................................9-8

&RQVLGHUDWLRQV�IRU�8VHU�$FFRXQWV�DQG�*URXSV��

$XWKHQWLFDWLQJ�([WHUQDO�&OLHQWV ��

*UDQWLQJ�$GPLQLVWUDWRU�3ULYLOHJHV�WR�([WHUQDO�8VHUV��

To grant administrator privileges to an externally-defined user ...........................9-10

*UDQWLQJ�'HYHORSHU�3ULYLOHJHV�WR�([WHUQDO�8VHUV ��

To grant developer privileges to an externally-defined user ................................9-11

*UDQWLQJ�$FFHVV�WR�6HUYLFHV�DQG�)LOHV�WR�([WHUQDO�8VHUV ��

&KDSWHU��0DQDJLQJ�3DFNDJHV��

8VLQJ�3DFNDJHV��

Predefined Packages ...........................................................................................10-2

+RZ�WKH�6HUYHU�6WRUHV�3DFNDJH�,QIRUPDWLRQ ��

Manifest File .........................................................................................................10-4

)LQGLQJ�,QIRUPDWLRQ�DERXW�<RXU�3DFNDJHV��

Viewing the Packages that Reside on Your Server .............................................10-5


[ 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

To view the packages that reside on the server.................................................. 10-5

Determining Whether the Server Successfully Loaded the Package.................. 10-5

Determining Whether the Package is Enabled or Disabled ................................ 10-6

Displaying Information about a Package............................................................. 10-6

To display information about a package.............................................................. 10-7

Displaying Documentation for a Package ........................................................... 10-8

To access the home page for a package ............................................................ 10-8

To access any Web document for a package ..................................................... 10-9

:RUNLQJ�ZLWK�3DFNDJHV��

Creating a Package ........................................................................................... 10-10

To create a package.......................................................................................... 10-10

Activating a Package ......................................................................................... 10-10

To activate a package ....................................................................................... 10-10

Reloading a Package ........................................................................................ 10-11

To reload a package.......................................................................................... 10-11

Enabling a Package........................................................................................... 10-11

To enable a package ......................................................................................... 10-11

Disabling a Package.......................................................................................... 10-11

To disable a package ........................................................................................ 10-12

Deleting a Package ........................................................................................... 10-12

To delete a package .......................................................................................... 10-12

Recovering a Package ...................................................................................... 10-13

To recover a package........................................................................................ 10-13

Identifying a Version Number for a Package..................................................... 10-13

To identify a version number for a package ...................................................... 10-13

Identifying Package Dependencies ................................................................... 10-13

To identify package dependencies for a package............................................. 10-14

Removing a Package Dependency ................................................................... 10-14

To remove a package dependency for a package ............................................ 10-14

&RS\LQJ�3DFNDJHV�IURP�2QH�6HUYHU�WR�$QRWKHU ��

Overview of Package Replication...................................................................... 10-14

Who Can Subscribe?......................................................................................... 10-15

Guidelines for Using Package Replication ........................................................ 10-16

The Publishing Server ....................................................................................... 10-16

Displaying Subscribers ...................................................................................... 10-17

To display the subscribers for a package.......................................................... 10-17


6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH xi

Specifying Subscribers.......................................................................................10-17

To specify subscribers........................................................................................10-17

Removing Subscribers for a Package................................................................10-18

To remove subscribers.......................................................................................10-18

Publishing a Package.........................................................................................10-18

To create the distribution file ..............................................................................10-19

To send the distribution file ................................................................................10-19

The Subscribing Server......................................................................................10-20

Displaying Packages That Your Server Subscribes To .....................................10-20

To display the packages to which your server subscribes.................................10-20

Subscribing to a Package from Another Server.................................................10-20

To subscribe to a package from another server ................................................10-21

Canceling a Subscription....................................................................................10-21

To cancel your subscription to a package on another server ............................10-21

Installing a Package Published by Another Server ............................................10-22

To install a package that was published from another server............................10-22

&KDSWHU��0DQDJLQJ�6HUYLFHV��

$ERXW�6HUYLFHV ��

)XOO\�4XDOLILHG�6HUYLFH�1DPHV��

Package Names and Service Names ..................................................................11-3

)LQGLQJ�,QIRUPDWLRQ�DERXW�6HUYLFHV�DQG�,QWHUIDFHV ��

Listing Interfaces and Services ............................................................................11-4

To list interfaces and services..............................................................................11-4

Displaying Information about a Service................................................................11-4

To display information about a service.................................................................11-4

:RUNLQJ�ZLWK�6HUYLFHV ��

Registering Services ............................................................................................11-6

To register a service.............................................................................................11-6

Unregistering Services .........................................................................................11-7

To unregister a service.........................................................................................11-7

Editing Service Information ..................................................................................11-8

To edit service information ...................................................................................11-8

Manually Adding a Service to the Server .............................................................11-9

To manually add a service to the server ..............................................................11-9

Testing Services.................................................................................................11-10

To test a service .................................................................................................11-10


[LL 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

5XQQLQJ�6HUYLFHV�:KHQ�3DFNDJHV�DUH�/RDGHG�8QORDGHG ��

What is a Startup Service? ................................................................................ 11-11

What is a Shutdown Service?............................................................................ 11-11

Guidelines for Using Startup/Shutdown Services.............................................. 11-11

Identifying Startup and Shutdown Services....................................................... 11-12

To identify startup and shutdown services ........................................................ 11-12

Removing Startup and Shutdown Services....................................................... 11-12

To remove startup and shutdown services........................................................ 11-12

6FKHGXOLQJ�6HUYLFHV�WR�([HFXWH�DW�6SHFLILHG�7LPHV ��

Scheduling a User Task .................................................................................... 11-13

Using the Once Option ...................................................................................... 11-13

Using the Repeating Option .............................................................................. 11-13

Using the Complex Option................................................................................. 11-14

To schedule the execution of a service ............................................................. 11-16

Viewing Scheduled User Tasks........................................................................ 11-18

To view scheduled user tasks ........................................................................... 11-18

Updating Scheduled User Tasks....................................................................... 11-18

To update a scheduled user task ...................................................................... 11-18

Canceling Scheduled User Tasks ..................................................................... 11-18

To cancel a scheduled user task....................................................................... 11-18

Viewing the Scheduled System Tasks .............................................................. 11-18

To view the scheduled system tasks................................................................. 11-18

&KDSWHU��&DFKLQJ�6HUYLFH�5HVXOWV ��

:KDW�LV�&DFKLQJ"��

7\SHV�RI�6HUYLFHV�WR�&DFKH��

Services Suited for Caching ................................................................................ 12-2

Services You Should Not Cache ......................................................................... 12-3

&RQWUROOLQJ�+RZ�WKH�6HUYHU�8VHV�&DFKLQJ ��

6HWWLQJ�WKH�&DFKLQJ�&RQWUROV�IRU�D�6HUYLFH ��

To set the cache controls for a service................................................................ 12-4

5HVHWWLQJ�WKH�&DFKH ��

To reset the cache for all services....................................................................... 12-5

To reset the cache for a specific service ............................................................. 12-5

9LHZLQJ�6HUYLFH�6WDWLVWLFV ��

To monitor the performance of your cache ......................................................... 12-6

&KDSWHU��&RQILJXULQJ�$FFHVV�WR�'DWDEDVH�6\VWHPV��


6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH xiii

'DWDEDVH�&RQQHFWLRQ�,QIRUPDWLRQ��

Pre-Loading JDBC Drivers at Server Initialization ...............................................13-2

Making the Java Classes for JDBC Drivers Accessible.......................................13-3

,GHQWLI\LQJ�'DWDEDVH�$OLDVHV��

To identify a database alias .................................................................................13-3

8SGDWLQJ�,QIRUPDWLRQ�IRU�'DWDEDVH�$OLDVHV ��

To update information for a database alias..........................................................13-5

'HOHWLQJ�'DWDEDVH�$OLDVHV��

To delete a database alias ...................................................................................13-5

&KDSWHU��&RQILJXULQJ�*XDUDQWHHG�'HOLYHU\��

$ERXW�*XDUDQWHHG�'HOLYHU\ ��

&RQILJXULQJ�WKH�6HUYHU�IRU�*XDUDQWHHG�'HOLYHU\ ��

Settings Shared by Both Inbound and Outbound Transactions...........................14-3

Settings for Inbound Transactions .......................................................................14-3

Settings for Outbound Transactions.....................................................................14-5

$GPLQLVWHULQJ�*XDUDQWHHG�'HOLYHU\ ��

Shutting Down Guaranteed Delivery....................................................................14-7

To shut down guaranteed delivery .......................................................................14-7

Reinitializing Guaranteed Delivery .......................................................................14-7

Inbound Transactions...........................................................................................14-7

To reinitialize guaranteed delivery for inbound transactions................................14-8

Outbound Transactions........................................................................................14-8

To reinitialize guaranteed delivery for outbound transactions..............................14-8

Testing Guaranteed Delivery................................................................................14-9

To test guaranteed delivery..................................................................................14-9

Specifying an E-Mail Address for Error Messages ............................................14-10

To set the e-mail address using the Server Administrator .................................14-10

To set the e-mail address in the server.cnf file ..................................................14-10

To test error message delivery...........................................................................14-10

$SSHQGL[�$6$3�%XVLQHVV�&RQQHFWRU�6HUYHU�'HSOR\PHQW�&KHFNOLVW �� $��

,QWURGXFWLRQ�� $��

67$*(��,QVWDOODWLRQ�� $��

67$*(��%DVLF�&RQILJXUDWLRQ�� $��

67$*(��6HWWLQJ�8S�8VHUV��*URXSV��DQG�$&/V�� $��

67$*(��3XEOLVKLQJ�3DFNDJHV�� $��

67$*(��&RQILJXULQJ�'DWDEDVH�&RQQHFWLRQV �� $��


[LY 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

67$*(��,QVWDOOLQJ�5XQ�7LPH�&ODVVHV ��$��

67$*(��6HWWLQJ�8S�6HFXULW\ ��$��

67$*(��6WDUWXS�DQG�7HVW��$��

67$*(��$UFKLYH�6RXUFHV��$��

$SSHQGL[�%6HUYHU�&RQILJXUDWLRQ�3DUDPHWHUV��%��

,QWURGXFWLRQ��%��

ZDWW�GHEXJ��%��

ZDWW�GHEXJ��%��

ZDWW�QHW� %��

ZDWW�SUR[\� ��%��

ZDWW�VHUYHU��%��

ZDWW�VHFXULW\��%��

ZDWW�W[� %��

$SSHQGL[�&6HUYHU�/RJ�)LOHV ��&��

7KH�$XGLW�/RJ��&��

7KH�(UURU�/RJ ��&��

7KH�6HUYHU�/RJ��&��

7KH�6HVVLRQ�/RJ ��&��

7KH�6WDWLVWLFV�/RJ��&��

7KH�7UDQVDFWLRQ�/RJV ��&��

$SSHQGL[�',1'(;��'��

6$3�$* ,QWURGXFWLRQ

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH ��

&KDSWHU�� ,QWURGXFWLRQ

Welcome! ................................................................................. 1-2

Program Code Conventions ..................................................... 1-2

Related Documentation............................................................ 1-3

,QWURGXFWLRQ 6$3�$*

:HOFRPH�

�� 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

� :HOFRPH�

This guide is for the administrator of a SAP Business Connector Server. It provides anoverview of how the server operates and explains common administrative tasks such as:

• Starting and stopping the server

• Configuring the server

• Setting up user accounts and security

• Managing packages and services

�3URJUDP�&RGH�&RQYHQWLRQV

For programming code and command syntax, this document uses the followingtypographical conventions:

&RQYHQWLRQ ([DPSOH

Keywords and values that you musttype exactly as printed are shown intypewriter font.

%CoSymbol%

Variable values or parameters thatyou must supply are shown in italics.

%9DU1DPH%

Keywords or values that are optionalare enclosed in [ ]. Do not type the [ ]symbols in your own code.

%loop /RRS9DU [null=NullValue]%

6$3�$* ,QWURGXFWLRQ

3URJUDP�&RGH�&RQYHQWLRQV

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH 1-3

� 5HODWHG�'RFXPHQWDWLRQ

The following documents are companions to this guide. Some documents are in PDFformat and others are in HTML.

5HIHU�WR�WKLV�ERRN« )RU«

6$3�%XVLQHVV&RQQHFWRU'HYHORSHUV�*XLGH

Information about how to SAP BC services. It also containsinformation about creating client applications, working withoutput templates, and accessing databases through SAPBusiness Connector Server. This book is for developers.

You will find this book at:

��VDSEF\developer\doc\SAPBCAdministrationGuide.pdf

6$3�%XVLQHVV&RQQHFWRU�$3,5HIHUHQFH

Descriptions of the Java classes and built-in services you use tocreate SAP BC services. This reference is aimed a developerswho build SAP BC services.

You will find this reference at:

��VDSEF\server\doc\API

6$3�%XVLQHVV&RQQHFWRU�2QOLQH5HIHUHQFH

Information about the controls in the SAP Business ConnectorServer screens.

You can access the online reference by selecting the Help tabon a Server Administrator screen.

,QWURGXFWLRQ 6$3�$*

5HODWHG�'RFXPHQWDWLRQ


6$3�$* $Q�2YHUYLHZ�RI�WKH�6HUYHU


&KDSWHU��$Q�2YHUYLHZ�RI�WKH�6HUYHU

The Role of the Server ............................................................. 2-2

Architecture .............................................................................. 2-2

How the Server Executes Services .......................................... 2-4

Security Features ..................................................................... 2-5

Audit-Trail Logging ................................................................... 2-5

Caching .................................................................................... 2-5

Load Balancing ........................................................................ 2-6

$Q�2YHUYLHZ�RI�WKH�6HUYHU 6$3�$*

7KH�5ROH�RI�WKH�6HUYHU


� 7KH�5ROH�RI�WKH�6HUYHU

The SAP Business Connector Server hosts packages that contain services and relatedfiles. The server comes with several packages. For example, it includes packages thatcontain built-in services that your developers might want to invoke from their services orclient applications and services that demonstrate some of the features. You can createadditional packages to hold the services that your developers create. Your developers cancreate services that perform functions, such as, integrating your business systems withthose of your partners, retrieving data from legacy systems, accessing and updatingdatabases, or performing Web automation.

The SAP Business Connector Server provides an environment for the orderly, efficient,and secure, execution of SAP BC services. It decodes client requests, identifies therequested services, invokes the services, passes data to them in the expected format,encodes the output produced by the services, and returns output to the clients.

Additionally, the server authenticates clients, verifies that they are authorized to executethe requested service, maintains audit-trail logs, and promotes throughput using facilitiessuch as service result caching.

� $UFKLWHFWXUH

The SAP Business Connector Server listens for client requests on one or more ports. Youcan associate the type of listener that the server uses for each port. The server supportsHTTP, HTTPS, and FTP listeners.

When applications are built around the thin client, the application uses an HTTP orHTTPS listener for communication with the server. When using HTTP or HTTPSlisteners, the clients communicate using the webMethods Remote Procedure Call (RPC).Because the server supports both HTTP and HTTPS, it can listen on an HTTP port fornon-secure client requests and an HTTPS port for secure requests.

To interact with the server without using the webMethods RPC, use an FTP listener. Atypical use for an FTP listener is to get a directory listing, change to the directory thatcontains the service you want to invoke, put a file that contains input to the service, andrun the service. The server returns the output from the service to the directory in whichthe service resides.

You can define as many ports as you want. When you initially install the server, it hastwo listening ports defined—an HTTP listening port at 5555 and an FTP listening port at8021.


6$3�%&�6HUYLFHV


7KH�6HUYHU�/LVWHQV�IRU�5HTXHVWV�RQ�3RUWV�WKDW�<RX�6SHFLI\

6$3�%XVLQHVV�&RQQHFWRU6HUYHU

+773/LVWHQHU

+7736/LVWHQHU

+773�UHTXHVWV

+7736�UHTXHVWV

)73/LVWHQHU

)73�UHTXHVWV

�6$3�%&�6HUYLFHV

Client requests involve executing one or more SAP BC services. The server maintainssuccessfully loaded services as runnable objects within the server’s program space.

When you initialize the server, the server loads the services that are contained in enabledpackages into memory. When you or another administrator enable a disabled package, theserver loads services that are in that package.

6HUYLFHV�([HFXWH�ZLWKLQ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU·V�9LUWXDO�0DFKLQH


+773/LVWHQHU

+7736/LVWHQHU

6HUYLFH�$

6HUYLFH�%

6HUYLFH�&)73/LVWHQHU

When a client invokes a service, that service runs as a thread within the SAP BusinessConnector Server program. Depending on what function the service is to accomplish, itcan also create additional threads to perform tasks simultaneously.

�5HWULHYLQJ�'DWD�IRU�6HUYLFHV

Tasks that services perform often include retrieving data from data sources. The servercan retrieve data (for example, XML and HTML data) from local data sources or byissuing HTTP or HTTPS requests to resources such as Web servers and JDBC-enableddatabases. When the server accesses data from external data sources, you can optionallyroute either protocol (HTTP or HTTPS) through a proxy server.


+RZ�WKH�6HUYHU�([HFXWHV�6HUYLFHV


7KH�6HUYHU�*HWV�'DWD�IURP�/RFDO�5HVRXUFHV�RU�5HVRXUFHV�RQ�WKH�,QWHUQHW

%�%�,QWHJUDWLRQ�6HUYHU

+773�5HTXHVWV

+7736�5HTXHVWV

3UR[\�6HUYHU

3UR[\�6HUYHU

,QWHUQHW

RSWLRQDO


+773/LVWHQHU

+7736/LVWHQHU

)73/LVWHQHU

/RFDO�'DWD�6RXUFH

6HUYLFH�$

6HUYLFH�%

6HUYLFH�&

� +RZ�WKH�6HUYHU�([HFXWHV�6HUYLFHV

When the SAP Business Connector Server receives a request from a client, it performsthe following actions:

1. The server authenticates the client.

2. If a session already exists for the client, the server uses the existing session. If onedoes not exist, the server creates a session.

3. The server determines the content-type of the service request so it can prepare datafor the requested service.

4. The server uses the supplied service name to look up the service.

5. The server determines whether access to the requested service is being controlledbased on the listening port on which the request came in. If there is no restriction, theserver continues with the execution of the service.

6. The server looks up the Access Control List (ACL) for the service and, using theACL, determines whether the client is to be granted access to the service. If the ACLindicates that the client is allowed to access the service, the server continues with theexecution of the service.

7. The server adds an entry to the Audit Log to mark the start of the request.

8. The server starts gathering service statistics for the service.

9. The server checks to see if the results for this service are cached. If they are, theserver returns the cached results. If they are, the server invokes the service. If theservice is a flow service, which can be comprised of several services, it invokes eachservice in the flow.

1RWH

For each service in a flow, the server performs steps 4 through 11.


5HWULHYLQJ�'DWD�IRU�6HUYLFHV


10. The server ends the gathering of server statistics for the service.

11. The server adds an entry to the Audit Log to mark the end of the request.

12. The server encodes the service results as specified by the content type.

13. The server returns the results to the client.

� 6HFXULW\�)HDWXUHV

The SAP Business Connector has several built-in security mechanisms to protect servicesfrom unauthorized access, prevent unauthorized administration of the SAP BusinessConnector Server, and to prevent data from being intercepted during transmission.

• It requires clients to present valid credentials (i.e., user name and password or a clientcertificate) in order to connect to the server.

• It controls access to individual services by user groups. This mechanism is providedthrough the use of Access Control Lists (ACLs) that you associate with a service.

• It allows you to control access to services based on the port on which a servicerequest is received.

• It requires clients to present valid credentials that have Administrator privilegesbefore allowing access to SAP Business Connector Server Administrator functions.

• It allows you to configure an Administrator port. When you have an administratorport, requests to administer the SAP Business Connector Server are accepted onlythrough the Administrator port.

• It supports encrypted conversations through Secure Sockets Layer (SSL).

For additional information about the server’s security features, refer to 0DQDJLQJ�6HUYHU6HFXULW\ on page 8-1.

� $XGLW�7UDLO�/RJJLQJ

The SAP Business Connector Server keeps several log files to maintain an audit-trail ofthe services that execute and errors that occur. It also maintains other log files to supportguaranteed delivery and maintain performance statistics.

You can specify the level of detail you want to maintain in a log and how much historicalinformation you want to keep.

For additional information about working with the log files, see :RUNLQJ�ZLWK�/RJ�)LOHVon page 6-12.

� &DFKLQJ

Caching is an optimization feature available for stateless services. You activate it on aservice-by-service basis. When you enable caching, the server saves the serviceinvocation results in a local cache for a specified period of time. While the results are in


/RDG�%DODQFLQJ


cache, rather than re-invoking the service, the server can quickly retrieve the serviceresults for subsequent clients requests for the service.

Caching can significantly improve response time of services that retrieve informationfrom busy data sources such as high-traffic commercial Web servers or databases.

For additional information about using cache, see &DFKLQJ�6HUYLFH�5HVXOWV on page 12-1.

� /RDG�%DODQFLQJ

Load balancing is an optimizing feature you use with clustered SAP Business ConnectorServers. Load balancing allows a server to automatically refer a client request to anotherserver if it is too busy to handle the request itself. To use this feature, you must use thewebMethods High-Availability Option, which uses a central database to maintain thestatus of SAP BC services running in the cluster. For more information, refer to theZHE0HWKRGV�+LJK�$YDLODELOLW\�2SWLRQ�8VHU�*XLGH.

6$3�$* 7KH�5ROH�RI�WKH�$GPLQLVWUDWRU


&KDSWHU��7KH�5ROH�RI�WKH�$GPLQLVWUDWRU

What Does a SAP BC Administrator Do?................................. 3-2

Typical Administrative Responsibilities .................................... 3-2

Receiving Administrative Messages from the Server ............... 3-3

The Administrator User ............................................................ 3-3

Adding Backup Administrators ................................................. 3-4

7KH�5ROH�RI�WKH�$GPLQLVWUDWRU 6$3�$*

:KDW�'RHV�D�6$3�%&�$GPLQLVWUDWRU�'R"


� :KDW�'RHV�D�6$3�%&�$GPLQLVWUDWRU�'R"

In a SAP Business Connector environment, the administrator is responsible for installing,configuring, and maintaining the SAP Business Connector Server. He or she is alsoresponsible for ensuring the server is secure, available to clients, and running at peakperformance. Usually, one person is appointed as the administrator, although most sitesidentify at least one other person to act as a backup.

� 7\SLFDO�$GPLQLVWUDWLYH�5HVSRQVLELOLWLHV

If you are the SAP Business Connector Server Administrator for your site, you might beinvolved in some or all of the following activities.

g ,QVWDOOLQJ�DQG�XSJUDGLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU 6HUYHU��which includes taskssuch as equipping the server computer with appropriate hardware and software,downloading and installing the server program, and implementing upgrades as needed.

g 6WDUWLQJ�DQG�VWRSSLQJ�WKH�VHUYHU� which includes shutting down the server whennecessary (e.g., for routine maintenance or reconfiguration) and restarting it afterwards. Italso includes performing your site’s standard recovery procedures following a hardware orsoftware failure of the server computer. For information about these activities, refer to6WDUWLQJ�DQG�6WRSSLQJ�WKH�6HUYHU on page 4-1.

g &RQILJXULQJ�VHUYHU�VHWWLQJV� which includes setting basic operating parameters such asthe maximum session limits, log file options, and HTTP port assignments. For informationabout these activities, refer to &RQILJXULQJ�WKH�6HUYHU on page 6-1.

g $GPLQLVWHULQJ�XVHUV�DQG�JURXSV, which includes defining user names and passwords forauthorized users and assigning them to groups. For information about this task, refer to0DQDJLQJ�8VHUV�DQG�*URXSV on page 7-1. Alternatively, you can configure the server toacquire user and group information from an external system (e.g., LDAP or NIS). Formore information, refer to 8VLQJ�DQ�([WHUQDO�'LUHFWRU\��/'$3�RU�1,6� on page 9-1.

g $GPLQLVWHULQJ�VHUYHU�VHFXULW\, which includes identifying other administrators,assigning access controls to individual SAP BC services, and configuring the server’s useof digital certificates. For more information about this task, refer to 0DQDJLQJ�6HUYHU6HFXULW\ on page 8-1.

g 0DQDJLQJ�6$3�%&�SDFNDJHV�DQG�VHUYLFHV, which includes tasks such as creating newpackages, activating/deactivating SAP BC services, and updating services and/or packagesas necessary. For more information about this task, refer to 0DQDJLQJ�3DFNDJHV on page10-1 and 0DQDJLQJ�6HUYLFHV on page 11-1.

6$3�$* 7KH�5ROH�RI�WKH�$GPLQLVWUDWRU

7KH�6HUYHU�$GPLQLVWUDWRU


g 2SWLPL]LQJ�VHUYLFH�SHUIRUPDQFH, which includes setting up controls for caching theresults of services. For information about improving service performance, refer to &DFKLQJ6HUYLFH�5HVXOWV on page 12-1.

�7KH�6HUYHU�$GPLQLVWUDWRU

The "Server Administrator" is the utility you use to accomplish administrative tasks. Youuse it to monitor server activity, examine log information, add users, enable/disableservices, and adjust the server’s performance features. For information about the ServerAdministrator, see 8VLQJ�WKH�6HUYHU�$GPLQLVWUDWRU on page 5-1.

� 5HFHLYLQJ�$GPLQLVWUDWLYH�0HVVDJHV�IURP�WKH�6HUYHU

The SAP Business Connector Server issues e-mail messages for a variety of failureconditions (for example, internal errors, binding errors, and transaction manager errors).As an administrator, you are the one who should receive these messages and takeappropriate action when errors occur.

To ensure that you (or an appropriate alternate) receive messages from the server, youmust set the 0DLO parameters using the Server Administrator as described in 6SHFLI\LQJ(UURU�0HVVDJH�5HFLSLHQWV on page 6-16.

� 7KH�$GPLQLVWUDWRU�8VHU

Every SAP Business Connector Server is installed with a predefined user account called"Administrator". By default, this user is the only one who can perform administrativetasks with the System Administrator.

�7KH�$GPLQLVWUDWRU¶V�3DVVZRUG

The predefined password assigned to the Administrator user account is "manage".

&DXWLRQ

Change this password LPPHGLDWHO\ after installing the SAP Business ConnectorServer. Otherwise, your server will be vulnerable to anyone who knows the defaultpassword that are installed on the servers.

To learn how to change passwords, see &KDQJLQJ�3DVVZRUGV on page 7-6.

7KH�5ROH�RI�WKH�$GPLQLVWUDWRU 6$3�$*

$GGLQJ�%DFNXS�$GPLQLVWUDWRUV


� $GGLQJ�%DFNXS�$GPLQLVWUDWRUV

It is a good idea to designate at least one individual as a “backup administrator,” who canadminister the SAP Business Connector Server when you are not available.

To add a backup administrator to your server, create a regular user account for the user (ifhe or she does not already have one); then add that user account to the "Administrators"group.

Only members of the "Administrators" group can use the Server Administrator. Forinformation about creating user accounts and adding them to groups, refer to 0DQDJLQJ8VHUV�DQG�*URXSV on page 7-1.

1RWH

If you use an external directory for user and group information, refer to *UDQWLQJ$GPLQLVWUDWRU�3ULYLOHJHV�WR�([WHUQDO�8VHUV on page 9-10 for information about addingadministrators.

6$3�$* 6WDUWLQJ�DQG�6WRSSLQJ�WKH�6HUYHU


&KDSWHU��6WDUWLQJ�DQG�6WRSSLQJ�WKH�6HUYHU

Starting the SAP Business Connector Server .......................... 4-2

What Happens When You Start the Server?............................ 4-4

How to Tell if the Server is Running Correctly.......................... 4-4

Shutting Down the SAP Business Connector Server ............... 4-5

Restarting the SAP Business Connector Server ...................... 4-5

Server Recovery ...................................................................... 4-6

6WDUWLQJ�DQG�6WRSSLQJ�WKH�6HUYHU 6$3�$*

6WDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU


� 6WDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU

The SAP Business Connector Server must be running in order for clients to execute SAPBC services. If you are using the server in a development environment, it must be runningin order for your developers to build, update, and test services using the SAP BusinessConnector Developer.

�7R�VWDUW�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU

Choose 3URJUDPV� �6$3�%&� �6$3�%XVLQHVV�&RQQHFWRU�6HUYHU from the windows startmenu.

�6WDUWLQJ�WKH�6HUYHU�IURP�WKH�&RPPDQG�/LQH

There are times when it is useful to start the server from the command line. Starting theserver this way allows you to override certain settings in the configuration file. It also letsyou start the server in GHEXJ mode, so you can record or display server activity.

�7R�VWDUW�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU�IURP�WKH�FRPPDQG�OLQH

1. At a command line, type the following command to switch to the server’s homedirectory:

cd sapbc\server

2. Type the following command to start the server:

For Windows: bin\server.bat –switch –switch …

where VZLWFK is any of the following:

6ZLWFK 'HVFULSWLRQ

-port SRUW1XPEHU Specifies the port on which the server listens forHTTP requests.

SRUW1XPEHU specifies the TCP/IP port number

([DPSOH��-port 8080

This switch overrides the value assigned towatt.server.port.


6WDUWLQJ�WKH�6HUYHU�IURP�WKH�&RPPDQG�/LQH


6ZLWFK 'HVFULSWLRQ

-home�GLUHFWRU\1DPH Specifies the server’s home directory.

GLUHFWRU\1DPH specifies the complete path for thehome directory.

([DPSOH��-home D:\wmtest\server

This switch overrides the value assigned towatt.server.home.

Specifies the level of detail you want the server tomaintain in its server log.

OHYHO is a number from 1 to 10 that indicates thelevel of detail you want to record in the log.

6SHFLI\� 7R�UHFRUG�

1 Critical messages only

2 Error and critical messages

3 Warning, error, and critical messages

4 Debug, warning, error, and criticalmessages

5-10 Informational, debug, warning, error,and critical messages

The server records more levels ofinformational messages the higher youset the number.

-debug�OHYHO

This switch overrides the value assigned towatt.debug.level.

-log�GHVWLQDWLRQ Specifies where you want the server to write its loginformation. Specify one of the following forGHVWLQDWLRQ:

2SWLRQ 'HVFULSWLRQ

ILOHQDPH Specify the name of the file where youwant the server to write loginformation.


:KDW�+DSSHQV�:KHQ�<RX�6WDUW�WKH�6HUYHU"


6ZLWFK 'HVFULSWLRQ

none Display log information on thecomputer screen. When you use thisoption, the server records a timestampin the long file, but does not recordany other log information in the logfile.

This switch overrides the value assigned towatt.debug.logfile.

� :KDW�+DSSHQV�:KHQ�<RX�6WDUW�WKH�6HUYHU"When you start the SAP Business Connector Server, it performs a series of initializationsteps to make itself ready for client requests. The server:

1. Establishes the operating environment by using the configuration parameters locatedin the configuration file (VDSEF/config/server.cnf).

2. Initializes processes that perform internal management.

3. Loads information about all the enabled packages and their services that reside in theVDSEF/packages directory. If a package depends on other packages, the server loadsthe prerequisite packages first. The server does not load disabled packages.

4. Executes the startup services for each loaded package.

5. Initializes the guaranteed delivery engine. The server checks the job store for pendingguaranteed delivery transactions. It retries the pending transactions as the guaranteeddelivery configuration settings specify. For more information, refer to &RQILJXULQJ*XDUDQWHHG�'HOLYHU\ on page 14-1.

6. Schedules internal system tasks, such as log rotation.

�+RZ�WR�7HOO�LI�WKH�6HUYHU�LV�5XQQLQJ�&RUUHFWO\

To determine whether your server is running, start your browser and point it to the SAPBusiness Connector Server. (See 6WDUWLQJ�WKH�6HUYHU�$GPLQLVWUDWRU on page 5-2 if youneed instructions for this step.)

If the server is running, you will be prompted for a name and password.

If the server is not running, your browser will issue an error message similar to thefollowing:

"Cannot open the Internet site http://localhost:5555.""A connection with the server could not be established."


9LHZLQJ�$FWLYH�6HVVLRQV


� 6KXWWLQJ�'RZQ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU

Shutdown the server to stop the SAP Business Connector Server and all active sessions.

�7R�VKXW�GRZQ�WKH�VHUYHU

1. Open the Server Administrator if it is not already open.

2. Select 6KXWGRZQ�on the navigation panel.

3. Select whether you want the server to wait before shutting down or to shutdownimmediately.

• :DLW�IRU�DFWLYH��QRQ�DGPLQLVWUDWRU�VHVVLRQV�WR�FRPSOHWH� Specify the number of minutesyou want the SAP Business Connector Server to wait before shutting down. Itthen begins monitoring user activity and automatically shuts down when all non-administrator sessions complete or when the time you specify elapses (whichevercomes first).

• 6KXWGRZQ�LPPHGLDWHO\� The server and all active sessions terminate immediately.

For instructions on how to view the active sessions, refer to�9LHZLQJ�$FWLYH�6HVVLRQVon page 4-5.

4. Choose 6KXWGRZQ.

�9LHZLQJ�$FWLYH�6HVVLRQV

Before you shutdown or restart the server, you can view the sessions that are currentlyactive.

�7R�YLHZ�DFWLYH�VHVVLRQV

1. Select 6WDWLVWLFV�on the navigation panel.

2. Choose tab page 6HUYHU�6WDWV.

3. In section *HQHUDO, select the value in field�6HDWV�/LPLW.

� 5HVWDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHURestart the server when you need to stop and reload the SAP Business Connector Server.You should restart the server when:

• <RX�PDNH�FHUWDLQ�FRQILJXUDWLRQ�FKDQJHV. Some configuration changes require the serverto be restarted before they take affect. This document indicates when you are requiredto restart the server for configuration changes.

• <RX�ZDQW�WR�LQFRUSRUDWH�XSGDWHG�VHUYLFHV�WKDW�FDQQRW�EH�G\QDPLFDOO\�UHORDGHG��This typicallyoccurs for non-Java services.


6HUYHU�5HFRYHU\


�7R�UHVWDUW�WKH�VHUYHU

1. Select 6KXWGRZQ�from the navigation panel.

2. Select whether you want the server to wait before restarting the server or if you wantto restart immediately.

• :DLW�IRU�DFWLYH��QRQ�DGPLQLVWUDWRU�VHVVLRQV�WR�FRPSOHWH� Specify the number of minutesyou want the SAP Business Connector Server to wait before shutting down andrestarting the server. It then begins monitoring user activity and automaticallyshuts down and restarts when all non-administrator sessions complete or when thetime you specify elapses (whichever comes first).

• 5HVWDUW��LPPHGLDWHO\� The server and all active sessions terminate immediately.Then, the server restarts.

For instructions on how to view the active sessions, refer to to�9LHZLQJ�$FWLYH6HVVLRQV on page 4-5.

3. Choose 5HVWDUW.

� 6HUYHU�5HFRYHU\If a hardware or software problem causes the SAP Business Connector Server to fail,restart the server using the normal start-up procedure. The server will automaticallyperform clean-up and initialization processes to reset the operating environment.

− As part of the recovery process, the server automatically:

− Reloads the cache environment to its pre-failure state.

Restores the transaction manager’s guaranteed delivery queues. See &RQILJXULQJ*XDUDQWHHG�'HOLYHU\ on page 14-1 for additional information about guaranteed deliveryrecovery options.

�6LWH�6SHFLILF�6HUYLFHV

Although the server itself does not require you to take any special steps after a serverfailure, services that your site has created might have their own unique recoveryrequirements. You will need to consult with your developers for information about thesekinds of requirements.

�5HFRYHU\�DQG�WKH�/RJ�)LOH

If the SAP Business Connector Server fails before midnight and is not restarted until aftermidnight, the daily log file will not be closed as it should. Instead, the server will appendthe new day’s information to the previous day’s log file, and the file will end upcontaining two day’s worth of information.

If you want to prevent this from happening, you must manually close the previous day’slogs before you restart the server. To close the log file, rename or move all the .log filesusing the naming conventions described in :RUNLQJ�ZLWK�/RJ�)LOHV on page 6-12.

6$3�$* 8VLQJ�WKH�6HUYHU�$GPLQLVWUDWRU


&KDSWHU��8VLQJ�WKH�6HUYHU�$GPLQLVWUDWRU

What is the Server Administrator?............................................ 5-2

Starting the Server Administrator ............................................. 5-2

Basic Operation........................................................................ 5-3

Logging Out of the Server Administrator .................................. 5-4

The Configuration File .............................................................. 5-4

8VLQJ�WKH�6HUYHU�$GPLQLVWUDWRU 6$3�$*

:KDW�LV�WKH�6HUYHU�$GPLQLVWUDWRU"


� :KDW�LV�WKH�6HUYHU�$GPLQLVWUDWRU"

The Server Administrator is an HTML-based utility you use to administer the SAPBusiness Connector Server. It allows you to monitor server activity, manage useraccounts, make performance adjustments, and set operating parameters.

You can run the Server Administrator from any browser-equipped workstation on yournetwork. (The Server Administrator is a browser-based application that uses SAP BCservices to accomplish its work.)

� 6WDUWLQJ�WKH�6HUYHU�$GPLQLVWUDWRU

To use the Server Administrator, simply open your browser and point it to the port on thehost machine where the SAP Business Connector Server is running.

The SAP Business Connector Server must be running in order to use this utility. If theserver is not running, your browser will issue an error similar to the following:

"Cannot open the Internet site http://localhost:5555.""A connection with the server could not be established."

�7R�VWDUW�WKH�6HUYHU�$GPLQLVWUDWRU

1. Start your browser.

2. Point your browser to the host and port where the SAP Business Connector Server isrunning.

([DPSOH

If the server were running on the default port on the same machine where you arerunning the Server Administrator, you would type:

http://localhost:5555

If the server were running on port 4040 on a machine called QUICKSILVER, youwould type:

http://QUICKSILVER:4040

3. Log on to the server with a user name and password that has administrator privileges.

If you just installed the SAP Business Connector Server, you can use the followingdefault values:

User Name: Administrator

Password: manage

6$3�$* 8VLQJ�WKH�6HUYHU�$GPLQLVWUDWRU

*HWWLQJ�+HOS


&DXWLRQ

Use the H[DFW�FRPELQDWLRQ of upper and lower-case characters shown above—usernames and passwords are case sensitive

� %DVLF�2SHUDWLRQ

When you start the Server Administrator, your browser displays the 3HUIRUPDQFH6WDWLVWLFV screen.

7KH�6HUYHU�$GPLQLVWUDWRU�6FUHHQ

Navigation Panel Tab strip

Tab page

NavigationButton

The navigation panel on the left side of the screen displays the names of administrativetasks. To start a task, select a task name in the navigation panel. The server displays ascreen that corresponds to the task you select.

Most screens display a list of tabs along the bottom. Each tab corresponds to a separatescreen. To work with a specific screen, select the tab.

�*HWWLQJ�+HOS

You can obtain information about the Server Administrator by choosing the +HOS�tabslocated on each screen. The help system displays a description of the parameters for the

8VLQJ�WKH�6HUYHU�$GPLQLVWUDWRU 6$3�$*

/RJJLQJ�2XW�RI�WKH�6HUYHU�$GPLQLVWUDWRU


screen. From this window, choose &RQWHQWV�to view the help system’s table of contentsfrom which you can search for a specific screen description.

� /RJJLQJ�2XW�RI�WKH�6HUYHU�$GPLQLVWUDWRULog out of the Server Administrator when you no longer need to continue your currentsession. When you log out, the server cleans up your session.

If you are going to be away from your PC, you might also want to log out of the ServerAdministrator to prevent someone from accessing the Server Administrator with youruser name from your PC.

�7R�ORJ�RXW�RI�WKH�6HUYHU�$GPLQLVWUDWRU

1. Choose /RJRXW from the navigation panel.

The SAP Business Connector Server displays a dialog box to ensure you want to logout.

2. Choose 2. to log out of the Server Administrator.

To resume use of the Server Administrator, select any task in the navigation panel.

� 7KH�&RQILJXUDWLRQ�)LOH

Configuration settings for the SAP Business Connector Server are stored in the serverconfiguration file (server.cnf). This file resides in the VDSEF\server\config directoryand contains parameters that determine how the server operates.

You can set most parameters in the server.cnf file with the Server Administrator.However, you can only set certain parameters by editing the server.cnf file directly.When this is the case, you will be instructed to open the server.cnf file with a texteditor.

For a list of parameters in the server.cnf file and their default values, refer to 6HUYHU&RQILJXUDWLRQ�3DUDPHWHUV on page B-1.

6$3�$* &RQILJXULQJ�WKH�6HUYHU


&KDSWHU��&RQILJXULQJ�WKH�6HUYHU

Viewing and Changing Licensing Information .......................... 6-2

Configuring Listening Ports ...................................................... 6-4

Configuring Web Automation Settings ..................................... 6-7

Specifying a Proxy Server ...................................................... 6-10

Setting the Timeout Limit........................................................ 6-11

Working with Log Files ........................................................... 6-12

Specifying Error Message Recipients .................................... 6-16

&RQILJXULQJ�WKH�6HUYHU 6$3�$*

9LHZLQJ�DQG�&KDQJLQJ�/LFHQVLQJ�,QIRUPDWLRQ


� 9LHZLQJ�DQG�&KDQJLQJ�/LFHQVLQJ�,QIRUPDWLRQ

When you purchase a SAP Business Connector Server, your organization is granted alicense to use it with a specified number of concurrent users (seats). The license expiresafter a time period specified by your particular purchase agreement.

�7KH�/LFHQVH�.H\

When you install the server, the setup program asks you to enter your “key,” which is aspecial code associated with your license. After you enter this code, it is assigned to thewatt.server.key parameter in the server.cnf file in the VDSEF/server/configdirectory. If the watt.server.key parameter is inadvertently changed or deleted or ifyour license expires, your server reverts to demo mode. In this mode, the serverautomatically shuts down 30 minutes after it is started.

�9LHZLQJ�RU�&KDQJLQJ�WKH�/LFHQVH�.H\

To view or change the license key for your SAP Business Connector Server, choose6HWWLQJV from the navigation panel.


/LFHQVHG�6HDWV


�7R�YLHZ�WKH�/LFHQVH�.H\

1. Select 6HWWLQJV on the navigation panel.

2. Choose tab page *HQHUDO�6HWWLQJV.

The server displays the license key in field�/LFHQVH�.H\.

�7R�FKDQJH�WKH�/LFHQVH�.H\


2. Choose tab page *HQHUDO�6HWWLQJV�

3. Choose (GLW�WKHVH�VHWWLQJV.

4. In field /LFHQVH�.H\ of the screen, type the new license key.

5. Choose 6XEPLW.

1RWH

The SAP Business Connector Server updates the expiration date automatically afteryou choose 6XEPLW.

�5HQHZDO�5HPLQGHUV

Approximately 30 days before your license expires, the SAP Business Connector Serversends an e-mail to the administrative-message recipient, reminding him or her to renewthe license. In addition, the server displays the following message at the top of the 6HUYHU6HWWLQJV screen of the Server Administrator:

License key expires in about GD\V days … contact SAP AG for a newkey.

�5HQHZLQJ�D�.H\

If you need to obtain a new key or renew your license, contact your SAP AG salesrepresentative.

�/LFHQVHG�6HDWV

Your license allows a specified number of users to have sessions in the SAP BusinessConnector Server concurrently. The SAP Business Connector Server creates a sessionwhen a developer connects to the server from the SAP Business Connector Developer ora SAP BC client connects to the server to execute services. If a user attempts to access the


&RQILJXULQJ�/LVWHQLQJ�3RUWV


server while the maximum number of sessions are in use, the server rejects the requestand returns the following error to the user:

Server has reached client limit.

You can view the current number of active seats and the seat limit using the Statisticspage in the Server Administrator. This value is permanently associated with your licensekey and can only be changed by obtaining a new license.

�7R�YLHZ�WKH�FXUUHQW�QXPEHU�RI�DFWLYH�VHDWV�DQG�WKH�VHDW�OLPLW

1. Select 6WDWLVWLFV on the navigation panel.

2. Select tab page 6HUYHU�6WDWV.

The server displays the current number of active seats and the seat limit in field6HDWV�/LPLWV. The first number represents the number of active seats in use. Thesecond number represents the maximum number of sessions your license allows.

For detailed information about the active sessions, select the value in field6HDWV�/LPLWV.

� &RQILJXULQJ�/LVWHQLQJ�3RUWV

The SAP Business Connector Server listens for requests on ports that you specify. Eachport is associated with a specific type of listener—HTTP, HTTPS, or FTP. Typically,most client requests use an HTTP listener, or for secure requests, an HTTPS listener. Usean FTP for an alternate way to request services and a convenient way for moving files toand from the server. The server has a primary listening port and one or more additionallistening ports.

�&RQILJXULQJ�WKH�3ULPDU\�/LVWHQLQJ�3RUW

The primary listening port is the first port the server opens during server startup. If theserver is unable to open the primary listening port, server startup fails. The server requiresthat the primary listening port remain enabled while the server is running, so at least oneport is always available for incoming connections. By default, the server designates port5555 with an HTTP listener as the primary listening port.

You can change the port number and/or the listener for the primary listening port. Forexample, if you want only secure connections to the server, change the listener for theprimary listening port to HTTPS. The primary listening port must use either an HTTP orHTTPS listener.

�7R�FRQILJXUH�WKH�SULPDU\�OLVWHQLQJ�SRUW


2. Select tab page /LVWHQHUV.

3. Set the &KDQJH�3ULPDU\�3RUW parameters as follows:


$GGLQJ�/LVWHQLQJ�3RUWV


)RU�WKLV�SDUDPHWHU 6SHFLIL\��

3URWRFRO The type of listener you want to associate with theprimary port:

HTTP Accepts non-secure requests that usethe Hypertext Transfer Protocol.

HTTPS Accepts secure requests that use theHypertext Transfer Protocol withSecure Sockets Layer (SSL)

1HZ�3RUW�1XPEHU The port number you want to use for the primarylistening port

4. Choose &KDQJH.

�$GGLQJ�/LVWHQLQJ�3RUWV

In addition to the primary port, you can configure one or more additional listening ports.You can associate an HTTP, HTTPS, or FTP listener with the additional ports. You mightadd additional listeners:

g If you have applications that require a specific port number

g If you want to support multiple types of listening protocols

g If you want to open several listening ports for the same protocol

g If you want to establish a separate port that only administrator can use. Forinformation about setting up an administrator’s port, refer to &RQWUROOLQJ�$FFHVV�WR6$3�%&�6HUYLFHV�%\�/LVWHQLQJ�3RUW on page 8-17.

By default, the server designates an additional listening port, port 8021, which isassociated with an FTP listener.

�7R�DGG�DQ�DGGLWLRQDO�OLVWHQLQJ�SRUW



3. Set the $GG�/LVWHQHU parameters as follows:


&RQILJXULQJ�/LVWHQLQJ�3RUWV



7\SH The type of listener you want to associate with theprimary port:

HTTP Accepts non-secure requests that usethe Hypertext Transfer Protocol.

HTTPS Accepts secure requests that use theHypertext Transfer Protocol withSecure Sockets Layer (SSL)

FTP Accepts secure requests that use theFile Transfer Protocol (FTP)

3RUW�1XPEHU The port number you want SAP BusinessConnector Server to listen for incoming requests.

4. Choose $GG. The server displays a dialog box that prompts you to verify your action.Choose 2. to verify you want to add the new listening port to your configuration.

5. Locate the new listener in the /LVWHQLQJ�3RUWV list at the top of the screen, and ensurethat the icon in the (QDEOHG" column is green (enabled). If it is not, select the iconto enable the listener.

�'HOHWLQJ�D�/LVWHQLQJ�3RUW

If you no longer need a listening port, you can delete it.

1RWH

You cannot delete the primary listening port.

�7R�GHOHWH�D�OLVWHQLQJ�SRUW



3. Locate the listener in the /LVWHQLQJ�3RUWV list, and select the icon in the 'HOHWHcolumn to delete the listener. The server displays a dialog box that prompts you toverify your action.

4. Choose 2. to verify you want to delete the listening port.


(QDEOLQJ�'LVDEOLQJ�D�/LVWHQHU


�(QDEOLQJ�'LVDEOLQJ�D�/LVWHQHU

If you want to temporarily prevent the server from accepting requests on one of its ports,you can disable that port. This action blocks incoming requests from reaching the server.When a listening port is disabled, clients receive an error message when they issuerequests to it. At a later time, you can enable the port. If you shut down and restart theserver, the server enables the port at server startup.

1RWH

You cannot disable the primary listening port.

�7R�GLVDEOH�D�OLVWHQLQJ�SRUW



3. Locate the listener in the /LVWHQLQJ�3RUWV list, and select the green icon in the(QDEOHG" column to disable the listener. The server displays a dialog box thatprompts you to verify your action.

4. Choose 2. to verify you want to disable the listening port.

The server replaces the green icon with the red icon to indicate that the listeningport is now disabled.

�7R�HQDEOH�D�OLVWHQLQJ�SRUW



3. Locate the listener in the /LVWHQLQJ�3RUWV list, and select the red icon in the(QDEOHG" column to disable the listener

4. .The server displays a dialog box that prompts you to verify your action. Choose 2.to verify you want to disable the listening port.

The server replaces the red icon with the green icon to indicate that the listeningport is now enabled.

� &RQILJXULQJ�:HE�$XWRPDWLRQ�6HWWLQJV

When the server executes services that perform Web automation, it issues HTTP requeststo retrieve Web documents. In this capacity, it functions much like a Web browser—i.e.,it requests HTML and XML documents from the Internet or your intranet.


&RQILJXULQJ�:HE�$XWRPDWLRQ�6HWWLQJV


�2YHUYLHZ�RI�WKH�:HE�$XWRPDWLRQ�6HWWLQJV

The Web Automation parameters control how the server presents and processes outboundHTTP and HTTPS requests (i.e., requests that the SAP Business Connector Server issueson behalf of a client). The parameters control behavior such as how long the server waitsfor a response, how many times it retries a failed request, and so forth.

1RWH

A developer can override some of the server’s Web automation defaults at run time.The following descriptions note when this is allowed.

8VHU�$JHQWThe 8VHU�$JHQW parameter specifies the value the server uses in the HTTP User Agentrequest header that it sends when requesting a Web document. The User Agent headertells a Web server what type of browser is making the request. In the case of the SAPBusiness Connector Server, the User Agent header indicates the type of browser that theSAP Business Connector Server appears to be to the Web server. Some Web serversexamine this header to determine a client’s capabilities so they can tailor their responsesaccordingly.

When you install the SAP Business Connector Server, the 8VHU�$JHQW parameter is set toMozilla/4.0 [en] (winNT; I). You can change this value as you need; however, thevalue you set should satisfy the majority of services that your server executes.

Be sure your developers know the 8VHU�$JHQW value your server uses. If their applicationsrequire a different User Agent, they can override the server’s default at run time byincluding an HTTP User Agent header with their request.

0D[�5HGLUHFWVThe 0D[�5HGLUHFWV�parameter specifies the number of times that the SAP BusinessConnector Server allows a request to be redirected (i.e., automatically sent to anotherURL) by the target server. If a request exceeds the specified number of redirections, theSAP Business Connector Server immediately returns an I/O exception to the client.

When you install the SAP Business Connector Server, 0D[�5HGLUHFWV is set to five. Youwill need to increase this value if the targets that you access typically redirect theirrequests more than this. (This may happen if the target operates in a clusteredenvironment.)

7LPHRXWThe 7LPHRXW parameter specifies the length of time the server waits for a response from atarget server. If the SAP Business Connector Server does not receive a response in theallotted time, it retries the request up to the number of times specified by the 5HWULHVparameter. When it exceeds the number of allowed retries, it returns an exception.

When you install the SAP Business Connector Server, the 7LPHRXW parameter is set tothree minutes. For most sites this is a reasonable; however, you may need to adjust this


6SHFLI\LQJ�:HE�$XWRPDWLRQ�6HWWLQJV


value if you work with targets that have longer response times than this (e.g., largecommercial Web sites or databases during peak periods).

5HWULHVThe 5HWULHV parameter specifies the number of times the server reissues a request that hastimed out (i.e., one to which it did not receive a response within the time period specifiedby the 7LPHRXW parameter).

When you install the SAP Business Connector Server, 5HWULHV is set to zero. This meansthat the server automatically returns an exception if it does not get a response within theallotted time. Set 5HWULHV to a value greater than zero if you want the server to retry(reissue) timed-out requests. The server will retry the request the number of times youspecify.

Be sure your developers know what 5HWULHV value your server uses. If they need to use adifferent value, they can explicitly assign a 5HWULHV value to their service.

�6SHFLI\LQJ�:HE�$XWRPDWLRQ�6HWWLQJV

Use the following procedure to set the Web Automation Defaults.

�7R�VHW�WKH�:HE�$XWRPDWLRQ�'HIDXOWV


2. Select tab page *HQHUDO�6HWWLQJV.

3. Choose (GLW�WKHVH�6HWWLQJV.

4. Set the Web Automation Defaults as follows:


8VHU�$JHQW The string that you want the server to supply in the HTTPUser Agent header if the client does not specify a value.Type the string H[DFWO\ as you want it to appear in theHTTP header, including spaces, symbols, andpunctuation.

0D[�5HGLUHFWV An integer that indicates the number of times to allow arequest to be redirected before the server returns an I/Oexception to the client

7LPHRXW An integer that indicates the number of seconds the serverwaits for a response from the target server before retryingthe service or returning a timeout error to the client.

7\SH An integer that indicates the number of times the serverretries a service that has timed out before returning anexception to the client.

5. Choose 6XEPLW.


6SHFLI\LQJ�D�3UR[\�6HUYHU


� 6SHFLI\LQJ�D�3UR[\�6HUYHUWhen the SAP Business Connector Server executes a Load Document service, it issuesan HTTP or HTTPS request to the specified target server. If you want to route theserequests through a proxy server (for example, if your SAP Business Connector Server sitsbehind a firewall), you must define the address of the proxy server using the ServerAdministrator.

The SAP Business Connector Server allows you to define two proxies—one to use foroutbound HTTP requests, and one to use for outbound HTTPS requests.

�7R�VSHFLI\�D�3UR[\�6HUYHU




4. Set the 3UR[\��+773� and 3UR[\��+7736� parameters as follows. (If you use a proxyserver for only one request type, complete the parameters for that type, and leave theparameters for the other type empty.)


3UR[\�+RVW The name of the proxy server

3UR[\�3RUW The port on which the proxy server listens forHTTP and/or HTTPS requests.

3UR[\�8VHU The user name the SAP Business ConnectorServer must use when accessing this proxy server(if one is required).

3UR[\�3DVVZRUG The password the SAP Business Connector Servermust use to access this proxy server (if one isrequired).

5. Choose 6XEPLW.

�%\SDVVLQJ�D�3UR[\�6HUYHU

If you are using a proxy server for outbound HTTP and/or HTTPS requests, you canoptionally route selected requests directly to their targets, bypassing the proxy.

To do this, you use the Server Administrator to define the list of domains to which youwant the SAP Business Connector Server to issue requests directly.


6SHFLI\LQJ�:HE�$XWRPDWLRQ�6HWWLQJV


�7R�E\SDVV�D�SUR[\�VHUYHU




4. In the %\SDVV�/LVW, type the domain names of the servers to which you want the SAPBusiness Connector Server to issue requests directly. Separate domain names withcommas.

([DPSOH

If you wanted to bypass requests made to localhost, www.yahoo.com, andhome.microsoft.com, you would type:

localhost,yahoo,microsoft

5. Choose 6XEPLW.

� 6HWWLQJ�WKH�7LPHRXW�/LPLW

When a remote client connects to the SAP Business Connector Server, the server starts asession for that client. That session remains active until the client application specificallyissues a disconnect instruction to the server (which forces an immediate termination) orthe session “times-out” due to inactivity, whichever comes first.

If a session is idle (inactive) for a long period of time, it usually means that the client isno longer active or the connection between client and the server has been lost. The serverconstantly monitors for inactive sessions, and terminates sessions that are idle for morethan the allowed period of time. (If the server did not take steps to clear out such sessions,they would remain active indefinitely, wasting valuable server resources.)

You use the 6HVVLRQ�7LPHRXW�parameter to specify the length of time you will allow anidle session to remain active (in other words, how long you want the server to wait beforeterminating an idle session). To set the Session Timeout parameter appropriately, youmust be familiar with the clients that use your server.

If your clients are all Java programs, you can usually reduce the timeout value to six orseven minutes. You may need to experiment with this setting to find the appropriate valuefor your site. By default, the server uses a timeout limit of 10 minutes. This is anappropriate value for most sites. However, you may have to increase this value if yourclients normally have lengthy delays (greater than 10 minutes) between successiverequests.


:RUNLQJ�ZLWK�/RJ�)LOHV


�7R�VHW�WKH�7LPHRXW�/LPLW




4. In field�6HVVLRQ�7LPHRXW, type the number of minutes you want the server to waitbefore terminating an idle session.

5. Choose 6XEPLW.

� :RUNLQJ�ZLWK�/RJ�)LOHV

The SAP Business Connector Server uses log files to maintain an audit-trail of services itexecutes and errors that occur. These files contain a historical trace you can use todiagnose application failures, analyze server performance, and trace server-related events.

�:KDW�.LQG�RI�/RJ�)LOHV�'RHV�WKH�6HUYHU�0DLQWDLQ"

The server maintains the following log files. Each file contains information for aparticular purpose or process.

/RJ )LOH�1DPH )LOH�1DPH

$XGLW audit.log Maintains an audit trail for all services that theserver executes. For each service, the server addstwo records that contain information about theservice. It adds one when it begins execution; thisrecord includes the timestamp of when executionbegan. It adds the second record when the serviceterminates; this record includes the timestamp ofwhen the service terminated. You can use this logto determine all services requested from the serverand which client requested each service.

(UURU error.log Maintains information about all errors andexceptions that have occurred in the SAP BCsystem. You can use this log for debuggingproblems with services.

6HUYHU server.log Maintains information about the version of theSAP Business Connector Server that is runningthe operations that the server has performed. Youcan use this information for general debuggingpurposes.


:KHUH�DUH�WKH�/RJ�)LOHV"


/RJ )LOH�1DPH )LOH�1DPH

6HVVLRQ session.log Maintains information about all sessions in theSAP BC system. The SAP Business ConnectorServer creates a session when a developerconnects to the server from the SAP BCDeveloper or a SAP BC client connects to theserver to execute services. Each record in theSession Log includes a timestamp indicating whena user established a connection with the SAPBusiness Connector Server.

6WDWLVWLFV stats.log Maintains statistical information about theconsumption of system resources. You can usethis information to determine the cause ofperformance problems on your server.

7UDQVDFWLRQ txin.log

txout.log

Maintains information about inbound andoutbound guaranteed delivery transactions. Theserver writes a record for each critical operation itperforms for a guaranteed delivery transaction.Use these logs in conjunction with the appropriatejob store (inbound or outbound) to determinemore information about a guaranteed deliverytransaction.

For a sample of the contents of each log, refer to 6HUYHU�/RJ�)LOHV on page C-1.

�:KHUH�DUH�WKH�/RJ�)LOHV"

The SAP Business Connector Server maintains the log files in VDSEF\server\log.

�+RZ�0XFK�,QIRUPDWLRQ�LV�5HFRUGHG"

Most log files contain brief, standard descriptions of key events. The server log(server.log) is an exception. Its contents can be configured.

For the server.log file, you can specify the type of events you want the server to recordand the amount of detail you want to see. This flexibility is useful for troubleshooting.For example, you might temporarily increase the level of detail written to this log to helpuncover the cause of a server error or performance problem, and return to a lower levelonce the problem is resolved.




�7R�FRQILJXUH�WKH�FRQWHQWV�RI�WKH�VHUYHU�ORJ�ILOH


2. Select tab page /RJJLQJ.


4. In field�/RJ�/HYHO, type a value from 1 to 10 to specify the amount of information youwant the server to record for the selected facilities:

6SHFLIL\ 7R�UHFRUG

� Critical messages only

� Error and critical messages

� Warning, error, and critical messages

� Debug, warning, error, and critical messages

�� Informational, debug, warning, error, and critical messages

1RWH

Recording more information consumes more system resources.

5. For )DFLOLWLHV, select the type of information you want the server to include in the log.

6. Choose 6XEPLW.

�+RZ�/RQJ�'RHV�WKH�6HUYHU�0DLQWDLQ�LWV�/RJV"

The server regularly closes log files and opens new ones. This process is referred to as"rotating the log files." You can configure:

g :KHQ�WKH�ILUVW�URWDWLRQ�RI�WKH�ORJ�ILOHV�RFFXUV��You specify how long the server isto collect log information from the time the server is started to the time it rotates thelog files for the first time.

g +RZ�ORQJ�VXEVHTXHQW�URWDWLRQ�LQWHUYDOV�DUH� You specify an interval of time thatindicates how often (after the first log file rotation) the server continues to rotate thelog files.

g +RZ�WKH�VHUYHU�VWRUHV�WKH�FORVHG�ORJ�ILOHV� You specify whether the server is tomaintain all the log files in a single directory (rename) or create a new directory eachtime it rotates the log files (move).


+RZ�/RQJ�'RHV�WKH�6HUYHU�0DLQWDLQ�LWV�/RJV"


To have the server store all log files in a single directory, use the UHQDPH setting. Thissetting indicates that the server is to rename the log files to include the date and time thelog files were closed.

5HQDPHG�ORJ�ILOHV

To have the server create a new directory for each set of closed log files, use the PRYHsetting. This setting indicates that the server is to create a new directory and move theclosed log files to the new directory. The server gives the new directory a name thatidentifies when it closed the log file.

0RYHG�ORJ�ILOHV

By default, the server maintains log files that hold information for a single day. The firstrotation occurs at 00:00 (midnight). The rotation interval is 24 hours, so it continues toclose the log files every day at 00:00 (midnight). When the server closes the previousday’s log files, it stores them in a single directory.

�&RQILJXULQJ�/RJ�)LOH�5RWDWLRQ

You use the following procedure to configure how the server rotates the log files.

�7R�FRQILJXUH�ORJ�ILOH�URWDWLRQ

1. Open the server.cnf file with a text editor. (This file resides in the VDSEF\serverdirectory.)

2. To set when the rotation will occur, locate the following two parameters. If theseparameters do not exist, add them. Set them as follows:




6HW�WKLV�SDUDPHWHU 7R��

watt.server.logRotateFirstInterval The number of milliseconds after theserver is started when the server rotatesthe log files for the first time.

watt.server.logRotateInterval The number of milliseconds after the firstrotation when the server will continue torotate the log files.

3. To set how the rotation will occur, locate the watt.server.logRotate parameter. Ifthis parameter does not exist, add it. Set the watt.server.logRotate parameter toone of the following:

6HW�WKLV�YDOXH 7R��

rename Rename the log files to include the date and timethe server closes the log files and keep them in thesame directory.

move Create a new directory with a name that representswhen the server closes the log files and move thelog files to the new directory.

4. Save the server.cnf file.

5. Restart the server to put your changes into effect.

�6SHFLI\LQJ�(UURU�0HVVDJH�5HFLSLHQWV

When critical errors occur, the server automatically issues a message to a specified e-mailaddress. To ensure that this information reaches the appropriate person, you must specifywhere you want the server to deliver these messages.

The server issues the following types of error messages. You can route each type to adifferent recipient.

g Internal Error Messages. The server issues this type of error when a critical problemoccurs with the server program or a service. For example, when the server encountersa null pointer exception or other exception it cannot handle. Most sites route this typeof message to the server administrator or an appropriate alternate.

g Service Error Messages. The server issues this type of error when an output bindingfails—i.e. the structure of a requested document does not match the expectations ofthe SAP BC service requesting it. In these cases, your developers may need to updatethe service to match the document’s new structure. Most sites route this type ofmessage to someone in their development organization.


6SHFLI\LQJ�(UURU�0HVVDJH�5HFLSLHQWV


�7R�VSHFLI\�WKH�HUURU�PHVVDJH�UHFLSLHQWV



3. Select (GLW�WKHVH�6HWWLQJV.

4. Set the 0DLO parameters as follows:

)RU�WKLV�SDUDPHWHU�� 6SHFLI\��

6073�6HUYHU Domain name (e.g., purple.sap.com) or IP address(e.g. 132.906.19.22) of the SMTP server that youwant the SAP Business Connector Server to use.

,QWHUQDO�(�PDLO E-mail address of the user you want notified whenan internal server error occurs. Typically, this isthe e-mail address of the administrator for theSAP Business Connector Server.

6HUYLFH�(�PDLO The e-mail address of the person the server willnotify when an output binding fails. Typically,this is the e-mail address for someone that isfamiliar with the services on your server, such as alead developer.

7UDQVDFWLRQ�(�PDLO The e-mail address of the person the server willnotify when guaranteed delivery fails.

5. Choose 6XEPLW.

6$3�$* 0DQDJLQJ�8VHUV�DQG�*URXSV


&KDSWHU��0DQDJLQJ�8VHUV�DQG�*URXSV

Users and Groups .................................................................... 7-2

Defining a User Account........................................................... 7-3

Defining Groups ....................................................................... 7-6

0DQDJLQJ�8VHUV�DQG�*URXSV 6$3�$*

8VHUV�DQG�*URXSV


� 8VHUV�DQG�*URXSV

Use the Server Administrator to define user and group information to the server. Thedefinition for a user contains the user name, password, and group membership. Thedefinition for a group contains the group name and a list of users in the group. The serverstores and maintains the information.

Alternatively, you can set up the SAP Business Connector Server to access theinformation from an external directory if your site uses one of the following externaldirectories for user and group information:

g Lightweight Directory Access Protocol (LDAP)

g Network Information Service (NIS)

This chapter describes only how the SAP Business Connector Server works when userand group information is defined internally. For information about using an externaldirectory with the SAP Business Connector Server, refer to 8VLQJ�DQ�([WHUQDO�'LUHFWRU\�/'$3�RU�1,6� on page 9-1.

�3XUSRVH�RI�8VHUV�DQG�*URXSV

The server uses user and group information to authenticate clients and determine theserver resources that a client is allowed to access.

If the server is using basic authentication (user names and passwords) to authenticate aclient, it uses the user names and passwords defined in user accounts to validate thecredentials a client supplies.

After a client is authenticated (whether through basic authentication or client certificates),the server uses the group membership to determine if a client is authorized for therequested action, such as, using the Server Administrator or invoking a service.

Access to the server’s resources is controlled at the group level. By setting up users andgroups, you can control who can:

g &RQILJXUH�DQG�PDQDJH�WKH�VHUYHU��Only users that are members of the Administratorsgroup (administrator privilege) can access the Server Administrator.

g &UHDWH��PRGLI\��DQG�GHOHWH�VHUYLFHV�WKDW�UHVLGH�RQ�WKH�VHUYHU� Only users that are members ofthe Developers group (developer privileges) can connect to the server from the SAPBusiness Connector Developer.

g $FFHVV�VHUYLFHV�DQG�ILOHV�WKDW�UHVLGH�RQ�WKH�VHUYHU��Access to services and files is protectedat the group level.


3XUSRVH�RI�8VHUV�DQG�*URXSV


� 'HILQLQJ�D�8VHU�$FFRXQW

When you create a user account on the SAP Business Connector Server, you specify auser name, password, and group membership.

g 8VHU�QDPH� A user name is a unique name that identifies a client. You can specify auser name that represents an actual person (e.g., "JDSmith" for John D. Smith), oryou can specify a user name to represent applications, job functions, or organizations.For example, you might set up generically-named user names such as"MktgPurchAgent," "MktgTimeKeeper," and so forth, to represent job functions.

g 3DVVZRUG� A password is an arbitrary string of characters that you associate with a username. The server uses the password when authenticating a client who has submitted avalid user name. For more information about authentication, refer to $XWKHQWLFDWLQJ&OLHQWV on page 8-20.

A password is meant to be a secret code shared only by the server, the serveradministrator, and the owner of the user account. Its purpose is to give the server addedassurance that a request is coming from a legitimate user. Only administrators can assigna password to a user name and change a password for an existing account.

Passwords are optional; however, for secure operation, we recommended that you specifya password for all user names. If a user account does not have a password, the serverallows access to any user who submits that user name, regardless of what passwordaccompanies it.

g Group membership. The group membership identifies the groups to which a userbelongs. Access to the server’s resources is controlled at the group level:

� Only users that are members of the Administrators group can configure andmanage the server using the Server Administrator. For more information aboutcontrolling access to the Server Administrator, refer to &RQWUROOLQJ�:KR�&DQ&RQILJXUH�DQG�0DQDJH�WKH�6HUYHU on page 8-2.

� Only users that are members of the Developers group can connect to the serverfrom the SAP Business Connector Developer to create, modify, and deleteservices. For information, refer to &RQWUROOLQJ�:KR�&DQ�&RQILJXUH�DQG�0DQDJHWKH�6HUYHU on page 8-2.

� The server protects access to services and files using Access Control Lists(ACLs). You set up ACLs that identify groups that are allowed or not allowed toaccess a resource. For more information about protecting services and files, see&RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�DQG�)LOHV�ZLWK�$&/V on page 8-10.


'HILQLQJ�D�8VHU�$FFRXQW


�3UHGHILQHG�8VHU�$FFRXQWV

The server has the following predefined user accounts:

8VHU *URXSV 'HVFULSWLRQ

$GPLQLVWUDWRU EverybodyAdministratorsReplicators

A user account that has administratorprivileges. You can use the Administratoruser account to access the ServerAdministrator to configure and manage theserver.

'HIDXOW Everybody The server uses the information defined forthe Default user when the client does notsupply a user name and password.

'HYHORSHU EverybodyDevelopers

A user that can connect to the server from theSAP Business Connector Developer tocreate, modify, and delete services that resideon the server.

$GPLQLVWUDWRU EverybodyAdministratorsReplicators

The user account that the server uses duringpackage replication. 'R�QRW�GHOHWH�WKLV�XVHUDFFRXQW. If you do, the server will not be ableto perform any package replication functions.For more information on package replication,refer to &RS\LQJ�3DFNDJHV�IURP�2QH�6HUYHUWR�$QRWKHU on page 10-14.

&DXWLRQ

The server GRHV�QRW assume the Default user information if the client is the SAPBusiness Connector Developer. When a connection is made to the server from theSAP Business Connector Developer, the user PXVW provide a valid user name andpassword or else the server denies access.


$GGLQJ�8VHU�$FFRXQWV


�$GGLQJ�8VHU�$FFRXQWV

Use the following procedure to add a user account for a user.

�7R�DGG�D�XVHU�DFFRXQW�WR�WKH�VHUYHU

1. Select $FFHVV on the navigation panel.

2. Select tab page 8VHUV.

3. Choose $GG to open the 1HZ�8VHU screen.

4. In field�8VHU�1DPH, type a unique user name made up of any combination of letters,numbers, or symbols.

5. In field�3DVVZRUG, type a password made up of any combination of letters, numbers,or symbols.

&DXWLRQ

User names and passwords are case-sensitive. When you create a user account, typethese values exactly as you want the client to enter it.

6. In box�0HPEHU�RI, select (highlight) the groups to which you want the user name tobelong.

1RWH

If you have not created groups yet, you can edit the user information at a later time tochange group membership or you can assign users to a group when you create agroup.

7. Choose 6XEPLW.

�5HPRYLQJ�8VHU�$FFRXQWV

Use the following procedure to delete a user account when it is no longer needed.

�7R�GHOHWH�D�XVHU�DFFRXQW�IURP�WKH�VHUYHU



3. Select the user name for the user account you want to delete from the�&XUUHQW�8VHUVlist.

4. Choose 'HOHWH. The server issues a prompt to verify that you want to delete the useraccount. Choose 2. to remove the user account.


'HILQLQJ�*URXSV


1RWH

When you delete a user, the user is automatically removed from the members list ofall groups to which it was assigned.

�&KDQJLQJ�3DVVZRUGV

Use the following procedure to change the password associated with a user name.

�7R�FKDQJH�D�SDVVZRUG



3. Select the user name for the user whose password you want to change and choose(GLW.

4. In field�3DVVZRUG, type a new password made up of any combination of letters,numbers, or symbols.

&DXWLRQ

Passwords are case-sensitive. Type a password exactly as you want the client to enterit.

5. Choose 6XEPLW to commit this change to the server.

� 'HILQLQJ�*URXSV

A group is a named collection of users that share privileges. The privileges can be:

g Administrator privileges

g Replicator privileges

g Developer privileges

g Privileges to invoke a service

g Privileges to allow the server to serve files

Administrator, replicator, and developer privileges are granted by adding a user to theAdministrators, Replicators, or Developers group, respectively.

Privileges to invoke a service or access files are granted and denied by Access ControlLists (ACLs) that you set up. When an administrator creates ACLs, he or she identifies


3UHGHILQHG�*URXSV


groups that are allowed to access services and files and groups that are denied access toservices and files.

Create groups that identify groups of users that will share the same privileges. When youcreate a group definition, you specify the following a group name and the members of thegroup.

g *URXS�QDPH� A group name is a unique name that identifies the group. You can useany name, for example, a name that defines a department (Marketing) or job function(Programmers).

g 0HPEHUV� List of user names that are members of the group.

�3UHGHILQHG�*URXSV

The server is installed with the following predefined groups.

*URXS�1DPH 0HPEHUV 'HVFULSWLRQ

$GPLQLVWUDWRUV Administrator This group identifies users that haveadministrator privileges. A user must haveadministrator privileges to configure andmanage the server.

'HYHORSHUV Developer This group identifies users that havedeveloper privileges. A user must havedeveloper privileges to connect to the serverfrom the SAP Business ConnectorDeveloper.

(YHU\ERG\ AdministatorDefaultDeveloperReplicator

All users are a member of this group. Everynew user is automatically added to theEverybody group.

5HSOLFDWRUV AdministatorReplicator

This group identifies users that havereplicator privileges. The Replicators groupgives the Replicator user the authority toperform package replication. (The serveralways uses the Replicator user account forpackage replication.) 'R�QRW�GHOHWH�WKLVJURXS� If you do, the server will not be ableto perform any package replication functions.

For more information on package replication,refer to &RS\LQJ�3DFNDJHV�IURP�2QH�6HUYHUWR�$QRWKHU on page 10-14.


'HILQLQJ�*URXSV


�$GGLQJ�*URXSV

Use the following procedure to add groups.

�7R�DGG�D�QHZ�JURXS�WR�WKH�VHUYHU


2. Select tab page *URXSV.

3. Choose $GG to open the 1HZ�*URXS screen.

4. In field�*URXS�1DPH, type a unique group name made up of any combination ofletters, numbers, or symbols.

&DXWLRQ

Group names are case-sensitive.

5. In field�0HPEHUV, select (highlight) the users that you want to include in the groupmembership.

6. Choose 6XEPLW.

�5HPRYLQJ�*URXSV

Use the following procedure to remove groups that you no longer need.

�7R�GHOHWH�D�JURXS�IURP�WKH�VHUYHU

Select $FFHVV on the navigation panel.

Select tab page *URXSV.

Select the group name of the group you want to delete from the groups listed in field&XUUHQW�*URXSV.

Choose 'HOHWH. The server issues a prompt to verify that you want to delete the group.Choose 2. to remove the group.

1RWH

When you delete a group, the server automatically removes the group from:

− The group membership for users that were in the group

− The Allowed Groups or Denied Groups of ACLs that reference the group


9LHZLQJ�RU�&KDQJLQJ�*URXS�0HPEHUVKLS


�9LHZLQJ�RU�&KDQJLQJ�*URXS�0HPEHUVKLS

Use the following procedure to view the members or a group or change the members in agroup.

�7R�YLHZ�RU�FKDQJH�WKH�JURXS�PHPEHUVKLS�IRU�D�JURXS


2. Select tab page *URXSV.

3. Select the group name for the group whose membership you want to view or changeand chosse (GLW.

4. To change the group membership, select (highlight) users that you want to add to themembership and deselect users you no longer want to be members of the group.

− To select additional users without deselecting currently selected users, press theCTRL key while you select the users you want to select.

− To deselect a user, press the CTRL key while you select the currently selectedentry.

5. Choose 6XEPLW.


'HILQLQJ�*URXSV


6$3�$* 0DQDJLQJ�6HUYHU�6HFXULW\


&KDSWHU��0DQDJLQJ�6HUYHU�6HFXULW\

Overview of Security ................................................................ 8-2

Controlling Who Can Configure and Manage the Server ......... 8-2

Controlling Who Can Create, Modify, and Delete Services...... 8-3

Securing Communications with the Server .............................. 8-4

Controlling Access to SAP BC Services and Files with ACLs 8-10

Controlling Access to SAP BC Services By Listening Port..... 8-17

Authenticating Clients............................................................. 8-20

0DQDJLQJ�6HUYHU�6HFXULW\ 6$3�$*

2YHUYLHZ�RI�6HFXULW\


� 2YHUYLHZ�RI�6HFXULW\

To secure access to your server and the data that resides on the server, you can:

g &RQWURO�ZKR�FDQ�FRQILJXUH�DQG�PDQDJH�WKH�VHUYHU��You can restrict access to the ServerAdministrator.

g &RQWURO�ZKR�FDQ�XVH�WKH�6$3�%XVLQHVV�&RQQHFWRU�'HYHORSHU�WR�FRQQHFW�WR�WKH�VHUYHU�You can specify who is authorized to create, edit, and delete the services that resideon the server.

g 6HFXUH�WKH�WUDQVPLVVLRQ�RI�GDWD�EHWZHHQ�6$3�%&�FOLHQWV�DQG�WKH�VHUYHU� You can configure alistening port for SSL communications.

g &RQWURO�DFFHVV�WR�6$3�%&�VHUYLFHV�DQG�WKH�ILOHV�WKDW�UHVLGH�RQ�WKH�VHUYHU. You can createAccess Control Lists (ACLs) that control access to individual services and files, andyou can restrict access to services based on the listening port on which an incomingrequest is received.

g 6SHFLI\�KRZ�\RX�ZDQW�WKH�VHUYHU�WR�DXWKHQWLFDWH�FOLHQWV� This allows you to authenticate aclient based on client certificates or user name/password authentication.

� &RQWUROOLQJ�:KR�&DQ�&RQILJXUH�DQG�0DQDJH�WKH�6HUYHU

Use the Server Administrator to configure and manage the server. Before the serverallows access to the Server Administrator, it ensures the user has administrator privileges.

A user has administrator privileges if he or she belongs to the Administrators group. Todetermine if a user has administrator privileges, the server authenticates the user to obtainhis or her user name. (For information about how the server determines the user name,refer to $XWKHQWLFDWLQJ�&OLHQWV on page 8-20.) After determining the user name, the serverdetermines if the user is a member of the Administrators group. If the user is a member ofthe Administrators group, the server allows access to the Server Administrator.

To grant administrator privileges to a user, you must assign that user to theAdministrators group.

1RWH

The user to whom you want to grant administrative privileges must already have auser account on the SAP Business Connector Server. If the user does not already havea user account, create one for him or her before you perform the following steps.

�*UDQWLQJ�DGPLQLVWUDWLYH�SULYLOHJHV�WR�D�XVHU


2. Choose tab page 8VHUV.


9LHZLQJ�RU�&KDQJLQJ�*URXS�0HPEHUVKLS


3. Select the user to whom you want to grant administrator privileges.

4. Choose (GLW�

5. In the list�*URXS�0HPEHUVKLS, select the $GPLQLVWUDWRUV group. (If other groups arealready selected in Group Membership, make sure to hold the CTRL key when youselect the $GPLQLVWUDWRUV group. Otherwise, you will deselect all of the user’s othergroup memberships.)

6. Select 6XEPLW�

1RWH

If you inadvertently deselect the user’s original group memberships while editing thisscreen, select 5HVHW to restore the user’s account setting to the original values.

� &RQWUROOLQJ�:KR�&DQ�&UHDWH��0RGLI\��DQG�'HOHWH�6HUYLFHV

A developer can use the SAP Business Connector Developer to create, modify, and deleteservices that reside on the server. Before the server allows a connection from the SAPBusiness Connector Developer, it ensures the user has developer privileges.

A user has developer privileges if he or she belongs to the Developers group. Todetermine if a user has developer privileges, the server authenticates the user to obtain hisor her user name. (For information about how the server determines the user name, referto $XWKHQWLFDWLQJ�&OLHQWV on page 8-20.) After determining the user name, the serverdetermines if the user is a member of the Developers group. If the user is a member of theDevelopers group, the server allows the connection between the SAP Business ConnectorDeveloper and the server to be established.

To grant developer privileges to a user, you must assign that user to the Developersgroup.

1RWH

The user to whom you want to grant administrative privileges must already have auser account on the SAP Business Connector Server. If the user does not already havea user account, create one for him or her before you perform the following steps.

�*UDQWLQJ�GHYHORSHU�SULYLOHJHV�WR�D�XVHU


2. Choose tab page 8VHUV.

3. Select the user to whom you want to grant developer privileges.


6HFXULQJ�&RPPXQLFDWLRQV�ZLWK�WKH�6HUYHU


4. Choose (GLW�

5. In the *URXS�0HPEHUVKLS list, select the 'HYHORSHUV group. (If other groups arealready selected in Group Membership, make sure to hold the CTRL key when youselect the 'HYHORSHUV group. Otherwise, you will deselect all of the user’s other groupmemberships.)

6. Select 6XEPLW�

1RWH

If you inadvertently deselect the user’s original group memberships while editing thisscreen, select 5HVHW�to restore the user’s account setting to the original values.

� 6HFXULQJ�&RPPXQLFDWLRQV�ZLWK�WKH�6HUYHU

An administrator can configure the SAP Business Connector Server to use SecureSockets Layer (SSL) to provide secure communications with the server. Use SSL toensure that data is transmitted privately and that the content of the data is not alteredduring transit.

�%DFNJURXQG�$ERXW�66/

In an SSL transaction, there is an SSL client and an SSL server. The SSL client initiatesan SSL transaction. At the beginning of an SSL transaction, the client and server performwhat is called an SSL handshake:

I. The server sends its digital certificate to the client. The client uses this certificateto authenticate the server, which assures the client that it is communicating withthe organization that the certificate identifies.

II. Optionally, the server can request a client certificate from the client. The servercan use the client certificate to authenticate the client.

III. The client and the server negotiate how they will securely transmit data.


66/�DQG�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU


�66/�DQG�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU

Depending on the situation, the SAP Business Connector Server can be either a client or aserver in an SSL transaction.

When a SAP BC client communicates via HTTPS with the SAP Business ConnectorServer, the SAP BC client is the SSL client and the SAP Business Connector Server is theSSL server.

6$3�%XVLQHVV&RQQHFWRU�6HUYHU

&OLHQW$SSOLFDWLRQ

66/�&OLHQW 66/�6HUYHU

+7736

When a service on the SAP Business Connector Server submits an HTTPS request toanother resource on the Internet, the SAP Business Connector Server is the SSL clientand the target system to which it is communicating is the SSL server.


,QWHUQHW5HVRXUFH

66/�&OLHQW 66/�6HUYHU

+7736

When the server acts as a client, during the SSL handshake it determines whether it hasconnected to a trusted site. It determines whether the site is trusted by comparing thedigital signature (or fingerprint) of the certificate authority that issued the SSL server’scertificate. If the server can match the fingerprint to a fingerprint it has on file, it logs amessage that indicates the certificate is signed by a known CA. If the server cannot matchthe fingerprint to a fingerprint it knows about, it records the fingerprint of the unknowncertificate authority to the system log and then continues with the SSL transaction.




�&KHFNOLVW�IRU�8VLQJ�66/

a 7DVN 1RWHV

Acquire a private/public key pair. Refer to ,WHPV�<RX�1HHG%HIRUH�&RQILJXULQJ�66/ onpage 8-7.

Create a certificate signing request (CSR)for a digital certificate and send it to acertificate authority.

Refer to ,WHPV�<RX�1HHG%HIRUH�&RQILJXULQJ�66/ onpage 8-7.

Obtain your digital certificate and thecertificate of the certificate authority thatsigned your digital certificate.

Ensure the certificates youreceive are in DER format.If they are not, use an SSLtoolkit to convert them toDER format.

Create a file that contains the private keyof your private/public key pair.

Place the file in a directoryto which the SAP BusinessConnector Server has access.

Create a file that contains your digitalcertificate and a file that contains thedigital certificate of the certificateauthority.

Place the files in a directoryto which the SAP BusinessConnector Server has access

If the SAP Business Connector Server willact as an SSL client, obtain the fingerprint(digital signatures) of the certificateauthorities that signed the certificates forthe Internet resources that wil act as SSLservers..

Place the fingerprints inplain text format in a singlefile. For more information,refer to ,WHPV�<RX�1HHG%HIRUH�&RQILJXULQJ�66/ onpage 8-7.

Configure the SAP Business ConnectorServer to use SSL.

Refer &RQILJXULQJ�WKH�6HUYHUWR�8VH�66/ to on page 8-9.

Add an HTTPS listening port if none aredefined.

If you want to allow only secureconnections to the server, ensure that theprimary listening port uses an HTTPSlistener and delete all other non-HTTPSlistening ports. Add as many additionalHTTPS listening ports as you want.

Refer to &RQILJXULQJ/LVWHQLQJ�3RUWV on page 6-4.


,WHPV�<RX�1HHG�%HIRUH�&RQILJXULQJ�66/


a 7DVN 1RWHV

If you want to authenticate clients usingclient certificates, configure the server torequest client certificates.

Refer to &OLHQW�&HUWLILFDWHVon page 8-21.

�,WHPV�<RX�1HHG�%HIRUH�&RQILJXULQJ�66/

Before the SAP Business Connector Server can act as an SSL server or SSL client, youmust obtain items that are required for an SSL transaction. To obtain these items, you canuse an SSL toolkit, for example, the toolkit provided by the OpenSSL project(http://www.openssl.org).

g 3ULYDWH�3XEOLF�.H\�3DLU��The SSL server and SSL client use public key encryption (alsoknown as asymmetric encryption) during the SSL handshake. This type of encryptionrequires a key pair that is made up of a public key and a private key. The data that isencrypted with one of the keys can only be decrypted using the other key in the pair.

Use an SSL toolkit to create the private/public key pair. Place the private key of thekey pair in a file. The public key is included in the digital certificate for the SAPBusiness Connector Server.

The party with which the SAP Business Connector Server is communicating obtainsthe public key from the SAP Business Connector Server’s certificate. To communicatesecurely, the other party can encrypt information with the public key before sending itto the SAP Business Connector Server, which decrypts the information with its privatekey.

g 'LJLWDO�&HUWLILFDWH�IRU�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU��Obtain a digital certificate thatattests to the identity of the SAP Business Connector Server. Use an SSL toolkit tocreate a Certificate Signing Request (CSR) for a digital certificate. You need tosupply the public key of the public/private key pair in the CSR.

After creating the CSR, send it to a certificate authority (CA) to request a digitalcertificate. Request the certificate in DER format. If you receive a certificate in PEMformat (or any format other than DER), use an SSL toolkit to convert it to DERformat.

When the SAP Business Connector Server acts as an SSL server, it uses thiscertificate in the SSL handshake to identify itself to the client. When the SAPBusiness Connector Server acts as an SSL client and the SSL server requests a clientcertificate, the SAP Business Connector Server presents this certificate as its clientcertificate.

g 6LJQLQJ�&$V�&HUWLILFDWH��The signing CA’s certificate attests to the identity of the CAthat signed the digital certificate for the SAP Business Connector Server. The CAshould send this certificate to you when it sends you the digital certificate for the SAPBusiness Connector Server. If it is not in DER format, use an SSL toolkit to convert itto DER format.




When the SAP Business Connector Server acts as an SSL client and the SSL serverrequests a client certificate, the SAP Business Connector Server presents thiscertificate along with its client certificate.

g )LQJHUSULQWV�RI�&HUWLILFDWH�$XWKRULWLHV� A fingerprint is a digital signature. The server usesfingerprints when it acts as an SSL client to determine if the SSL server’s certificatewas signed by a certificate authority that the server knows about.

The server is shipped with the fingerprints of several well-known certificateauthorities. If the Internet resources to which your server will connect use certificatesthat are signed by other certificate authorities, you can add their fingerprints to theserver. Add them in plain text format by copying and pasting them from a certificateinto a file or by typing the fingerprint into the file. Store all plain text fingerprints intoa single file.

The fingerprints are only used to provide information about trusted resources. An SSLconnection is still established if your server does not contain a fingerprint for acertificate authority; the server logs the use of the unknown certificate authority in thelog.

�8VLQJ�2SHQ66/�SURMHFW�66/�WRRONLW�WR�REWDLQ�LWHPV�UHTXLUHG�IRU�66/

The following describes how to obtain the items you need before configuring SSL usingthe OpenSSL project SSL toolkit (http://www.openssl.org).

1. Use the following command to create a random seed.

openssl md5 * > rand.dat

The random seed is placed in the rand.dat file.

2. Use the following command to generate a private key. The command specifies therandom seed file (rand.dat) that you created in the previous step.

openssl genrsa –rand rand.dat –des3 1024 > key.pem

The OpenSSL project SSL toolkit creates the private key (in PEM) format and placesit in the key.pem file.

1RWH

You will be prompted to enter a pass phrase when you execute the above command.Be sure to remember your pass phrase.

3. Use the following command to create the certificate signing request (CSR). Thecommand specifies the private key file (key.pem ) that you created in the previousstep. The OpenSSL project SSL toolkit creates the public key for your private keyand places it in the CSR.

This command prompts you to specify additional information, such as the name ofyour organization and your domain name.


&RQILJXULQJ�WKH�6HUYHU�WR�8VH�66/


openssl req –new –key key.pem –out csr.pem -config openssl.txt

1RWH

The file specified with the config parameter (openssl.txt ) is located in theopenssl/apps directory.

The OpenSSL project SSL toolkit places the CSR in the csr.pem file.

4. To obtain your digital certificate, send the CSR (csr.pem ) to a certificate authority(for example, Verisign).The certificate authority will send you your digital certificate. It should also send youits own digital certificate.

5. Convert your private key, digital certificate, and the certificate of the certificateauthority to DER format.• Use the following command to convert your private key. This command assumes

your private key is in a file named key.pem .

openssl rsa –in key.pem –out key.der –outform DER

The DER format version of the key is in the key.der file.• Use the following command to convert your digital certificate. This command

assumes your private key is in a file named cert.pem .

openssl x509 –in cert.pem –out cert.der –outform DER

The DER format version of the certificate is in the cert.der file.• Use the following command to convert the certificate of the certificate authority.

This command assumes the certificate is in a file named cacert.pem.

openssl x509 –in cacert.pem –out cacert.der –outform DER

The DER format version of the certificate is in the cacert.der file.

�&RQILJXULQJ�WKH�6HUYHU�WR�8VH�66/

The following procedure describes how to set up the SAP Business Connector Server touse SSL for secure transmission of data. If you want to set up the server to request clientcertificates for authenticating clients, see &OLHQW�&HUWLILFDWHV on page 8-21.

�7R�FRQILJXUH�WKH�VHUYHU�WR�XVH�66/�IRU�VHFXUH�FRPPXQLFDWLRQV


2. Choose tab page 6HFXULW\.

3. Choose (GLW�WKHVH�VHWWLQJV�

4. Set the 66/�&HUWLILFDWH parameters as follows:


&RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�DQG�)LOHV�ZLWK�$&/V


)RU�WKLV�SDUDPHWHU 6SHFLI\«

6HUYHUV�6LJQHG&HUWLILFDWH

Path and file name of the file that contains theSAP Business Connector Server’s digitalcertificate.

6LJQLQJ�&$V&HUWLILFDWH

Path and file name of the file that contains thecertificate for the certificate authority thatsigned the SAP Business Connector Server’sdigital certificate.

6HUYHUV�3ULYDWH�.H\ Path and file name of the file that contains theprivate key of the private/public key pairassociated with the SAP Business ConnectorServer’s digital certificate.

5. Enter the path and file name of the file that contains the plain text fingerprints in field&$�)LQJHUSULQW�)LOH,

6. Choose 6XEPLW�

7. Add an HTTPS listener if one does not already exist. Follow the instructions in$GGLQJ�/LVWHQLQJ�3RUWV on page 6-5. Specify HTTPS for the type of listener.

� &RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�DQG�)LOHV�ZLWK�$&/V

To control access to services that clients can invoke and the files that the server can serve,assign Access Control Lists (ACLs) to services and files.

�$ERXW�$&/V�DQG�WKH�3UHFHGHQFH�6HWWLQJ

ACLs control access to services and files at the group level. An ACL identifies groupsthat are allowed to access a service or file (Allowed Groups) and/or groups that are notallowed to access a service or file (Denied Groups). When identifying Allowed Groupsand Denied Groups, you select from groups that you have previously defined.

When a client requests that the server invoke a service, the server checks the ACLassociated with the service. If the client is a member of any of the groups defined asAllowed Groups, the server invokes the service. If the client is a member of any of thegroups defined as Denied Groups, the server denies the request to invoke the service.

When a client requests that the server serve a file, the server determines whether the fileis protected by an ACL. If the file is not protected by an ACL, the server serves the file. Ifit is protected, the server checks the ACL associated with the file. If the user is a memberof any of the groups defined as Allowed Groups, the server serves the file. If the user is amember of any of the groups defined as Denied Groups, the server does not serve the file.


$ERXW�$&/V�DQG�WKH�3UHFHGHQFH�6HWWLQJ


Request is denied if the client isa member of an Denied Group.

Request is allowed if the client isa member of an Allowed Group.

AllowedGroups

DeniedGroups

;

AllowedGroups

DeniedGroups

;

In addition to setting up ACLs, you need to set the Precedence. The Precedence identifieswhether the server allows or denies access to a service or file when it is not clear which todo from the information in the ACL. These ambiguous situations occur when the client iseither:

g A member of both an Allowed Group and a Denied Group

g Not a member of any of the Allowed Groups or Denied Groups

The Precedence setting is usedto determine whether the requestis allowed or denied.

The Precedence setting is usedto determine whether the requestis allowed or denied.

AllowedGroups

DeniedGroups

;

AllowedGroups

DeniedGroups

;

You can set the Precedence to one of the following settings:

$OORZ��This setting allows access to services and files in ambiguous situations

'HQ\��This setting denies access to services and files in ambiguous situations

The following table shows whether the server allows or denies access to a service or filebased on the client’s membership in the groups specified in the ACL and the Precedencesetting:




&OLHQW�LV�D�PHPEHURI�$OORZHG�*URXSV

&OLHQW�LV�D�PHPEHURI�'HQLHG�*URXSV 3UHFHGHQFH

$FFHVV�WR�WKH6HUYLFH

✔ n/a Allowed

✔ n/a Denied

✔ ✔ Allow Allowed

✔ ✔ Deny Denied✴

Allow Allowed

Deny Denied✴

✴The server allows access if the client is an administrator.

�6HWWLQJ�WKH�3UHFHGHQFH

The Precedence setting is a toggle. That is, if Precedence is set to Allow and you changeit, it becomes Deny (and vice versa).

�7R�FKDQJH�WKH�3UHFHGHQFH


2. Choose tab page $&/V.The server displays the current Precedence in the 3UHFHGHQFH section of the screen.

3. Choose &KDQJH�SUHFHGHQFH.

&DXWLRQ

The server comes with predefined ACLs, which are set up for the Allow Precedence. If you change thePrecedence to Deny, update the predefined ACLs to deselect all groups in the Denied Groups list. If youdo not update the Developers and Replicators ACLs, developers will no longer be authorized to connectto the server from the SAP BC Developer, and the Replicator user will no longer be authorized toperform package replication functions.

�3UHGHILQHG�$&/V

The server comes with the following predefined ACLs. Do not delete the predefinedACLs.

g $GPLQLVWUDWRUV. Allows only users in the Administrators group access to a serviceand denies all other users.


&UHDWLQJ�$&/V


g 'HIDXOW. Allows all users access to a service or file. When a service is not specificallyassigned an ACL, the server uses the Default ACL. If the ACL assigned to a serviceor file is deleted, the server uses the Default ACL.

g 'HYHORSHUV. Allows only users in the Developers group access to a service and deniesall other users.

g 5HSOLFDWRUV. Allows the Replicator user replication privileges. If you delete thisACL, the server will not be able to perform any package replication functions.

&DXWLRQ

The predefined ACLs are set up for the Allow Precedence. If you change the Precedence to Deny, updatethe ACLs to deselect all groups in the Denied Groups list. If you do not update the Developers andReplicators ACLs, developers will no longer be authorized to connect to the server from the SAP BCDeveloper, and the Replicator user will no longer be authorized to perform package replication functions.

�&UHDWLQJ�$&/V

When creating an ACL, you select groups to use for the Allowed Groups and DeniedGroups from previously defined groups.

�7R�FUHDWH�DQ�$&/

1. Select the $FFHVV task on the navigation panel.

2. Choose the $&/V tab if it is not already displayed.

3. Choose $GG�$&/.

4. Specify the name of the new ACL in field�$&/�1DPH.

5. In field�$OORZHG�*URXSV, select the group(s) to which you want to allow access.

6. In the 'HQLHG�*URXSV field, select the group(s) to which you want to deny access.

7. Select 6XEPLW.

�8SGDWLQJ�$&/V

After an ACL is created, you can edit it to add and/or remove groups that are identified asAllowed Groups and Denied Groups.

�7R�XSGDWH�DQ�$&/


2. Choose tab page $&/V.

3. Select the ACL you want to edit in the &XUUHQW�$&/V section of the screen.

4. Choose (GLW�$&/�




5. Make the changes to the $OORZHG�*URXSV and 'HQLHG�*URXSV.

6. To select additional groups without deselecting currently selected groups, press theCTRL key while you select the groups you want to select.

7. To deselect a group, press the CTRL key while you select the currently selectedentry.

8. Choose 6XEPLW.

�'HOHWLQJ�$&/V

You can delete any ACL except the Default ACL. You can delete ACLs that are currentlyassigned to services or files. When a client attempts to access a service or file that isassigned to a deleted ACL, the server uses the Default ACL to determine whether theclient is allowed or denied access.

When you delete an ACL that is assigned to a service, the service retains informationabout the deleted ACL. As a result, when you view the service information, the serverdisplays the name of the deleted ACL in the $&/ field. For information about how toassign a different ACL to a service, refer to $VVLJQLQJ�$&/V�WR�6HUYLFHV�DQG�,QWHUIDFHV onpage 8-16.

When you delete an ACL that is assigned to a file, update the .access file to assign adifferent ACL to the file. For more information about assigning ACLs to files, refer to$VVLJQLQJ�$&/V�WR�)LOHV�WKH�6HUYHU�&DQ�6HUYH on page 8-17.

&DXWLRQ

Do not delete the Administrators or Developers ACLs. If you do, the server will usethe Default ACL and allow all users access to services and files that should only beaccessed by users with administrator or developer privileges.

�7R�GHOHWH�DQ�$&/


2. Choose tab page $&/V�

3. Select the ACL you want to edit in the &XUUHQW�$&/V section of the screen.

4. Choose 'HOHWH�$&/. The server issues a prompt to verify that you want to delete theACL. Choose OK to remove the ACL.


+RZ�$&/V�:RUN�ZLWK�,QWHUIDFHV�DQG�6HUYLFHV


�+RZ�$&/V�:RUN�ZLWK�,QWHUIDFHV�DQG�6HUYLFHV

This section describes which ACL the server uses to control access to a service based onwhether there is:

g No ACL assigned to a service

g An ACL assigned to an interface for a service

g An ACL defined to a service

�:KHQ�1R�$&/�LV�$VVLJQHG�WR�D�6HUYLFH²'HIDXOW�$&/

By default, interfaces and services have no ACL assigned to them. When an interface orservice has no assigned ACL, the server displays in the $&/ field of the interface andservice information. When a client attempts to invoke a service that does not have anACL, the server uses the Default ACL.

1RWH

The Default ACL identifies the Everybody group as an Allowed group. This meansthat if you do not assign an ACL to a service, all clients can access the service. Inaddition, because the Everybody group is an Allowed group in the Default ACL, theserver does not authenticate the client before granting access to the service.

�:KHQ�<RX�$VVLJQ�DQ�$&/�WR�DQ�,QWHUIDFH

When you assign an ACL to an interface, it affects the subinterfaces and services in theinterface. The subinterfaces and services that do not have an assigned ACL inherit theACL that you assign to the interface. Services in the interface to which you specificallyassign an ACL are not affected. When an interface has an assigned ACL, the serverdisplays the name of the ACL in the $&/�field of the interface information.

When a subinterface or service inherits the ACL of its interface, the server displays thename of the ACL of the interface followed by an asterisk (*) in the $&/ field of theservice information. When the client attempts to invoke a service, the server uses theinherited ACL.




�:KHQ�<RX�$VVLJQ�DQ�$&/�WR�D�6HUYLFH

You can specifically assign an ACL to a service. When a service has an assigned ACL,the server displays the name of the assigned ACL in the $&/ field of the serviceinformation. When the client attempts to invoke the service, the server uses the assignedACL.

�6XPPDU\�RI�$&/�,QKHULWDQFH

The following table summarizes which ACL the server uses based on whether you haveassigned an ACL to a service, its immediate parent interface, or neither.

$&/�LVDVVLJQHG�WR�WKHVHUYLFH

,I�$&/�LVDVVLJQHG�WR�WKHLQWHUIDFH 7KH�VHUYHU�XVHV�WKH�

✔ ACL assigned to the service

✔ Inherited ACL that is assigned to theinterface

✔ ✔ ACL assigned to the service

Default ACL

�$VVLJQLQJ�$&/V�WR�6HUYLFHV�DQG�,QWHUIDFHV

You can assign an ACL to an individual service or to all the subinterfaces and services inan interface. Use the following procedure to assign a new or different ACL to a service orinterface.

�7R�DVVLJQ�DQ�$&/�WR�D�6HUYLFH�RU�,QWHUIDFH

1. Select 6HUYLFHV on the navigation panel.

2. Choose tab page 6HUYLFH�/LVW.

3. If the current screen does not list the interface or service to which you want to assignan ACL, select the name of the parent interface until the server displays a screen thatlists the interface or service with which you want to work.

4. Choose the or name of the currently assigned ACL in the $&/�field.

5. Select the ACL you want to assign to the service or interface from the $FFHVV�FRQWUROdrop down list.

6. Choose 6XEPLW.


$VVLJQLQJ�$&/V�WR�)LOHV�WKH�6HUYHU�&DQ�6HUYH


�7R�UHPRYH�DQ�$&/�IURP�D�6HUYLFH�RU�,QWHUIDFH


2. Choose tab page 6HUYLFH�/LVW.

3. If the current screen does not list the interface or service from which you want toremove an ACL, select the name of the parent interface until the server displays ascreen that lists the interface or service with which you want to work.

4. Choose the name of the currently assigned ACL in the $&/�field.

5. Select �1RQH! from the $FFHVV�FRQWURO drop down list.

6. Choose 6XEPLW.

�$VVLJQLQJ�$&/V�WR�)LOHV�WKH�6HUYHU�&DQ�6HUYH

The server can serve files that reside in the pub directory for a package or a subdirectoryof the pub directory. To protect the files, place a .access file in each directory thatcontains files you want to protect. For example, if you want to protect files in a pubdirectory and one of its subdirectories, place a .access file in each directory.

For each file in the directory that you want to protect, place a line in the .access file thatidentifies the name of the file followed by the ACL you want to use to protect the file.

For example, assume you have a directory that contains two files (adminpage.dsp andindex.htm) and you want to protect the adminpage.dsp file with the Administrators ACLso only administrators can access this file. You also want to assign the Default ACL tothe index.htm file so all users can access it. To accomplish this, you would place thefollowing records in the .access file:

adminpage.dsp Administratorsindex.htm Default

1RWH

In the above example, because you want all users to be able to access the index.htmfile, you could comit the index.htm Default from the .access file. The server does notcontrol access to files that are not identified in a .access file.

� &RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�%\�/LVWHQLQJ�3RUW

By default, the Server allows access to all service requests that come in on all listeningports (unless prohibited by an ACL). However, you can prevent access to services basedon the port on which the incoming service request arrives.

There are three ways to set up the restrictions for a port:


&RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�%\�/LVWHQLQJ�3RUW


g $OORZ�%\�'HIDXOW� Use this type to allow access to all services except those youspecify in a list that is associated with the port. All ports are initially set to Allow ByDefault with no service list, which indicates that clients can access all servicesthrough the port.

g 'HQ\�%\�'HIDXOW� Use this type to deny access to all services except those youspecify in a list that is associated with the port. You might use a Deny By Defaultport to restrict access so only the set of services that a single application uses areaccessible through the port. Set the port to Deny By Default and specify the servicesfor the application in the list associated with the port. Then, clients using theapplication can only access the specific services for the application.

g $GPLQLVWUDWRU�3RUW� Use this type to set up a single port for all administratoractivity. The server honors all service requests that come in on the AdministratorPort. You can associate a list of services with the Administrator Port. The list ofservices identifies services that are only available through the Administrator Port.When requests for services that are in this list come in on any other port, the serverdenies access. This includes Deny By Default ports that contain the same services inthe list of services to allow; the settings for the Administrator Port take precedence.

�7R�FRQWURO�DFFHVV�WR�6$3�%&�VHUYLFHV�E\�SRUW


2. Choose tab page 3RUWV.

3. Choose the port number with which you want to work.

4. In field�7\SH, select how you want to control access:

6HOHFW« 7R�KDYH�WKH�VHUYHU«

$OORZ�%\�'HIDXOW Allow all requests for services except for thoseyou identify in the ,QWHUIDFH�6HUYLFH�/LVW field.

'HQ\�%\�'HIDXOW Deny all requests for services except for thoseyou identify in the ,QWHUIDFH�6HUYLFH�/LVW field.

$GPLQLVWUDWRU�3RUW Allow all requests for services. Only allowaccess to the services in the ,QWHUIDFH�6HUYLFH/LVW field through this port. You can defineonly one Administrator Port.

1RWH

If you attempt to set up a second Administrator port, the Server creates the new portas an Administrative Port and resets the original Administrative Port. When a port isreset, the server returns it to Allow by Default with no Interface/Service List.


$VVLJQLQJ�$&/V�WR�)LOHV�WKH�6HUYHU�&DQ�6HUYH


&DXWLRQ

The SAP Business Connector Server executes services to perform the tasks yourequest while using the Server Administrator. Be careful when changing port settingsthat you do not restrict your current access to the services for the ServerAdministrator.

• Before changing the port you are currently using to $OORZ�%\�'HIDXOW, be sure the,QWHUIDFH�6HUYLFH list does not contain services that the Server Administrator uses.

• Before changing the port you are currently using to 'HQ\�%\�'HIDXOW, be sure the,QWHUIDFH�6HUYLFH list contains the services that the Server Administrator uses.

If you make any port other than the one that you are currently using an AdministratorPort, you will restrict access to the services that the Server Administrator requires.

5. For each service you want to add to the Interface/Service list, type the name of theinterface or service in the $GG�,QWHUIDFH�6HUYLFH field and select $GG. If you add aninterface to the Interface/Service List, the settings apply to all subinterfaces andservices in the interface.

The SAP Business Connector Server uses the Interface/Service list according to thesetting of the 7\SH field for the port:

)RU�WKLV�W\SH�� 7KH�VHUYHU«

$OORZ�%\�'HIDXOW Denies access to all services identified by theInterface/Service List.

'HQ\�%\�'HIDXOW Only allows access to the services identified bythe Interface/Service List.If you identify an interface or service that is alsoidentified in the Interface/Service list of theAdministrator Port (if one exists), the SAPBusiness Connector Server honors the settingfor the Administrator port and only allowsaccess to the services through the AdministratorPort.

$GPLQLVWUDWRU�3RUW Only allows access to the services identified inthe Interface/Service List when the requestcomes in on the Administrator Port.When you set the 7\SH to Administrator Port,the server automatically adds all interfaces andservices that are protected by the AdministratorsACL to the Interface/Service List. If you do notwant to restrict access to these services, you canremove them from the list.

6. Choose 'RQH to return to the previous screen.


$XWKHQWLFDWLQJ�&OLHQWV


&DXWLRQ

The changes you make take effect immediately, even before you select 'RQH. Thefunction of the 'RQH button is only to display the previous screen.

�7R�UHPRYH�LQWHUIDFHV�DQG�VHUYLFHV�IURP�WKH�,QWHUIDFH�6HUYLFH�/LVW


2. Choose tab page 3RUWV if it is not already displayed.

3. Choose the port number with which you want to work.

4. In the ,QWHUIDFH�6HUYLFH�/LVW section of the screen, choose the icon in the 5HPRYHcolumn for each interface or service that you want to remove.

5. Choose 'RQH to return to the previous screen.

&DXWLRQ

The changes you make take effect immediately, even before you select 'RQH. Thefunction of the 'RQH button is only to display the previous screen.

�7R�UHVHW�D�SRUW�WR�WKH�GHIDXOW


2. Choose tab page 3RUWV.

3. Choose the icon in the 5HVHW column for the port you want to reset.

The SAP Business Connector Server changes the type to Allow By Default andremoves any Interface/Service List.

� $XWKHQWLFDWLQJ�&OLHQWV

Authentication is determining who a client is. When the server performs authentication, itdetermines the user name of a client.

Authentication works with access control. After the server determines the user name of aclient, it can then determine whether the client should be granted access to the requestedresource. The server uses the client’s group membership to control access to the serverresources.


&OLHQW�&HUWLILFDWHV


7KH�VHUYHU�DXWKHQWLFDWHV�ZKHQD�FOLHQW�DWWHPSWV�WR«

7KH�VHUYHU�FRQWUROV�DFFHVV�WR�WKH�UHTXHVWHGUHVRXUFH�E\�GHWHUPLQLQJ�ZKHWKHU«

,QYRNH�D�VHUYLFH The client is a member of a group listed among theAllowed Groups or Denied Groups in the ACL thatis associated with the service.

$FFHVV�D�ILOH�WKDW�LV�SURWHFWHGE\�DQ�$&/

The client is a member of a group listed among theAllowed Groups or Denied Groups in the ACL thatis associated with the file.

$FFHVV�WKH�6HUYHU$GPLQLVWUDWRU

The client is a member of the AdministratorsGroup, which indicates the client has administratorprivileges.

&RQQHFW�WR�WKH�VHUYHU�IURP�WKH6$3�%&�'HYHORSHU

The client is a member of the Developers Group,which indicates the client has developer privileges.

The server first attempts to authenticate the client using client certificates. If the server isunable to authenticate using client certificates, it attempts to authenticate the client usingbasic authentication (user names and passwords).

�&OLHQW�&HUWLILFDWHV

A client certificate is a digital certificate that identifies a client. The server attempts toauthenticate using client certificates only if the incoming request is an HTTPS request.

If the server is configured to request client certificates, it requests the client certificateduring the SSL handshake that the client and server perform when initializing an SSLtransaction. If the server is required to receive client certificates, the client request fails ifthe client does not supply a client certificate.

After the SSL handshake is complete, the server authenticates the client using the clientcertificate. To authenticate the client, the server uses the certificates of certificateauthorities (CA certificates) that it knows about to validate the client certificate. If thecertificate is not valid, the request fails; the server does not execute the requested service.If the certificate is valid and signed by a trusted certificate authority, the server uses theCommon Name field in the client certificate as the client’s user name and continuesprocessing the request to invoke a service.

If the server cannot authenticate the client using client certificates, it authenticates theclient using basic authentication; that is by prompting for and validating a user name andpassword. For more information, refer to %DVLF�$XWKHQWLFDWLRQ��8VHU�1DPHV�DQG3DVVZRUGV� on page 8-23. The following lists reasons why the server cannot authenticatea client using client certificates:

g The server is not configured to use SSL.

g The server is not configured to request client certificates.


$XWKHQWLFDWLQJ�&OLHQWV


g The incoming request is not an HTTPS request.

g The client does not supply a client certificate.

g The CA certificate of the certificate authority that signed the client is not in the CAcertificate directory.

�&KHFNOLVW�IRU�8VLQJ�&OLHQW�&HUWLILFDWHV

a 7DVN 1RWHV

Configure the server to use SSL. Refer to 6HFXULQJ�&RPPXQLFDWLRQVZLWK�WKH�6HUYHU on page 8-4.

Obtain the certificates of theCertificate Authorities that youwant the server to use to validateclient certificates.

Place each certificate in a separate file.Place all the files in a directory towhich the SAP Business ConnectorServer has access. For moreinformaton, refer to ,WHPV�<RX�1HHG%HIRUH�&RQILJXULQJ�WKH�6HUYHU�WR5HTXHVW�&OLHQW�&HUWLILFDWHV on page 8-22

Configure the server to requestclient certificates.

Refer to &RQILJXULQJ�WKH�6HUYHU�WR5HTXHVW�&OLHQW�&HUWLILFDWHV on page 8-22.

�,WHPV�<RX�1HHG�%HIRUH�&RQILJXULQJ�WKH�6HUYHU�WR�5HTXHVW�&OLHQW&HUWLILFDWHV

Before configuring the server to request client certificates, you must configure the serverto use SSL and obtain the certificates that the server uses to validate client certificates.

g &RQILJXUH�WKH�VHUYHU�WR�XVH�66/� For information about configuring the server touse SSL, refer to 6HFXULQJ�&RPPXQLFDWLRQV�ZLWK�WKH�6HUYHU on page 8-4.

g &$�FHUWLILFDWHV� These are the certificates that the server uses to validate clientcertificates. One way to obtain these certificates is to extract them from a Webbrowser. Most Web browsers that support SSL are shipped with the certificates ofwell-known certificate authorities. If the certificates are not in DER format, use anSSL toolkit to convert them to DER format, for example, the SSL toolkit provided bythe OpenSSL project (http://www.openssl.org).

Place each certificate in a separate file. Place all the files in the same directory.

�&RQILJXULQJ�WKH�6HUYHU�WR�5HTXHVW�&OLHQW�&HUWLILFDWHV

Use this procedure to configure the server to request client certificates.

�7R�FRQILJXUH�WKH�VHUYHU�WR�UHTXHVW�FOLHQW�FHUWLILFDWHV



%DVLF�$XWKHQWLFDWLRQ��8VHU�1DPHV�DQG�3DVVZRUGV�


2. Select tab page 6HFXULW\.


4. In field�5HTXHVW�&OLHQW�&HUWLILFDWHV", choose the <HV radio button.

5. If you want the server to require client certificates for all requests that come in onHTTPS listening ports, select <HV in field�5HTXLUH�&OLHQW�&HUWLILFDWHV". If a clientdoes not supply a client certificate, the request fails.

6. In the &$�&HUWLILFDWH�'LUHFWRU\ field, type the path and directory name of thedirectory in which the CA certificates reside.

7. Choose 6XEPLW.

�%DVLF�$XWKHQWLFDWLRQ��8VHU�1DPHV�DQG�3DVVZRUGV�

When the server uses basic authentication, it prompts the client for a user name andpassword. If a user account is found for the supplied user name, the server authenticatesthe user name by comparing the supplied password to the password in the user accountfor the supplied user name. If the password is correct, the server proceeds with therequest. If the password is not correct, the server rejects the request. If a user account forthe supplied user name is not found, the server rejects the request.

If the client does not supply a user name or password, the server uses the Default useraccount for the client.

&OLHQW�VXSSOLHG�D�XVHUQDPH�SDVVZRUG"

8VHU�1DPHIRXQG"

3DVVZRUGFRUUHFW" 5HTXHVW«

YES YES YES proceeds

YES YES NO is rejected

YES NO n/a is rejected

NO n/a n.a proceeds usingthe Default user

account

For more information on setting up user accounts, refer to 'HILQLQJ�D�8VHU�$FFRXQWonpage 7-3. You can also use externally defined user accounts; for more information onhow to use external directories and how basic authentication works when using externalusers, refer to 8VLQJ�DQ�([WHUQDO�'LUHFWRU\��/'$3�RU�1,6� on page 9-1.

6$3�$* 8VLQJ�DQ�([WHUQDO�'LUHFWRU\��/'$3�RU�1,6�


&KDSWHU��8VLQJ�DQ�([WHUQDO�'LUHFWRU\��/'$3�RU�1,6�

Overview of Using External Directories.................................... 9-2

Configuring the Server to Use an External Directory................ 9-4

Considerations for User Accounts and Groups ........................ 9-8

Authenticating External Clients ................................................ 9-9

Granting Administrator Privileges to External Users .............. 9-10

Granting Developer Privileges to External Users ................... 9-11

Granting Access to Services and Files to External Users ...... 9-12

8VLQJ�DQ�([WHUQDO�'LUHFWRU\��/'$3�RU�1,6� 6$3�$*

2YHUYLHZ�RI�8VLQJ�([WHUQDO�'LUHFWRULHV


1RWH

This chapter describes how the server acts differently when it uses an externaldirectory rather than using internally-defined user and group information. It alsodescribes how to set up the server to use an external directory.

Before you read this chapter, you should understand how the server uses user andgroup information. Read the following sections if you have not already done so.

• 0DQDJLQJ�8VHUV�DQG�*URXSV on page 7-1

• &RQWUROOLQJ�:KR�&DQ�&RQILJXUH�DQG�0DQDJH�WKH�6HUYHU on page 8-2

• &RQWUROOLQJ�:KR�&DQ�&UHDWH��0RGLI\��DQG�'HOHWH�6HUYLFHV on page 8-3

• &RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�DQG�)LOHV�ZLWK�$&/V on page 8-10

• %DVLF�$XWKHQWLFDWLRQ��8VHU�1DPHV�DQG�3DVVZRUGV� on page 8-23

� 2YHUYLHZ�RI�8VLQJ�([WHUQDO�'LUHFWRULHV

If your site uses either Lightweight Directory Access Protocol (LDAP) or NetworkInformation Service (NIS) for user and group information, you can configure the SAPBusiness Connector Server to obtain user and group information from the externaldirectory. You can use only one external directory with SAP BC at a time, either LDAPor NIS.

LDAP and NIS are protocols designed to facilitate sharing information about resourceson a network. Typically, they are used to store profile information (login ID, password,etc.). You can also use them to store additional information.

Using your existing LDAP or NIS information allows you to take advantage of a centralrepository of user and group information. System administrators can add and removeusers from the central location. Users do not need to remember a separate password forSAP BC applications; they can use the same user names and passwords that they use forother applications.

�+RZ�WKH�6HUYHU�8VHV�([WHUQDOO\�'HILQHG�,QIRUPDWLRQ

The server can use externally-defined information for the same purposes it usesinternally-defined user and group information:

g To authenticate clients using user names and passwords

g To control who can configure and manage the server

g To control who can create, modify, and delete services using the SAP BC Developer

g To control access to services and files that are controlled by the server


:KHQ�WKH�6HUYHU�$FFHVVHV�([WHUQDOO\�'HILQHG�,QIRUPDWLRQ


Externally-defined information does not replace ACLs. To control access to servicesand files, you still need to set up the ACLs that identify the groups that are allowedand denied access to specific services and files. However, you can assign externally-defined groups to an ACL.

When you configure the server to use an external directory, the server displaysexternally-defined user and group information on screens in the Server Administrator(in addition to internally-defined user and group information). For example, when youdisplay the 1HZ�$&/ screen to create a new ACL, the server displays all groups thatare defined internally and externally in the $OORZHG�*URXSV and 'HQLHG�*URXSV fields.

Internally and externallydefined groups

�:KHQ�WKH�6HUYHU�$FFHVVHV�([WHUQDOO\�'HILQHG�,QIRUPDWLRQ

The server uses Java Naming and Directory Interface (JNDI) to access the user and groupinformation in LDAP or NIS. The server obtains externally-defined information in thefollowing circumstances:

g To authenticate clients

g To determine if an ACL allows or denies an action

g To display screens that contain externally-defined information

The server does not preload externally-defined user and group information. It accesses theinformation as it is needed to satisfy requests. When the server accesses information, itrequests the minimal amount it can to satisfy the request. The server stores the externally-defined information that it retrieves in cache. The information remains in the cache for a


&RQILJXULQJ�WKH�6HUYHU�WR�8VH�DQ�([WHUQDO�'LUHFWRU\


period of time you specify when you configure the server to use the external directory. Ifthe server receives subsequent requests that require the information it has in cache, it usesthe cached information rather than accessing the external directory.

1RWH

Because the server must interact with an external directory, client requests that requirethe server to access an external directory take a longer time for the server to completethan those that do not. The server also takes a longer time to display the $FFHVVscreens that display external information.

� &RQILJXULQJ�WKH�6HUYHU�WR�8VH�DQ�([WHUQDO�'LUHFWRU\

You can configure the server to use either LDAP or NIS.

�&RQILJXULQJ�WKH�6HUYHU�WR�8VH�/'$3

Use this procedure to configure the server to obtain user and group information fromLDAP.

�7R�FRQILJXUH�WKH�VHUYHU�WR�XVH�/'$3


2. Choose tab page -1',.


4. Select LDAP from the drop down list in the 3URYLGHU field. The server issues aprompt to verify that you want to change the setting. Choose 2..

The server redisplays the -1',�6HWWLQJV screen listing configuration settings that arespecific to LDAP.


6. Fill in the�6HWWLQJV�parameters as follows:

)RU�WKLV�SDUDPHWHU« 6SHFLI\«

6HUYHU�85/ The complete URL of the LDAP server. TheURL has the formatldap://KRVWQDPH:SRUWQXPEHU, for example,ldap://blue:389.


&RQILJXULQJ�WKH�6HUYHU�WR�8VH�/'$3



'LUHFWRU\�5RRW The distinguished name (DN) that defines theroot entry of your LDAP directory (e.g.,o=SAP, c=US).

&RQQHFWLRQ�SULQFLSDO The user ID the SAP Business ConnectorServer should supply to connect to the LDAPserver, for example, cn=DirectoryManager,o=SAP, c=US.

&RQQHFWLRQFUHGHQWLDOV

The password the SAP Business ConnectorServer should supply to connect to the LDAPserver.

8VHU�5RRW The name of the root where user entries arelocated on the LDAP system, relative to'LUHFWRU\�5RRW, for example, ou=People.

8VHU�)LOWHU A filter the SAP Business Connector Servershould use to narrow the selection of userswithin 8VHU�5RRW. for example,(objectclass=inetOrgPerson) or (uid=*).

This setting is optional. If you specify a filter,when the SAP Business Connector Serverrequests user information from the LDAPserver, the LDAP server only searches userentries that match the filter criteria.

For more information about LDAP searchfilters, consult 5)&��6HDUFK�)LOWHUV�IRU/'$3.

*URXS�5RRW The name of the root where group entries arelocated on the LDAP system, relative to'LUHFWRU\�5RRW, for example, ou=Group.


&RQILJXULQJ�WKH�6HUYHU�WR�8VH�DQ�([WHUQDO�'LUHFWRU\



*URXS�)LOWHU A filter the SAP Business Connector Servershould use to narrow the selection of groupswithin *URXS�5RRW, for example,(objectclass=groupOfNames) or (cn=*).

This setting is optional. If you specify a filter,when the SAP Business Connector Serverrequests group information from the LDAPserver, the LDAP server only searches groupentries that match the filter criteria.

For more informaton about LDAP searchfilters, consult 5)&��6HDUFK�)LOWHUV�IRU/'$3.

8VHU�,'�DWWULEXWH The name of the attribute that contains eachuser’s SAP BC user ID, for example, “uid”.

3DVVZRUG�DWWULEXWH The name of the attribute that contains eachuser’s SAP BC user password, for example,“userpassword”.

0HPEHU�DWWULEXWH The name of the attribute that specifies themembers of a group, for example, “member”.

$GGW¶O�LQIR��VWULQJ� A comma delimited list of additional stringattributes you want retrieved from the LDAPserver for each user. For example, if you wantto retrieve the “phonenumber” and “mail”attributes for each user, specify phonenumber,

mail.

$GGW¶O�LQIR��ELQDU\� A comma delimited list of additional binaryattributes you want retrieved from the LDAPserver for each user. For example, if you wantto retrieve the “userphoto” and “certificate”attributes for each user, specify userphoto,

certificate.

7LPHRXW��PV� Number of milliseconds that you want the SAPBusiness Connector Server to maintain userand group information that it retrieved from theLDAP server in cache. If the SAP BusinessConnector Server receives subsequent requeststhat it can satisfy with the information incache, it does so rather than accessing theLDAP server.


&RQILJXULQJ�WKH�6HUYHU�WR�8VH�1,6


7. Choose 6XEPLW.

8. Restart the server for the changes to take effect. For instructions, refer to 5HVWDUWLQJWKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU on page 4-5.

�&RQILJXULQJ�WKH�6HUYHU�WR�8VH�1,6

Use this procedure to configure the server to obtain user and group information from NIS.

�7R�FRQILJXUH�WKH�VHUYHU�WR�XVH�1,6

1. Select $FFHVV�on the navigation panel.



4. Select NIS from the drop down list in the 3URYLGHU field. The server issues a promptto verify that you want to change the setting. Choose 2..

The server redisplays the -1',�6HWWLQJV screen listing configuration settings that arespecific to NIS.

5. Select (GLW�WKHVH�VHWWLQJV.

6. Fill in the 6HWWLQJV parameters as follows:


6HUYHU�85/ The complete URL of the NIS server. TheURL has the format nis://KRVWQDPH��forexample, nis://blue.

'RPDLQ�1DPH The name of the domain being served by theNIS server.

7LPHRXW��PV� Number of milliseconds that you want the SAPBusiness Connector Server to maintain userand group information that it retrieved from theNIS server in cache. If the SAP BusinessConnector Server receives subsequent requeststhat it can satisfy with the information incache, it does so rather than accessing the NISserver.

7. Choose 6XEPLW.

8. Restart the server for the changes to take effect. For instructions, refer to to5HVWDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU on page 4-5.


&RQVLGHUDWLRQV�IRU�8VHU�$FFRXQWV�DQG�*URXSV


�6WRSSLQJ�8VH�RI�DQ�([WHUQDO�'LUHFWRU\

If you no longer want to use an external directory, you can update the configuration toremove the external directory configuration settings.

�7R�VWRS�XVLQJ�DQ�H[WHUQDO�GLUHFWRU\




4. Select None from the drop down list in the 3URYLGHU�field. The server issues a promptto verify that you want to change the setting. Choose 2..The server redisplays the -1',�6HWWLQJV screen, which now indicates that you are notusing an external provider of directory information.

5. Restart the server for the change to take effect. For instructions, refer to to 5HVWDUWLQJWKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU on page 4-5.

� &RQVLGHUDWLRQV�IRU�8VHU�$FFRXQWV�DQG�*URXSVThis section provides information about user accounts and groups that you shouldconsider if you are using an external directory for user and group information.

g <RX�VKRXOG�NHHS�LQWHUQDO�DQG�H[WHUQDO�XVHU�DFFRXQWV�DQG�JURXS�QDPHV�XQLTXH� It might getconfusing if you have an external user account that has the same user name as aninternal user account or an external group with the same group name as an internalgroup. If you do have identically named user names or group names, the serveralways uses the internally-defined information.

To avoid confusion, it is recommended that you do not set up user accounts or groupsinternally if you are using an external directory.

g <RX�VKRXOG�PDLQWDLQ�WKH�SUHGHILQHG�XVHU�DFFRXQWV� Although it is recommended that youdo not maintain both internally- and externally-defined user accounts, an exception isthat you maintain the following predefined user accounts:

• Default

• Administrator

• Developer

• Replicator

1RWH

The server always uses the internally-defined Replicator user account when publishinga package to another server or receiving packages from another server. You must keepthe Replicator user account if you plan to use the package replication feature to eitherpublish packages or subscribe to packages. For more information on packagereplication, refer to &RS\LQJ�3DFNDJHV�IURP�2QH�6HUYHU�WR�$QRWKHU on page 10-14.


6WRSSLQJ�8VH�RI�DQ�([WHUQDO�'LUHFWRU\


g <RX�VKRXOG�PDLQWDLQ�WKH�SUHGHILQHG�JURXSV� Although it is recommended that you do notmaintain both internally and externally-defined groups, an exception is that youmaintain the following predefined groups:

• Everybody

• Administrators

• Developers

• Replicators

g <RX�VKRXOG�RQO\�DVVLJQ�H[WHUQDOO\�GHILQHG�XVHUV�WR�H[WHUQDOO\�GHILQHG�JURXSV� Unpredictablesituations can occur when an externally-defined user is included as a member of aninternally-defined group. Only assign internally-defined users to internally-definedgroups and externally-defined users to externally-defined groups.

8VHUV

*URXSV

Administrator DeveloperReplicator Admin Lindsay Rebecca

Admins SAPBCDevsAdministrators DevelopersReplicators

([WHUQDO�'LUHFWRULHV6$3�%XVLQHVV�&RQQHFWRU�6HUYHU

An exception to this is that all users (internally- and externally-defined) are membersof the internally-defined Everybody group.

g <RX�FDQQRW�XVH�WKH�6HUYHU�$GPLQLVWUDWRU�WR�PDQDJH��L�H��FUHDWH��HGLW��RU�GHOHWH��/'$3�RU�1,6XVHU�DQG�JURXS�LQIRUPDWLRQ� To make changes to LDAP or NIS directories, follow yoursite’s standard directory update procedures.

� $XWKHQWLFDWLQJ�([WHUQDO�&OLHQWV

When the server is authenticating a client using user names and passwords, it firstattempts to find the user name and password internally. If it finds an internally-defineduser account for the supplied user name, the server authenticates the client using theinternally-defined information. If the supplied password is correct, the server proceedswith the request. If the supplied password is not correct, the server rejects the request.

If the server cannot find an internally-defined user account for the supplied user name, theserver accesses the external directory to obtain user name and password information forthe client. If it finds an externally-defined user account, the server authenticates the clientusing the externally-defined information. If the supplied password is correct, the serverproceeds with the request. If the supplied password is not correct, the server rejects therequest.


*UDQWLQJ�$GPLQLVWUDWRU�3ULYLOHJHV�WR�([WHUQDO�8VHUV


If the server cannot find either and internally or externally defined user account for theuser, the server rejects the request.

If the user does not supply a user name or password, the server uses the internally-definedDefault user account.

� *UDQWLQJ�$GPLQLVWUDWRU�3ULYLOHJHV�WR�([WHUQDO�8VHUV

The Administrators ACL controls who has administrator privileges. Because you cannotassign externally-defined users to internally-defined groups, you cannot grant externally-defined users administrator privileges by assigning them to the internally-definedAdministrators group. Instead, you need to set up an externally-defined group foradministrators. Then, identify the externally-defined group of administrators to theAdministrators ACL.

8VHUV

*URXSV

$&/V

Administrator Admin

AdminsAdministrators

Administrators

([WHUQDO6$3�%&�6HUYHU

�7R�JUDQW�DGPLQLVWUDWRU�SULYLOHJHV�WR�DQ�H[WHUQDOO\�GHILQHG�XVHU

1. Set up an externally-defined user account for the user if one does not already exist.

2. Set up an externally-defined administrators group if one does not already exist.

&DXWLRQ

Do not name the externally-defined group $GPLQLVWUDWRUV. The name of the groupmust not be the same name as any internally-defined group.

3. Make the externally-defined user a member of the externally-defined administratorsgroup.

4. Update the Administrators ACL to include the externally-defined administratorsgroup in the $OORZHG�*URXSV field.

For instructions on how to update an ACL, refer to 8SGDWLQJ�$&/V on page 8-13.




When the server displays the (GLW�$&/�,QIRUPDWLRQ screen, it displays externally-defined groups in both the�$OORZHG�*URXSV and 'HQLHG�*URXSV fields. Select theexternally-defined administrators group in the�Allowed Groups field while pressingthe CTRL key to grant users in the externally-defined administrators group SAP BCadministrator privileges. (Pressing the CTRL key allows you to select the groupwithout deselecting the currently selected groups.)

1RWH

If the ACL Precedence setting is set to Deny, be sure to deselect all groups in the'HQLHG�*URXSV list.

� *UDQWLQJ�'HYHORSHU�3ULYLOHJHV�WR�([WHUQDO�8VHUV

The Developers ACL controls who can connect to the SAP Business Connector Serverfrom the SAP BC Developer to create, modify, and delete services that reside on theserver. Because you cannot assign externally-defined users to internally-defined groups,you cannot grant externally-defined users developer privileges by assigning them to theinternally-defined Developers group. Instead, you need to set up an externally-definedgroup for SAP BC developers. Then, identify the externally-defined group to theDevelopers ACL.

Developer Lindsay Rebecca

SAPBCDevsDevelopers

Developers

8VHUV

*URXSV

$&/V

([WHUQDO�'LUHFWRU\6$3�%&�6HUYHU

�7R�JUDQW�GHYHORSHU�SULYLOHJHV�WR�DQ�H[WHUQDOO\�GHILQHG�XVHU

1. Set up an externally-defined user account for the user if one does not already exist.

2. Set up an externally-defined developers group if one does not already exist.


*UDQWLQJ�$FFHVV�WR�6HUYLFHV�DQG�)LOHV�WR�([WHUQDO�8VHUV


&DXWLRQ

Do not name the externally-defined group 'HYHORSHUV. The name of the group mustnot be the same name as any internally-defined group.

3. Make the externally-defined user a member of the externally-defined developersgroup.

4. Update the Developers ACL to include the externally-defined developers group in the$OORZHG�*URXSV field.

For instructions on how to update an ACL, refer to 8SGDWLQJ�$&/V on page 8-13.When the server displays the�(GLW�$&/�,QIRUPDWLRQ screen, it displays externally-defined groups in both the $OORZHG�*URXSV and 'HQLHG�*URXSV fields. Select theexternally-defined developers group in the $OORZHG�*URXSV field while pressing theCTRL key to grant users in the externally-defined developers group SAP BCadministrator privileges. (Pressing the CTRL key allows you to select the groupwithout deselecting the currently selected groups.)

&DXWLRQ

If the ACL Precedence setting is set to Deny, be sure to deselect all groups in the'HQLHG�*URXSV list.

� *UDQWLQJ�$FFHVV�WR�6HUYLFHV�DQG�)LOHV�WR�([WHUQDO�8VHUV

You create ACLs that control access to services and files and assign them to the specificservices and files that you want to protect.

To grant access to a service or file, the server first uses internally-defined information todetermine whether the client is a member of allowed or denied groups listed in the ACL.If the server cannot find the information internally, it obtains externally-definedinformation to determine if the ACL allows or denies access.

If you want to allow an externally-defined user access to a service or file, update the ACLthat protects the service or file to identify the external user’s group as an Allowed groupin the ACL. Similarly, if you explicitly want to deny an externally-defined user access toa service or file, update the ACL that protects the service or file to identify the externaluser’s group as a Denied group in the ACL.




8VHUV

*URXSV

$&/V

Daniel

Finance

Finance

([WHUQDO6$3�%XVLQHVV&RQQHFWRU�6HUYHU

Leanna

$OORZHG�*URXSV

'HQLHG�*URXSV

EverybodyAdministratorsDevelopersReplicatorsFinanceMarketing

EverybodyAdministratorsDevelopersReplicatorsFinanceMarketing

Marketing

Finance

$&/�1DPH Finance

Marketing

Daniel is granted accessto the services protectedby the Finance ACLbecause his externalgroup is an Allowed group.

Leanna is denied accessto the services protectedby the Finance ACLbecause her externalgroup is a Denied group.

For information about working with ACLs, refer to &UHDWLQJ�$&/V on page 8-13 and8SGDWLQJ�$&/V on page 8-13.


*UDQWLQJ�$FFHVV�WR�6HUYLFHV�DQG�)LOHV�WR�([WHUQDO�8VHUV


6$3�$* 0DQDJLQJ�3DFNDJHV


&KDSWHU�� 0DQDJLQJ�3DFNDJHV

Using Packages ..................................................................... 10-2

How the Server Stores Package Information ......................... 10-3

Finding Information about Your Packages ............................. 10-4

Working with Packages .......................................................... 10-9

Copying Packages from One Server to Another .................. 10-14

0DQDJLQJ�3DFNDJHV 6$3�$*

8VLQJ�3DFNDJHV


� 8VLQJ�3DFNDJHVA package contains a set of services and related files, such as specifications, records, andoutput templates. When you add a service, specification, record, or output template to theSAP Business Connector Server, you must add it to a package. Use a package to groupservices and related files.

By placing related files in a package, you can easily manage all the services and files inthe package as a unit. For example, you can make them all available, disable them,refresh them, or delete them with one action. Additionally, if you have more than oneSAP Business Connector Server installed, you can use the package replication feature tocopy all the services and files in a package to another server.

You can group your services using any package structure you choose, though mostorganizations group services into packages by function or application. For example, youmight put all purchasing-related services in a package called "PurchaseOrderMgt" and alltime-reporting services into "TimeCards."

1RWH

Every service on the server must belong to a package. Before you can make a serviceavailable for execution, you must load the package to which it belongs.

�3UHGHILQHG�3DFNDJHV

The SAP Business Connector Server comes with the following predefined packages:

g 'HIDXOW� This package is empty.

g :P'HPRV� This package contains sample services.

g :P3XEOLF� This package contains services (i.e., utilities) that you can safely invokefrom your client applications and services.

g :P5RRW� This package contains services that the server uses for core functionalityand auxiliary files. Do not alter or delete this package.

g :P:LQ�� This package contains Windows-specific samples, such as sample VisualBasic services.

&DXWLRQ

Never remove the WmRoot packages. The SAP Business Connector Server uses theservices in these packages.


3UHGHILQHG�3DFNDJHV


� +RZ�WKH�6HUYHU�6WRUHV�3DFNDJH�,QIRUPDWLRQThe server physically stores package information in the sapbc/server/packages directory.The server creates a new subdirectory for each package. The name of the subdirectory isthe name of the package. For example, if a package is named "TimeCards", the servercreates the sapbc/server/packages/TimeCards directory to hold the files for the package.

When you create a new package, the server creates the following subdirectories to holdall the files associated with the package:

3DFNDJH1DPH

code

classes

pub

templates

widls

doc

Java services

Web documents

Templates

WIDL Services

Package documentation

jarssource

ns Namespace of the package

g 7KH�FRGH�VXEGLUHFWRU\ holds the Java and C/C++ services that belong to thispackage. Within the code subdirectory is the classes, jars, source, and libsubdirectories:

• The classes subdirectory is for Java classes for the Java and C/C++ services.

• The jars subdirectory is for Java classes that are packaged together in jar files.

• The source subdirectory is for the source of Java services.

• The libs subdirectory holds DLLs or specialized libraries that the Java and C/C++services use.

1RWH

The SAP Business Connector Server does not automatically create the libs directorybecause the directory’s existence prevents you from reloading a package withoutrestarting the server. You cannot reload a package that uses shared libraries; you mustrestart the server.


)LQGLQJ�,QIRUPDWLRQ�DERXW�<RXU�3DFNDJHV


For ease of administration, place services that use shared libraries in the samepackage.

g 7KH�GRF�VXEGLUHFWRU\ holds documentation for the package.

g 7KH�QV�VXEGLUHFWRU\ holds flows, specifications, records, and code fragments forJava services.

g 7KH�SXE�VXEGLUHFWRU\ holds Web documents for the package. For instructions onhow to access the Web documents for a package, refer to 'LVSOD\LQJ�'RFXPHQWDWLRQIRU�D�3DFNDJH on page 10-8.

g 7KH�WHPSODWHV�VXEGLUHFWRU\ holds output templates that are associated with thispackage.

g 7KH�ZLGOV�VXEGLUHFWRU\ holds WIDL services that are associated with this package.

�0DQLIHVW�)LOH

Each package has a manifest file. It contains:

g ,QGLFDWLRQ�RI�ZKHWKHU�WKH�SDFNDJH�LV�HQDEOHG�RU�GLVDEOHG� The server does not loaddisabled packages at server initialization and you cannot execute services that residein disabled packages.

g 3DFNDJH�YHUVLRQ�QXPEHU� You can assign version numbers to your packages. Forinformation, refer to ,GHQWLI\LQJ�D�9HUVLRQ�1XPEHU�IRU�D�3DFNDJH on page 10-13.

g 3DFNDJH�GHSHQGHQFLHV��LI�DQ\��IRU�WKH�SDFNDJH� For a specific package, you canidentify other packages that the server should load before it loads the services in aparticular package. In other words, you can identify when one package depends onanother. For information, refer to ,GHQWLI\LQJ�3DFNDJH�'HSHQGHQFLHV on page 10-13

g /LVW�RI�VWDUWXS�DQG�VKXWGRZQ�VHUYLFHV��LI�DQ\��IRU�WKH�SDFNDJH� For moreinformation about startup and shutdown services and how to identify services andstartup and shutdown services, refer to 5XQQLQJ�6HUYLFHV�:KHQ�3DFNDJHV�DUH/RDGHG�8QORDGHG on page 11-11

The manifest for a package is in the manifest.v3 file in the top directory for the package.

� )LQGLQJ�,QIRUPDWLRQ�DERXW�<RXU�3DFNDJHV

The server displays a variety of information about your packages. The section describesthe information that is available and the procedures to use to display the information.

,QIRUPDWLRQ

List of all of the packages that reside on your server

Status of whether the server successfully loaded the package or not


9LHZLQJ�WKH�3DFNDJHV�WKDW�5HVLGH�RQ�<RXU�6HUYHU


,QIRUPDWLRQ

Status of whether the package is enabled or disabled

Version number of the package

List of services in a package that the server successfully loaded intomemory

List of services in a package that the server failed to load into memory

List of load errors for the package

List of startup and shutdown services in a package

List of packages on which a package depends

List of servers that subscribe to this package

Date and time a ZIP file was made for this package

Documentation for the package

�9LHZLQJ�WKH�3DFNDJHV�WKDW�5HVLGH�RQ�<RXU�6HUYHU

The 3DFNDJHV screen of the Server Administrator lists all packages that reside on yourserver. It also displays whether the server successfully loaded the package and whetherthe package is enabled.

�7R�YLHZ�WKH�SDFNDJHV�WKDW�UHVLGH�RQ�WKH�VHUYHU

1. Select 3DFNDJHV on the navigation panel.

2. Select tab page $OO�3DFNDJHV.

�'HWHUPLQLQJ�:KHWKHU�WKH�6HUYHU�6XFFHVVIXOO\�/RDGHG�WKH�3DFNDJH

The server displays a status icon in the /RDGHG"�column of the 3DFNDJHV screen. Thecolor of the icon indicates whether the server successfully loaded the package.

&RORU ,QGLFDWHV�WKDW«

*UHHQ The server successfully loaded all services associated with thepackage. The services in the package are available for execution.The server also displays the green icon if the package is empty.




<HOORZ The server did not load one or more of the services associated withthe package. The services that the server successfully loaded areavailable for execution. For instructions on how to determine whichservices the server did not successfully load and why, refer to'LVSOD\LQJ�,QIRUPDWLRQ�DERXW�D�3DFNDJH on page 10-6.

5HG The server did not load any of the services associated with thepackage. None of the services are available for execution. Forinstructions on how to determine why the server could not load theservices, refer to 'LVSOD\LQJ�,QIRUPDWLRQ�DERXW�D�3DFNDJH on page10-6.

When the server is started, it automatically loads into memory all services that are inenabled packages. If a package is disabled at startup, the server loads the services intomemory when the package is enabled. You can manually reload a package into memoryby reloading it. Refer to 5HORDGLQJ�D�3DFNDJH on page 10-11for instructions on reloadinga package.

�'HWHUPLQLQJ�:KHWKHU�WKH�3DFNDJH�LV�(QDEOHG�RU�'LVDEOHG

The server displays a status icon in the (QDEOHG"�column of the 3DFNDJHV screen. Thecolor of the icon indicates whether package is enabled or disabled. A package must beenabled before the server allows clients access to the services in the package.

&RORU ,QGLFDWHV�WKDW«

*UHHQ The package is enabled and clients can invoke the services in thepackage.

5HG The package is disabled and clients cannot invoke the services inthe package.

For instructions on enabling and disabling packages, refer to (QDEOLQJ�D�3DFNDJH on page10-11 and 'LVDEOLQJ�D�3DFNDJH on page 10-11.

�'LVSOD\LQJ�,QIRUPDWLRQ�DERXW�D�3DFNDJH

The 3DFNDJH�,QIRUPDWLRQ�IRU�3DFNDJH1DPH screen displays the following informationabout a package:

g The version number that you specified for the package

g How many services in the package are loaded in the server’s memory and access tothe list of these services


'LVSOD\LQJ�,QIRUPDWLRQ�DERXW�D�3DFNDJH


g How many services in the package are not loaded in the server’s memory, a list ofthese services, and the reason why the server could not load them

g The list of startup and shutdown services in the package

g The list of packages that this package depends on (package dependencies)

g The list of subscribers to this package

g When the last ZIP file was created for the package

�7R�GLVSOD\�LQIRUPDWLRQ�DERXW�D�SDFNDJH



3. Select on the name of the package for which you want to display information.

The server displays the 3DFNDJH�,QIRUPDWLRQ�IRU�3DFNDJH1DPH screen that containsthe following fields:

)LHOG 'HVFULSWLRQ

3DFNDJH�1DPH Name of the package.

9HUVLRQ Version number of the package. Forinformation about setting the versionnumber, refer ,GHQWLI\LQJ�D�9HUVLRQ�1XPEHUIRU�D�3DFNDJH on page 10-13.

6HUYLFHV�/RDGHG Number of services that the serversuccessfully loaded. If the serversuccessfully loaded one or more services,the server displays the �VKRZ�OLVW� link.Select this link to have the server list theservices that it successfully loaded.

6HUYLFHV�1RW/RDGHG

Number of services that the server failed toload. If the server failed to load one or moreservices, the /RDG�(UURUV�section of thescreen lists the services that it could notload, along with the reason.

6WDUWXS�6HUYLFHV List of the services that you or anotheradministrator have identified as startupservices. For more information aboutstartup services, refer to 5XQQLQJ�6HUYLFHV:KHQ�3DFNDJHV�DUH�/RDGHG�8QORDGHG on page11-11.




)LHOG 'HVFULSWLRQ

6KXWGRZQ�6HUYLFHV List of the services that you or anotheradministrator have identified as shutdownservices. For more information aboutshutdown services, refer to 5XQQLQJ�6HUYLFHV:KHQ�3DFNDJHV�DUH�/RDGHG�8QORDGHG on page11-11.

3DFNDJH'HSHQGHQFLHV

List of the packages that you want theserver to load before it loads this package.For more information about packagedependencies, refer to Identifying PackageDependencies on page 10-13.

6XEVFULEHUV List of other SAP Business ConnectorServers that subscribe to this package. Forinformation on how to copy packages fromone server to another, how to subscribe topackages, and how to publish packages toanother server, refer to &RS\LQJ�3DFNDJHVIURP�2QH�6HUYHU�WR�$QRWKHU on page 10-14.

=LS�PRG�WLPH Date and time when the last distribution file(ZIP file) was created for this package. Formore information about creatingdistribution files, refer to 3XEOLVKLQJ�D3DFNDJH on page 10-18.

/RDG�(UURUV List of the services that the server failed toload, along with the reason why the servercould not load each service.

�'LVSOD\LQJ�'RFXPHQWDWLRQ�IRU�D�3DFNDJH

You can document the function of a package and its services in Web documents that theSAP Business Connector Server will serve. Place the Web documents in the pubsubdirectory for a package.

Be sure to create an index.html file that holds the home page for the package and containslinks to the other Web documents for the package.

�7R�DFFHVV�WKH�KRPH�SDJH�IRU�D�SDFNDJH



3. Select the home icon for the package.


'LVSOD\LQJ�'RFXPHQWDWLRQ�IRU�D�3DFNDJH


�7R�DFFHVV�DQ\�:HE�GRFXPHQW�IRU�D�SDFNDJH

Enter the URL for the Web document. The URLs for the Web documents have thefollowing format:

http://host:port/PackageName/Docname

where:

KRVW�SRUW is the server name and port address of the SAP Business ConnectorServer

3DFNDJH1DPH is the name of the package in which the Web document resides

'RF1DPH is the name of the Web document. If you do not specify 'RF1DPH,the server displays the index.html file.

� :RUNLQJ�ZLWK�3DFNDJHVYou can perform the following tasks that act on all the files in a package as a unit:

8VH�WKLVIXQFWLRQ� :KHQ�\RX�ZDQW�WR�

&UHDWH Create a new package.

$FWLYDWH Use a package that you just created without having to restartthe server.

5HORDG Reload the services in the package into memory withouthaving to restart the server.

(QDEOH Enable a package that you previously disabled.

'LVDEOH Disable access to a package, but do not want to delete thepackage.

'HOHWH Delete all services and related files in a package.

5HFRYHU Recover the services and related files from a package that youpreviously deleted. You can only recover a deleted package if youhad the server save a copy of the package before deleting it.

In addition, you can identify the following information for a package:

,I�\RX�ZDQW�WR�LGHQWLI\�

A version number for the package


:RUNLQJ�ZLWK�3DFNDJHV


,I�\RX�ZDQW�WR�LGHQWLI\�

Packages that must be loaded before a specific package is loaded (packagedependencies)

�&UHDWLQJ�D�3DFNDJH

When you want to create a new grouping for services and related files, create a package.This creates an empty package into which your developers can store services,specifications, records, and output templates. When you create a package, the serverbuilds the directory structure of the package as described in +RZ�WKH�6HUYHU�8VHV([WHUQDOO\�'HILQHG�,QIRUPDWLRQ on page 9-2.

�7R�FUHDWH�D�SDFNDJH


2. Select tab page 3DFNDJH�0DQDJHPHQW.

3. In the &UHDWH�D�QHZ�SDFNDJH�section of the screen, type the name for the new packagein field�3DFNDJH�QDPH.

&DXWLRQ

Do QRW use periods (.) in the name of a package. The watt.server.illegalNSCharssetting in the server.cnf file (which is located in the VDSEF/server/configdirectory) defines all the characters that you cannot use when naming SAPBCpackages.

4. Choose &UHDWH.

�$FWLYDWLQJ�D�3DFNDJH

If you add a package to the server while the server is running, the package is not availableuntil either you restart the server or you activate the package.

�7R�DFWLYDWH�D�SDFNDJH



3. In the $FWLYDWH�LQDFWLYH�SDFNDJHV section of the screen, select the package you want toactivate from the 3DFNDJH�QDPH drop down list.

4. Choose $FWLYDWH.


5HORDGLQJ�D�3DFNDJH


�5HORDGLQJ�D�3DFNDJH

If the server is running when a developer changes a Java service or flow service, youmust reload the package in which the service is contained for the changes to take effect.Reloading the package invokes the VM class loader to reload the package’s Java servicesand reloads the flow services into memory.

�7R�UHORDG�D�SDFNDJH

1. Select the 3DFNDJHV task on the navigation panel.

2. Select the $OO�3DFNDJHV�tab if it is not already displayed.

3. Select the reload icon in the 5HORDG column for the package.

The icon in the /RDGHG" column indicates whether the server loaded the packagesuccessfully. For more information, refer to 'HWHUPLQLQJ�:KHWKHU�WKH�6HUYHU�6XFFHVVIXOO\/RDGHG�WKH�3DFNDJH on page 10-5.

�(QDEOLQJ�D�3DFNDJH

To allow clients access to the services in a package, you must ensure the package isenabled. Before the server can execute a service in a package, the package must beenabled and the service must be loaded. By default, the packages are enabled.

When you enable a disabled package, the server loads the services in the package intomemory.

�7R�HQDEOH�D�SDFNDJH

1. Select the 3DFNDJHV task on the navigation panel.

2. Select tab page $OO�3DFNDJHV�tab if it is not already displayed.

3. Select the red icon in the (QDEOHG" column for the package you want to enable. Theserver issues a prompt to verify that you want to enable the package. Select OK toenable the package. When the package is enabled, the server displays a green icon inthe (QDEOHG" column.

�'LVDEOLQJ�D�3DFNDJH

When you want to temporarily prohibit access to the services in a package, disable thepackage. When you disable a package, the server unloads all of its services from memory.

&DXWLRQ

Never disable the WmRoot package. The SAP Business Connector Server uses theservices in this package.


:RUNLQJ�ZLWK�3DFNDJHV


�7R�GLVDEOH�D�SDFNDJH



3. Choose the green icon in the (QDEOHG" column for the package you want to disable.The server issues a prompt to verify that you want to disable the package. Select 2.to disable the package. When the package is disabled, the server displays a red icon inthe (QDEOHG" column.

1RWH

The server retains the access status of a package (enabled or disabled) across serverrestarts. When you start the server, the server does not load services in disabledpackages.

�'HOHWLQJ�D�3DFNDJH

When you no longer need the services and files in a package, you can delete the package.When you delete a package, you can optionally select to save a copy of the package. Ifyou save a copy, the server copies the package to the sapbc/server/replicate/salvagedirectory before deleting the package from the sapbc/server/packages directory. Ifneeded, you can recover the package at a later time. For instructions on recovering adeleted package, refer to 5HFRYHULQJ�D�3DFNDJH on page 10-13.

&DXWLRQ

Never delete the WmRoot package. SAP Business Connector Server uses the servicesin this package.

�7R�GHOHWH�D�SDFNDJH



3. In the 'HOHWH�H[LVWLQJ�SDFNDJHV section of the screen, select the package you want todelete from the drop down list in the 3DFNDJH�QDPH field.

4. If you want to save a copy of the package so you can recover it if it is needed again,check the 6DIH�GHOHWH checkbox in the 2SWLRQ field.

5. Select 'HOHWH.


5HFRYHULQJ�D�3DFNDJH


�5HFRYHULQJ�D�3DFNDJH

If you deleted a package using the 6DIH�GHOHWH option and you need the package again, youcan recover the package.

�7R�UHFRYHU�D�SDFNDJH



3. In the 5HFRYHU�GHOHWHG�SDFNDJHV section of the screen, select the package you want torecover from the drop down list in the�3DFNDJH�QDPH field.

4. If you want the server to enable the package after it is recovered, check the (QDEOHWKLV�SDFNDJH�XSRQ�UHFRYHU\�checkbox in the 2SWLRQ field.

5. Choose 5HFRYHU.

�,GHQWLI\LQJ�D�9HUVLRQ�1XPEHU�IRU�D�3DFNDJH

To indicate different versions of packages, you can give a package a version number. Bydefault, the server assigns all packages version number 1.0.

�7R�LGHQWLI\�D�YHUVLRQ�QXPEHU�IRU�D�SDFNDJH



3. Select the name of the package for which you want to specify a version number.

4. Choose (GLW�6HWWLQJV.

5. Type the version number in the 3DFNDJH�9HUVLRQ field. Typically, you should specifya decimal number with one decimal place (e.g., 1.3, 3.4, or 4.4).

6. Choose 6XEPLW.

�,GHQWLI\LQJ�3DFNDJH�'HSHQGHQFLHV

If you have a package that requires other packages be loaded before it is loaded, set uppackage dependencies. For example, assume you have a package named "Finance" thathas a startup service that invokes a service in the "FinanceUtil" package. For the startupservice to execute, the "FinanceUtil" package must be loaded before the "Finance"package is loaded. To ensure that the "FinanceUtil" package is loaded before the"Finance" package, you would identify the "FinanceUtil" package as a packagedependency for the "Finance" package.

Use this procedure to identify package dependencies for a package.


&RS\LQJ�3DFNDJHV�IURP�2QH�6HUYHU�WR�$QRWKHU


�7R�LGHQWLI\�SDFNDJH�GHSHQGHQFLHV�IRU�D�SDFNDJH


2. Select tab page $OO�3DFNDJHV if it is not already displayed.

3. Select the name of the package for which you want to specify a package dependency.

4. Follow the (GLW�'HSHQGHQFLHV link in the 3DFNDJH�'HSHQGHQFLHV field.

5. Type the name of the package that you want loaded before this package, along withits version number in the $GG�GHSHQGHQF\ box. Place either a space or semicolon (;)between the package name and version number.

For example, to indicate you want version 3.2 of the "FinanceUtil" package loadedbefore this package, specify FinanceUtil 3.2 or FinanceUtil; 3.2.

To identify multiple versions of the same package, use an asterisk (*) in the versionnumber. For example, to specify all versions with a version number that starts with"3.", type 3.* for the version number. To specify all versions with a version that startswith “3.1.”, type 3.1.* for the version number.

6. Choose $GG�GHSHQGHQF\.

�5HPRYLQJ�D�3DFNDJH�'HSHQGHQF\

Use this procedure to remove a package dependency for a package that is no longerneeded.

�7R�UHPRYH�D�SDFNDJH�GHSHQGHQF\�IRU�D�SDFNDJH


2. Select tab page�$OO�3DFNDJHV.

3. Select the name of the package for which you want to remove a package dependency.

4. Follow the (GLW�'HSHQGHQFLHV link in field�3DFNDJH�'HSHQGHQFLHV.

5. Select the package dependency you want to remove from the list on the left.

6. Choose 'HOHWH�GHSHQGHQF\.

� &RS\LQJ�3DFNDJHV�IURP�2QH�6HUYHU�WR�$QRWKHUUse package replication to copy (publish) packages from one SAP Business ConnectorServer to another. If you have a clustered environment, this feature is useful to quicklyreplicate new and updated packages across all servers in the cluster. It is also aconvenient way to distribute a package from one server to another anywhere on the Web.

�2YHUYLHZ�RI�3DFNDJH�5HSOLFDWLRQ

During replication, a single SAP Business Connector Server sends (publishes) a specifiedpackage to one or more recipient servers. The server on which the package originates isreferred to as the publisher, and the recipients are referred to as subscribers.


2YHUYLHZ�RI�3DFNDJH�5HSOLFDWLRQ



3XEOLVKHU

6XEVFULEHU

6XEVFULEHU


6XEVFULEHU

During package replication...

…a publishing server copies one package...

…to one or more subscribing servers.



Subscribing servers receive the package in their inbound directory(sapbc\server\replicate\inbound). To activate the new package, an administrator on thesubscribing server must install the package after it arrives. (This procedure is explained in




,QVWDOOLQJ�D�3DFNDJH�3XEOLVKHG�E\�$QRWKHU�6HUYHU on page 10-22.)

�:KR�&DQ�6XEVFULEH"

Any SAP Business Connector Server can subscribe to a package on another server if bothservers allow it from a security perspective.

The security for package replication involves setting the passwords for the Replicatoruser ID. All servers come predefined with a Replicator user ID. When you replicate apackage, both the publishing server and the subscribing server perform the work using theReplicator user ID. The passwords for the Replicator user ID on both the publishingserver and the subscribing server must be identical to allow package replication betweenthe servers.

The publishing server maintains a list of subscribing servers for each package. There aretwo ways to add subscribers:

g As an administrator of a publishing server, you can use the publisher functions to add(or remove) subscribers to any package that originates on your server (i.e., one towhich you do not subscribe).

g The administrator of a remote SAP Business Connector Server can submit asubscription request to your server. When your server receives this request, itautomatically adds that server to the subscription list for the requested package.Subscribers can also issue cancellation requests (i.e., cancel their subscriptions) forpackages to which they subscribe.

�*XLGHOLQHV�IRU�8VLQJ�3DFNDJH�5HSOLFDWLRQ

Keep the following guidelines in mind when using the package replication facility:

g Publishers and participating subscribers must use SAP Business Connector ServerVersion 2.0 or higher.

g Any SAP Business Connector Server can publish a package.

g Any SAP Business Connector Server can subscribe to a package on another SAPBusiness Connector Server.

g A SAP Business Connector Server can be both a publisher of packages and asubscriber of others; however, it cannot be both a publisher and a subscriber of thesame package.

g The publishing server assumes that a package is uniquely identified by its name. Thismeans that if you publish a package called TimeCard to a server that already has apackage called TimeCard, the server will write the published package in place of theoriginal package on the subscriber’s server. (The server saves the original package incase you need to revert to it). To prevent the publishing server from writing over theincorrect package, you should adopt naming conventions to uniquely identifypackages throughout your network. For example, you might require all publishers toprefix packages with the name of their server. In the TimeCard example above, youcould distinguish the two packages using names such as ENG105TimeCard andMKT01TimeCard.


7KH�3XEOLVKLQJ�6HUYHU


g If you delete the Replicator user account, Replicators group, or Replicators ACL, theserver cannot perform package replication. The SAP Business Connector Serveralways uses the Replicator user ID to perform package replication. The services thatthe server uses to perform package replication are protected by the Replicators ACL.

g You must keep the passwords of the Replicator user IDs identical on both thepublishing server and the subscribing server to allow package replication between thetwo servers.

�7KH�3XEOLVKLQJ�6HUYHU

This section describes the tasks you perform when your server is participating in packagereplication as the publishing server:

7DVN�

Displaying the list of subscribers for a package

Specifying subscribers for a package

Removing subscribers for a package

Publishing a package to subscribing servers

�'LVSOD\LQJ�6XEVFULEHUV

Use this procedure to display the list of subscribers for a specific package on your server.

�7R�GLVSOD\�WKH�VXEVFULEHUV�IRU�D�SDFNDJH



3. Select the name of the package for which you want to view subscribers.

The server lists the subscribers to the package in the 6XEVFULEHUV�field.

�6SHFLI\LQJ�6XEVFULEHUV

When you specify subscribers, you are identifying the SAP Business Connector Serversthat are to receive a package. You can have a different list of subscribers for each packageon your server.

Specify the subscribers (recipients) of the package. (You only need to execute this taskthe first time you publish the package—from then on, you can simply modify or reuse theinitial list.)

�7R�VSHFLI\�VXEVFULEHUV





2. Select tab page 3XEOLVKLQJ.

3. Select the package for which you want to identify subscribers from the drop down listin the 3DFNDJH field.

4. To identify a subscribing server, type its host name and the port number. Usehost:port format, for example, ENG105:5555. If you omit a port number, 5555 isassumed. Then, select $GG�WKLV�VXEVFULEHU� The server adds the subscriber to the listin the 6XEVFULEHUV field.

Repeat this step for each server you want to identify as a subscriber to the package.

&DXWLRQ

The subscribing server must be running at the time you add the subscriber.


7KH�3XEOLVKLQJ�6HUYHU


�5HPRYLQJ�6XEVFULEHUV�IRU�D�3DFNDJH

Use this procedure to remove a subscriber from a package that you publish.

1RWH

This procedure prevents your server from sending (publishing) a package. If yourserver is acting as a subscribing server and you no longer want to receive a package,you must cancel your subscription to the package. For more information, refer to&DQFHOLQJ�D�6XEVFULSWLRQ on page 10-21.

�7R�UHPRYH�VXEVFULEHUV



3. Select the package for which you want to remove subscribers from the drop down listin the 3DFNDJH field.

4. Select the subscriber that you want to remove from the list in the 6XEVFULEHUV field.

5. Choose 'HOHWH�VHOHFWHG�VXEVFULEHUV.

�3XEOLVKLQJ�D�3DFNDJH

Publishing a package to other SAP Business Connector Servers involves two tasks:

g &UHDWLQJ�D�GLVWULEXWLRQ�ILOH� To publish a package, you create a ZIP file that containsthe information for the package.

When you create the ZIP file, you select what information to include in the file. Inmost cases, you should include all files in the package. You must include themanifest.v3 package, or the server will not recognize the ZIP file as a package.

After you indicate the files to include in the ZIP file, the server places all the selectedfiles into a single, compressed file. It places the ZIP file in thesapbc\server\replicate\outbound directory. If the outbound directory already contains aZIP file for this package, the server overwrites the existing file.

g 6HQGLQJ�WKH�GLVWULEXWLRQ�ILOH. After you create the distribution file, you can send it tothe subscribing servers.

The subscribing servers receive the distribution file in their inbound directory(VDSEF\server\replicate\inbound). If a distribution file for the package alreadyexists in a subscribing server’s inbound directory, the server overwrites it. Thedistribution file remains in the inbound directory on the subscribing server until theadministrator of that server installs the package.




1RWH

Before you can publish a package, you must specify the subscribers. For instructions,refer to 6SHFLI\LQJ�6XEVFULEHUV on page 10-17.

�7R�FUHDWH�WKH�GLVWULEXWLRQ�ILOH



3. In the =LS�ILOHV�section of the screen, select (GLW�]LS�ILOH.

The server displays the =LS�ILOH�IRU�3DFNDJH1DPH screen, which lists all the files inthe package.

4. Identify the files that you want to include in the ZIP file.

,I�\RX�ZDQW�WR�LQFOXGH� 'R�WKLV�

$OO�ILOHV�LQ�WKH�=,3�ILOH In the 0HDQLQJ�RI�VHOHFWLRQ section, select,QFOXGH�VHOHFWHG�ILOHV from the drop down list

In the $FWLRQV section, choose 6HOHFW�DOO�

0RVW��EXW�QRW�DOO��RI�WKHILOHV�LQ�WKH�=,3�ILOH

In the )LOHV�LQ�SDFNDJH field, select the filesyou do not want included in the ZIP file

In the 0HDQLQJ�RI�VHOHFWLRQ section, select([FOXGH�VHOHFWHG�ILOHV from the drop down list�

2QO\�D�IHZ�RI�WKH�ILOHV�LQWKH�=,3�ILOH

In the )LOHV�LQ�SDFNDJH field, select the filesyou want included in the ZIP file

In the 0HDQLQJ�RI�VHOHFWLRQ section, select,QFOXGH�VHOHFWHG�ILOHV from the drop down list�

5. Select 0DNH�]LS�ILOH.

�7R�VHQG�WKH�GLVWULEXWLRQ�ILOH



3. Choose 6HQG�]LS�ILOH.


7KH�6XEVFULELQJ�6HUYHU


�7KH�6XEVFULELQJ�6HUYHU

This section describes the tasks you perform when your server is participating in packagereplication as the subscribing server:

7DVN�

Displaying packages to which your server subscribes

Subscribing to a package from another server

Canceling a subscription to a package on another server

Installing a package that was published from another server

�'LVSOD\LQJ�3DFNDJHV�7KDW�<RXU�6HUYHU�6XEVFULEHV�7R

You can view the subscriptions you have to each publishing server.

�7R�GLVSOD\�WKH�SDFNDJHV�WR�ZKLFK�\RXU�VHUYHU�VXEVFULEHV


2. Select tab page 6XEVFULELQJ.

3. In field�3XEOLVKHU, select the publishing server for which you want to viewsubscriptions.

The server displays the lists of package subscriptions you have for the selectedpublishing server in field�6XEVFULSWLRQV.

�6XEVFULELQJ�WR�D�3DFNDJH�IURP�$QRWKHU�6HUYHU

When you subscribe to a package that exists on another server, your server sends asubscription request to the publishing server. The publishing server adds your server tothe subscription list for the package.

To use this procedure, you must have the address of the publishing server and you musthave the exact name of the package to which you want to subscribe. If you do not havethis information, contact the administrator of the publishing server.

1RWH

If you request a subscription to a package that does not exist on the specified server,or if that server does not own the package (i.e., it is a subscriber of the package), youwill receive an error message, and the publishing server does not process yoursubscription.




�7R�VXEVFULEH�WR�D�SDFNDJH�IURP�DQRWKHU�VHUYHU



3. Type the name of the package in the 3DFNDJH field. Be sure to type the name exactlyas it is specified on the publishing server, using the same combination of upper- andlower-case characters.

4. Type the address of the publishing server in the 3XEOLVKHU field. Use host:port format,for example, ENG105:5555. If you omit a port number, 5555 is assumed.

&DXWLRQ

The publishing server must be running at the time you add the subscription.

5. Choose 6XEVFULEH�WR.

�&DQFHOLQJ�D�6XEVFULSWLRQ

When you cancel a subscription, the server sends your cancellation notice to thepublishing server. The publishing server removes your server from the subscription listfor the specified package.

1RWH

This procedure indicates that you no longer want to receive a package from anotherserver. If your server is acting as a publishing server and you want to prevent yourserver from sending a package to a subscriber, you must remove the subscriber. Formore information, refer to


7KH�6XEVFULELQJ�6HUYHU


5HPRYLQJ�6XEVFULEHUV�IRU�D�3DFNDJH on page 10-18.

�7R�FDQFHO�\RXU�VXEVFULSWLRQ�WR�D�SDFNDJH�RQ�DQRWKHU�VHUYHU



3. Select the subscription you want to delete by:

4. Select the publishing server from the 3XEOLVKHU field.

5. Select the subscription from the 6XEVFULSWLRQV field.

6. Choose 'HOHWH�VHOHFWHG�VXEVFULSWLRQ.




�,QVWDOOLQJ�D�3DFNDJH�3XEOLVKHG�E\�$QRWKHU�6HUYHU

When another server publishes a package to your server, you need to install the publishedpackage.

If you install a package that has the same name as an existing package on your server,your server copies the original package to VDSEF?VHUYHU?UHSOLFDWH?VDOYDJH before it installsthe new one. This lets you easily revert to the previous version if you are dissatisfied withthe new package. For information about reverting to the earlier version, refer toRecovering a Package on page 10-13.

You can select whether you want the server to immediately activate the package after itinstalls it. If you do not select to activate the package, the server copies the package to thepackages directory, but it is not available for clients to use. To make this packageavailable for clients, you must manually activate. For more information, refer toActivating a Package on page 10-10.

�7R�LQVWDOO�D�SDFNDJH�WKDW�ZDV�SXEOLVKHG�IURP�DQRWKHU�VHUYHU



3. In the ,QVWDOO�LQERXQG�SDFNDJHV section of the screen, select the package you want toactivate from the 3DFNDJH�QDPH drop down list.

4. If you want to make the package available immediately following installation, checkthe (QDEOH�XSRQ�LQVWDOODWLRQ checkbox in the 2SWLRQ field.

5. Choose ,QVWDOO.

6$3�$* 0DQDJLQJ�6HUYLFHV


&KDSWHU�� 0DQDJLQJ�6HUYLFHV

About Services ....................................................................... 11-2

Fully-Qualified Service Names ............................................... 11-2

Finding Information about Services and Interfaces ................ 11-4

Working with Services ............................................................ 11-6

Running Services When Packages are Loaded/Unloaded... 11-11

Scheduling Services to Execute at Specified Times ............ 11-12

0DQDJLQJ�6HUYLFHV 6$3�$*

$ERXW�6HUYLFHV


� $ERXW�6HUYLFHV

A service is a server-resident unit of functionality that clients can invoke. A service mightbe an entire application or used as part of a larger application. There are several types ofservices—flow services, Java services, C/C++ services, and WIDL services.

You create all flow services using the SAP BC Developer, except for database flowservices, which you can create using the Server Administrator. You can also use the SAPBCDeveloper to create Java services, or use your own development environment to createJava and C/C++ services. Although you cannot use the SAP BC Developer to createWIDL services, the server still executes WIDL services that were created with previousversions of the SAP BC Developer. For more information about the types of services andhow to create them, refer to the 6$3�%&�'HYHORSHU¶V�*XLGH.

Before the server can execute a service, it must be registered to the server. When youcreate a service using the SAP BC Developer, the SAP BC Developer automaticallyregisters the service with the server. Similarly, when a database flow service is createdusing the Server Administrator, the server automatically registers the service. However,when you create services using your own development environment, you need to registerthe services with the server. To register a service, you identify its name, type, andpackage.

You can designate one or more services in a package as a startup service and/or ashutdown service. A startup service is a service that the server automatically executeswhen a package is loaded. A shutdown service is a service that the server automaticallyexecutes when a package is unloaded.

To improve the performance of services, you can have the server cache the serviceresults. Then, when the server receives subsequent requests for the service, it returns thecached results rather than executing the service. For more information, refer to &DFKLQJ6HUYLFH�5HVXOWV on page 12-1.

� )XOO\�4XDOLILHG�6HUYLFH�1DPHV

The fully-qualified service name is comprised of two parts—an interface identifier andthe service name. The interface identifier is comprised of one or more interface names.The service name is a single name of the service.

Use an interface to group related services together. When an interface contains otherinterfaces, the nested interfaces are called subinterfaces. For example, if you have severalservices that involve financial information, you might create an interface named"Finance" to hold the services. Within the financial services, there might be services thatare for personal finances. You might create a subinterface named “Personal” to hold thoseservices.

Use any name for the service name. For example, if one of the financial services obtainsstock quotes, you might name the service, "StockQuote."

To specify a fully-qualified service name, identify the interface portion, then a colon (:),then the service name:

LQWHUIDFH�VHUYLFH


3DFNDJH�1DPHV�DQG�6HUYLFH�1DPHV


For example, if the "StockQuote" service is in the "Finance" interface, the fully-qualifiedservice name is:

Finance:StockQuote

If the interface portion identifies more than one interface, separate each interface namewith a period.

interface.subinterface1.subinterface2:service

For example, if the "HomeLoan" service is in the "Personal" interface, which is containedin the "Finance" interface, the fully-qualified service name is:

Finance.Personal:HomeLoan

The fully-qualified name of each service must be unique within the server. In addition,the fully-qualified name of a service cannot be the same as the fully-qualified name ofany specification or record that resides on the server.

1RWH

The watt.server.illegalNSChars setting in the server.cnf file (which is locatedin the VDSEF/server/config directory) defines the characters that you cannot usewhen naming interfaces and services.

�3DFNDJH�1DPHV�DQG�6HUYLFH�1DPHV

The relationship between the package name and the interface name can cause confusion.The name of the package to which a service belongs has no bearing on the names of theservices and interfaces it contains. Nor does it affect how it is referenced by a clientapplication. For example, if you move a service called "Personnel:GetDeptNames" from apackage called "Admin" to a package called "EmployeeData" you will not affect clientapplications that reference that service—it will still be referenced by the name"Personnel:GetDepNames".

Because the fully-qualified name of each service must be unique within the server, youcannot have two identically named services in two different packages on the same server.


)LQGLQJ�,QIRUPDWLRQ�DERXW�6HUYLFHV�DQG�,QWHUIDFHV


� )LQGLQJ�,QIRUPDWLRQ�DERXW�6HUYLFHV�DQG�,QWHUIDFHVThis section describes how to list the services (and interfaces) on your server and displayinformation about a specific service.

�/LVWLQJ�,QWHUIDFHV�DQG�6HUYLFHV

The ,QWHUIDFH�DQG�6HUYLFHV screens of the Server Administrator list the services that resideon your server and the interfaces with which they are associated.

�7R�OLVW�LQWHUIDFHV�DQG�VHUYLFHV


2. Select tab page 6HUYLFH�/LVW.

The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��723�/(9(/� screen. This screenlists only interfaces.

3. To view the contents of an interface, select the interface name. The server displaysanother�,QWHUIDFHV�DQG�6HUYLFHV�screen. For the selected interface, the server displaysthe subinterfaces followed by the services.

You can continue to select interface names to view subinterfaces and services inselected interfaces.

�'LVSOD\LQJ�,QIRUPDWLRQ�DERXW�D�6HUYLFH

The 6HUYLFH�,QIRUPDWLRQ�IRU�6HUYLFH1DPH screen displays a variety of information about aselected service.

�7R�GLVSOD\�LQIRUPDWLRQ�DERXW�D�VHUYLFH



The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��723�/(9(/� screen.

3. Select the name of the interface that contains the service for which you want todisplay information. The server displays another�,QWHUIDFHV�DQG�6HUYLFHV�screen.Continue to select interface names until you see the service for which you want todisplay information.

4. Select the name of the service for which you want to display information.

The server displays the�6HUYLFH�,QIRUPDWLRQ�IRU�6HUYLFH1DPH screen that contains thefollowing sections:


'LVSOD\LQJ�,QIRUPDWLRQ�DERXW�D�6HUYLFH


6HFWLRQ 'HVFULSWLRQ

*HQHUDO�,QIR Identifies

� The service by the name of the interface inwhich the service is contained and theservice name. (This is not the fully-qualified service name.)

� The name of the package with which theservice is associated.

� The type of service—Flow, Java, C/C++,or WIDL.

� Whether the service is stateless or not.

-DYD�VSHFLILF�LQIR For a Java service, identifies the Java classname and method name for the service.

$FFHVV�&RQWURO Identifies the ACL assigned to the service, ifany. For information about ACLs and services,refer to &RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHVDQG�)LOHV�ZLWK�$&/V on page 8-10.

&DFKH�&RQWURO Identifies whether the server is to save theresults of executing this service in cache. Forinformation, refer to &DFKLQJ�6HUYLFH�5HVXOWVon page 12-1.

'DWD�)RUPDWWLQJ Identifies the name of a binding service thatparses incoming XML for the service, theoutput template associated with the service (ifany), and the type of the output template(HTML or XML). For information aboutoutput templates, refer to the 6$3�%&'HYHORSHU¶V�*XLGH�


:RUNLQJ�ZLWK�6HUYLFHV


� :RUNLQJ�ZLWK�6HUYLFHVYou can perform the following tasks that act on services.

3HUIRUPWKLV�WDVN :KHQ�\RX�ZDQW�WR�

Register a service Register a service to the server.

Unregister a service Make a service unavailable.

Edit ServiceInformation

Update the information for a service, suchas access control information or cachingcontrols.

Manually add aservice to the server

Add a service that you created with yourown development environment.

Test a service Invoke a service and supply input to testhow it works.

Assign an ACL to theservice

Control which users can access a service.

Identify cache controls Improve service performance by cachingthe results of a service invocation.

Identify as a startup orshutdown service

Have the server automatically execute aservice when the package in which it iscontained is loaded (startup service) orunloaded (shutdown service).

�5HJLVWHULQJ�6HUYLFHV

Before a client can use a service, the service must be registered with the server. If theservice was created with the 6$3�%&�Developer or the Server Administrator, serviceregistration occurs automatically.

When services are created in other development environments, you must manuallyregister them with the server. You must also place the code for the service in the correctdirectory on the server. For information about placing service code on the server, refer to0DQXDOO\�$GGLQJ�D�6HUYLFH�WR�WKH�6HUYHU on page 11-9.

�7R�UHJLVWHU�D�VHUYLFH


2. Select tab page 1HZ�6HUYLFH.

3. Set the 6HUYLFH�GHWDLO parameters as follows:


8QUHJLVWHULQJ�6HUYLFHV



6HUYLFH�FODVV The type of service you are registering. Selectthe type from the drop down list.

3DFNDJH The package to which you want to associatethe service. The server lists all packages in thedrop down list. Select one from the drop downlist.

,QWHUIDFH�QDPH The interface to which you want to assign thisservice. Specify the fully-qualified interfacename (include the interface and allsubinterfaces). Separate interface names withperiods (.).

6HUYLFH�QDPH The name you want to assign to this service.

4. Choose 6XEPLW.

�8QUHJLVWHULQJ�6HUYLFHV

Unregister services that you no longer want the server to execute.

1RWH

When you unregister a service, the server does not physically remove the file. Itrenames the file that contains the service to have a .bak extension.

�7R�XQUHJLVWHU�D�VHUYLFH




3. Select the name of the interface that contains the service you want to unregister. Theserver displays another�,QWHUIDFHV�DQG�6HUYLFHV�screen. Continue to select interfacenames until the server displays a screen that lists the service you want to unregister.

4. To unregister the service, choose the icon in the 8QUHJLVWHU column for the service.




�(GLWLQJ�6HUYLFH�,QIRUPDWLRQ

Use this procedure to update information about a service.

�7R�HGLW�VHUYLFH�LQIRUPDWLRQ




3. Select the name of the interface that contains the service for which you want to editinformation. The server displays another�,QWHUIDFHV�DQG�6HUYLFHV�screen. Continue toselect interface names until the server displays a screen that lists the service for whichyou want to edit information.

4. Select the service name of the service for which you want to edit information.

The server displays the�6HUYLFH�,QIRUPDWLRQ�IRU�6HUYLFH1DPH screen.


6. You can update the following field in the General Info section of the screen:


6WDWHOHVV Whether the server should run this service as astateless service.

Select <HV if the service does not have tomaintain state information (information aboutthe user that invoked it) for the service. If youset this option, the service will run faster anduse fewer resources.

Select 1R if the server should maintain stateinformation for the service.

7. If the service is a Java service, you can update the following fields in the -DYD�VSHFLILF�LQIR�section of the screen:


&ODVV�QDPH Class of the Java service

0HWKRG�QDPH Method of the Java service

8. You can update the following field in the $FFHVV�&RQWURO section of the screen:


0DQXDOO\�$GGLQJ�D�6HUYLFH�WR�WKH�6HUYHU



$&/�*URXS The ACL group that you want to assign to thisservice to control which users can invoke theservice. For more information on ACL groupsand assigning them to services, refer to&RQWUROOLQJ�$FFHVV�WR�6$3�%&�6HUYLFHV�DQG)LOHV�ZLWK�$&/V on page 8-10.

9. You can update the fields in the &DFKH�&RQWURO section of the screen. For instructions,refer to 6HWWLQJ�WKH�&DFKLQJ�&RQWUROV�IRU�D�6HUYLFH on page 12-4.

10. You can update the following fields in the 'DWD�)RUPDWWLQJ section of the screen:


%LQGLQJ�1DPH The name of a service that parses incomingHTML for the service. There is no default.

2XWSXW�7HPSODWH The file name of the output template that youwant to associate with this service. For moreinformation about output templates, refer to the6$3�%&�'HYHORSHU¶V�*XLGH.

7HPSODWH�7\SH The type of template. Select either +70/ or;0/.

11. Choose 6XEPLW.

�0DQXDOO\�$GGLQJ�D�6HUYLFH�WR�WKH�6HUYHU

If you have services that were not created using the SAP BC Developer, you mustmanually add them to the server.

�7R�PDQXDOO\�DGG�D�VHUYLFH�WR�WKH�VHUYHU

1. Create the package for the service if it does not already exist. For instructions, refer to&UHDWLQJ�D�3DFNDJH on page 10-10.

2. Copy the source for the services to the following directory:

VDSEF�VHUYHU�SDFNDJHV�3DFNDJH1DPH�FRGH�VRXUFH

where:

3DFNDJH1DPH is the name of the package to which the service belongs.

3. Compile the source code.




4. Move the resulting class(es) to the following directory:

VDSEF�VHUYHU�SDFNDJHV�3DFNDJH1DPH�FRGH�FODVVHV

where:

3DFNDJH1DPH is the name of the package to which the service belongs.

5. Register the new service. For instructions, refer to 5HJLVWHULQJ�6HUYLFHV on page 11-6.

�7HVWLQJ�6HUYLFHV

You can test the operation of a service. This allows you to quickly and easily verify theoperation of a service and test it with special-case input values.

1RWH

The SAP BC Developer offers a more robust environment for testing services.

�7R�WHVW�D�VHUYLFH




3. Select the name of the interface that contains the service you want to test. The serverdisplays another�,QWHUIDFHV�DQG�6HUYLFHV�screen. Continue to select interface namesuntil the server displays a screen that lists the service you want to test.

4. To test the service, choose the icon in the 7HVW column for the service.

The server displays the 7HVW�6HUYLFH1DPH screen.

5. If you want to test the service with input values, fill in the required input informationin the $VVLJQ�LQSXW�YDOXHV section of the screen and choose 7HVW�ZLWK�LQSXWV.

If you want to test the service without specifying input values, choose 7HVW��QRLQSXWV�.


:KDW�LV�D�6WDUWXS�6HUYLFH"


� 5XQQLQJ�6HUYLFHV�:KHQ�3DFNDJHV�DUH�/RDGHG�8QORDGHGTo have the server automatically execute a prescribed set of operations each time theserver loads or unloads a package from memory, identify startup and shutdown services.

�:KDW�LV�D�6WDUWXS�6HUYLFH"

A startup service is one that the server automatically executes when it loads a package.The server loads a package:

g At server initialization (if the package is enabled)

g When someone uses the Server Administrator to reload a package

g When someone uses the Server Administrator to enable a package

Startup services are useful for generating initialization files or assessing and preparing(e.g., setting up or cleaning up) the environment before the server loads a package.However, you can use a startup service for any purpose. For example, you might want toexecute a time-consuming service at startup so that its cached result is immediatelyavailable to client applications.

�:KDW�LV�D�6KXWGRZQ�6HUYLFH"

A shutdown service is one that the server automatically executes when it unloads apackage from memory. If a package is in memory, the server unloads the package:

g At server shutdown or restart

g When someone uses the Server Administrator to disable the package

g Before the server removes the package from memory when someone uses the ServerAdministrator to reload a package

Shutdown services are useful for executing clean-up tasks such as closing files andpurging temporary data. You could also use them to capture work-in-progress or stateinformation before a package unloads.

�*XLGHOLQHV�IRU�8VLQJ�6WDUWXS�6KXWGRZQ�6HUYLFHV

Keep the following guidelines in mind when using startup and shutdown services.

g When you create a startup or shutdown service, you must register that service in thepackage with which it will be used.

g Because services in a package are not made available to clients until that package’sstartup services finish executing, you should avoid implementing startup services thataccess busy remote servers. They will delay the availability of other services in thatpackage.

g You may assign one or more startup services to a package; however, you cannotspecify the order in which they will execute. If you have a series of operations thatmust execute in a specific order, encode the entire sequence within a single service orhave a startup service invoke others.


6FKHGXOLQJ�6HUYLFHV�WR�([HFXWH�DW�6SHFLILHG�7LPHV


�,GHQWLI\LQJ�6WDUWXS�DQG�6KXWGRZQ�6HUYLFHV

Use the following procedure to identify startup and shutdown services.

�7R�LGHQWLI\�VWDUWXS�DQG�VKXWGRZQ�VHUYLFHV



3. Choose the name of the package to which you want to assign startup and shutdownservices.

4. Select 6WDUWXS�VKXWGRZQ�VHUYLFHV.

5. To add startup services, in the 6WDUWXS�VHUYLFHV section of the screen, select a servicefrom the drop down list and choose $GG�WKLV�VHUYLFH. Repeat this step for each serviceyou want to add as a startup service.

6. To add shutdown services, in the 6KXWGRZQ�VHUYLFHV section of the screen, select aservice from the drop down list and choose $GG�WKLV�VHUYLFH. Repeat this step for eachservice you want to add as a shutdown service.

�5HPRYLQJ�6WDUWXS�DQG�6KXWGRZQ�6HUYLFHV

Use the following procedure to remove startup and shutdown services.

�7R�UHPRYH�VWDUWXS�DQG�VKXWGRZQ�VHUYLFHV



3. Select the name of the package for which you want to remove startup and shutdownservices.

4. Choose 6WDUWXS�VKXWGRZQ�VHUYLFHV.

5. To remove startup services, in the 6WDUWXS�VHUYLFHV section of the screen, select thestartup services you want to remove from the list on the left and 'HOHWH�VHOHFWHGVHUYLFHV.

6. To remove shutdown services, in the 6KXWGRZQ�VHUYLFHV�section of the screen, selectthe shutdown services you want to remove from the list on the left and 'HOHWHVHOHFWHG�VHUYLFHV.

� 6FKHGXOLQJ�6HUYLFHV�WR�([HFXWH�DW�6SHFLILHG�7LPHV

Use the server’s scheduling function to schedule services to execute at times you specify.Services that you schedule are referred to as user tasks.

You can view a list of and update the scheduling options for scheduled user tasks. Afterthe server completes all scheduled executions of a service, it removes the user task from


6FKHGXOLQJ�D�8VHU�7DVN


the list. You can also cancel a scheduled user task before the server completes allscheduled executions.

In addition to the scheduled user tasks that you set up, the server schedules system tasksthat it performs for normal system operation. You can view, but not update or cancel, thescheduled system tasks.

�6FKHGXOLQJ�D�8VHU�7DVN

To schedule a user task, you specify:

g )XOO\�TXDOLILHG�VHUYLFH�QDPH��To indicate the service that you want the server toexecute, you specify the fully-qualified name of the service. For information aboutspecifying service names, refer to )XOO\�4XDOLILHG�6HUYLFH�1DPHV on page 11-2.

g 8VHU�QDPH�WKDW�\RX�ZDQW�WKH�VHUYHU�WR�XVH�ZKHQ�UXQQLQJ�WKH�VHUYLFH��The serverruns the service as if the user you specify is the authenticated user that invoked theservice. If the service is governed by an ACL, be sure to specify a user that is allowedto invoke the service.

g :KHWKHU�\RX�ZDQW�WKH�VFKHGXOHG�XVHU�WDVN�WR�SHUVLVW�DIWHU�D�UHVWDUW�RI�WKH�VHUYHU�Select this option if you want the server to maintain the scheduled user task in theevent that the server is restarted before it completes all scheduled executions. Whenthe server is restarted, it will continue to execute the service at the scheduled time(s).If you do not select this option, the user task is removed from the system at servershutdown and the server no longer executes the user task when the server is restarted.

g :KHQ�DQG�KRZ�RIWHQ�\RX�ZDQW�WKH�VHUYLFH�WR�UXQ�

� 2QFH� The server executes the service a single time.

� 5HSHDWLQJ� The server executes the service repeatedly at an interval you specify.

� &RPSOH[� The server runs the service on the day(s) and at the time(s) that youspecify either during a specified date range or indefinitely.

� 8VLQJ�WKH�2QFH�2SWLRQ

When you schedule a user task using the 2QFH option, the server executes the service onetime on the date and at the time that you specify. After the server executes the service atthe scheduled time, it removes the user task from the list of scheduled user tasks.

If you indicate that you do not want the user task to persist after a restart and the server isrestarted before the scheduled execute time, the server will not execute the service.

� 8VLQJ�WKH�5HSHDWLQJ�2SWLRQ

When you schedule a user task using the 5HSHDWLQJ option, the server executes the servicefor the first time immediately after you add the user task. The server continues to executethe service at the interval you specify. You specify the interval in seconds. For example,if you want the server to execute the service every 24 hours, specify 86400 seconds forthe interval.




There is no end date or time associated with a repeating user task. The server continues toexecute the service until you cancel the scheduled user task, or if the user task does notpersist after restart, until the server is restarted.

� 8VLQJ�WKH�&RPSOH[�2SWLRQ

The &RPSOH[ option offers the greatest flexibility for specifying when you want theserver to execute the service.

Specify any combination of the following settings to indicate when and how often youwant the server to execute the service:

6HWWLQJ ,QGLFDWHV«

6WDUW�7LPH(QG�7LPH

The time period for the server to run the service. If you do notspecify a 6WDUW�7LPH�and (QG�7LPH� the time period is indefinite; itstarts immediately after you schedule the user task and has no end.

0RQWKV The months that you want the server to execute the service.

0RQWK�'D\V The days of the months (0 through 31) that you want the server toexecute the service.

:HHN�'D\V The days of the week (Sunday through Saturday) that you want theserver to execute the service.

+RXUV The hours of the days that you want the server to execute theservice.

0LQXWHV The minute of the hour that you want the server to execute theservice.

The server combines all your selections to determine when to execute the service. If youdo not select an item in one of the above settings, the server assumes all items for theselection. For example, if you do not specify a month, the server assumes you want theservice to execute every month. If you do not select any items for any of the settings, theserver assumes you want the service to execute every month, every day, all week days,every hour, and every minute; in other words, the server executes the service everyminute from the time you add the task.

If you use the 6WDUW�7LPH�and (QG�7LPH to specify a date range, the server executes theservice at the scheduled times until the end of the time period. At the end of the timeperiod, the server removes the user task from the list of scheduled user tasks. If youindicate that you do not want the user task to persist after a restart, the server will notcontinue to execute the service if the server is restarted before the schedule time periodelapses.

If you do not use the 6WDUW�7LPH�and (QG�7LPH to specify a date range, the server executesthe service for an indefinite period of time. The scheduled user task remains in the systemuntil you cancel the scheduled user task, or if the user task does not persist after restart,until the server is restarted.




The following shows examples of how to use the Complex option settings:

,I�\RX�ZDQW�WKH�VHUYLFH�WR�H[HFXWH« )RU�WKLV�VHWWLQJ� 6SHFLI\«

Start Time 2000/01/01

End Time 2000/12/31

Months no selection

Month Days 28

Week Days no selection

Hours 0

The 28th day of every month atmidnight for the year 2000.

Minutes 0

Start Time leave blank

End Time leave blank

Months January, February,March

Month Days no selection

Week Days Monday

Hours 14

Every Monday in the months ofJanuary, February, and March at 2:30p.m. for an indefinite period of time.

Minutes 30


End Time 2000/06/30

Months June


Week Days Tuesday

Hours no selection

Every hour of every Tuesday of themonth of June, 2000.

Minutes 0

Every minute of every hour of everyTuesday of the month of June, 2000.





,I�\RX�ZDQW�WKH�VHUYLFH�WR�H[HFXWH« )RU�WKLV�VHWWLQJ� 6SHFLI\«

End Time 2000/06/30

Months June


Week Days Tuesday

Hours no selection

Minutes no selection

�7R�VFKHGXOH�WKH�H[HFXWLRQ�RI�D�VHUYLFH

1. Select 6FKHGXOHU on the navigation panel.

2. Select tab page 8VHU�7DVNV.

3. Select Schedule New Task.

4. Set the Execute parameters as follows:


6HUYLFH The fully-qualified service name of the serviceyou want the server to execute.

5XQ�DV�8VHU The user name you want the server to use whenrunning the service.

3HUVLVW�DIWHU�UHVWDUW Whether you want the server to maintain thisuser task in the event that the server isrestarted. Check the 3HUVLVW�DIWHU�UHVWDUWcheckbox if you want the server to execute theservice at the scheduled time(s) when theserver is restarted.

5. Select 2QFH��5HSHDWLQJ, or &RPSOH[ to indicate when and how often you want theserver to execute the service.




,I�\RX�VHOHFW« 6SHFLI\«

2QFH � The date on which you want the server toexecute the service in the 'DWH field. Use theformat YYYY/MM/DD to specify the date.For example, if you want the server to executethe service on March 11, 2000, specify2000/03/11.

� The time at which you want the server toexecute the service in the 7LPH field. Use theformat HH:MM:SS to specify the time (usinga 24-hour clock). For example, if you want theserver to execute the service at 1:00:00 a.m.,specify 1:00:00; if you want the server toexecute the service at 1:00:00 p.m., specify13:00:00.

For more information about using this option,refer to 8VLQJ�WKH�2QFH�2SWLRQ on page 11-13.

5HSHDWLQJ � The number of seconds that you want theserver to wait between executions of theservice in the ,QWHUYDO field. For moreinformation about using this option, refer to8VLQJ�WKH�5HSHDWLQJ�2SWLRQ on page 11-13.

&RPSOH[ � The 5XQ�0DVN�parameters to indicate whenyou want the server to execute the service. Forexamples of setting these parameters, refer to8VLQJ�WKH�&RPSOH[�2SWLRQ on page 11-14.

� The beginning date in the 6WDUW�7LPH field andending dates in the (QG�7LPH field to indicatethe time period that you want the server toexecute the service. Use the formatYYYY/MM/DD to specify the date. Forexample, if you want the server to execute theservice on May 3, 2000, specify 2000/05/03.

Leave these fields blank if you want the serverto execute the service for an indefinite periodof time.

For more information about using this option,refer to 8VLQJ�WKH�&RPSOH[�2SWLRQ on page 11-14.

6. Choose $GG�7DVN.

7. The server displays a screen to confirm you want to add the new task. Choose 2..




�9LHZLQJ��6FKHGXOHG�8VHU�7DVNV

Perform the following procedure to view the user tasks you have scheduled.

�7R�YLHZ�VFKHGXOHG�XVHU�WDVNV



�8SGDWLQJ�6FKHGXOHG�8VHU�7DVNV

Perform the following procedure to change the parameters for scheduled user tasks.

�7R�XSGDWH�D�VFKHGXOHG�XVHU�WDVN



3. Select the service name for the user task you want to update.

4. Update the scheduling options for the selected user task. For information about theoptions you can specify, refer to 6FKHGXOLQJ�D�8VHU�7DVN on page 11-13.

5. Choose 8SGDWH�7DVN.

6. The server displays a screen to confirm you want to update the user task. Choose 2..

�&DQFHOLQJ�6FKHGXOHG�8VHU�7DVNV

Perform the following procedure to cancel a user task before all scheduled executions ofthe service are complete.

�7R�FDQFHO�D�VFKHGXOHG�XVHU�WDVN



3. Choose the icon in the &DQFHO column for the user task you want to cancel. Theserver issues a prompt to verify that you want to cancel the user task. Choose 2..

�9LHZLQJ�WKH�6FKHGXOHG�6\VWHP�7DVNV

The server needs to perform system tasks periodically, such as expiring sessions orrecycling the log. The server schedules these tasks. Perform the following procedure toview the scheduled system tasks.

�7R�YLHZ�WKH�VFKHGXOHG�V\VWHP�WDVNV


2. Select tab page 6\VWHP�7DVNV.The server displays the 6\VWHP�7DVNV screen. It lists the names of each scheduled task,the next date and time the server is to execute the task, and the how often (,QWHUYDO)the server is to execute the task.

6$3�$* &DFKLQJ�6HUYLFH�5HVXOWV


&KDSWHU�� &DFKLQJ�6HUYLFH�5HVXOWV

What is Caching? ................................................................... 12-2

Types of Services to Cache ................................................... 12-2

Controlling How the Server Uses Caching ............................. 12-3

Setting the Caching Controls for a Service ............................ 12-4

Resetting the Cache............................................................... 12-5

Viewing Service Statistics ...................................................... 12-6

&DFKLQJ�6HUYLFH�5HVXOWV 6$3�$*

:KDW�LV�&DFKLQJ"


� :KDW�LV�&DFKLQJ"

Caching is an optimization feature that can improve the performance of stateless services.A stateless service is one for which the server does not maintain information about theclients that invoke the service.

You indicate the services for which you want to use cache. When you enable caching fora service, the server saves the results from invoking the service in a local cache for theperiod of time that you specify. When the server receives subsequent requests for aservice with the VDPH�VHW�RI�LQSXW�YDOXHV, it returns the cached result to the client ratherthan invoking the service again.

Caching can significantly improve response time of services. For example, services thatretrieve information from busy data sources such as high-traffic commercial Web serverscould benefit from caching. The server can cache the results for all types of SAPBCservices—flows, Java services, and C/C++ services.

The goal for caching is to strike the right balance between data currency and memoryusage. To gauge the effectiveness of your cache, you can monitor its performance byviewing service statistics from the Server Administrator and adjust your caching valuesaccordingly.

� 7\SHV�RI�6HUYLFHV�WR�&DFKH

While caching service results can improve performance, not all services should becached. You should never cache services if the cached results might be incorrect forsubsequent invocations or if the service performs tasks that must be executed each timethe service is invoked.

This section describes guidelines for you to consider when determining whether to cachethe results for a service.

�6HUYLFHV�6XLWHG�IRU�&DFKLQJ

g 6HUYLFHV�WKDW�UHTXLUH�QR�VWDWH�LQIRUPDWLRQ� If a service does not depend on stateinformation from an earlier transaction in the client’s session, you can cache itsresults.

g 6HUYLFHV�WKDW�UHWULHYH�GDWD�IURP�GDWD�VRXUFHV�WKDW�DUH�XSGDWHG�LQIUHTXHQWO\�Services whose sources are updated on a daily, weekly, or monthly basis are goodcandidates for caching.

g 6HUYLFHV�WKDW�DUH�LQYRNHG�IUHTXHQWO\�ZLWK�WKH�VDPH�VHW�RI�LQSXWV� If a service isfrequently invoked by clients that identify the same input information, it is beneficialto cache the results.


6HUYLFHV�<RX�6KRXOG�1RW�&DFKH


�6HUYLFHV�<RX�6KRXOG�1RW�&DFKH

g 6HUYLFHV�WKDW�SHUIRUP�UHTXLUHG�SURFHVVLQJ� Some services contain processing thatmust be processed each time a client invokes it. For example, if a service containsaccounting logic to perform charge back and you cache the service results, the serverdoes not execute the service, so the service does not perform charge back for thesubsequent invocations of the service.

g 6HUYLFHV�WKDW�UHTXLUH�VWDWH�LQIRUPDWLRQ� Do not cache services that require stateinformation from an earlier transaction, particularly information that identifies theclient that invoked it. For example, you do not want to cache a service that produceda price list for office equipment if the prices in the list vary depending on the clientwho initially connects to the data source.

g 6HUYLFHV�WKDW�UHWULHYH�LQIRUPDWLRQ�IURP�IUHTXHQWO\�XSGDWHG�VRXUFHV� If a serviceretrieves data from a data source that is updated frequently, the cached results canbecome outdated. Do not cache services that retrieve information from sources thatare updated in real-time or near real-time, such as stock quote systems ortransactional databases.

g 6HUYLFHV�WKDW�DUH�LQYRNHG�ZLWK�XQLTXH�LQSXWV� If a service handles a large numberof unique inputs and very few repeated requests, you will gain little by caching itsresults. You might even degrade server performance by quickly consuming largeamounts of memory.

� &RQWUROOLQJ�+RZ�WKH�6HUYHU�8VHV�&DFKLQJ

You enable caching on a per-service basis. When you enable caching for a service, youmust also identify several settings that indicate how the server manages the cache:

g &DFKH�([SLUDWLRQ��This indicates how many minutes the server should keep theservice results in the cache. The expiration timer begins when the server initiallycaches a result, and it expires when the time you specify elapses. The server does notreset the expiration timer each time it satisfies a service request with a cached result.

g 3UHIHWFK� You indicate whether you want the server to prefetch the service resultswhen the results in the cache expire. To prefetch the service results, the server re-executes the service.

You can use caching with or without Prefetch:

� With Prefetch, you instruct the server to automatically refresh the cache when itexpires. As a result, the server can service all subsequent clients with cachedresults.

� Without Prefetch, the server releases the cached results for a service when thecache timer expires. The server only caches the results again when another clientrequests the service. The client that causes the results to be re-cached bears theperformance penalty of requesting a non-cached service.


6HWWLQJ�WKH�&DFKLQJ�&RQWUROV�IRU�D�6HUYLFH


&DXWLRQ

Use Prefetch carefully. Overuse can quickly exhaust the memory available for cache.

'R�QRW�use Prefetch with Java or C/C++ services that invoke access-controlled SAPBCservices. Such services will fail during prefetch because the embedded service willbe invoked without the proper access privileges. As an alternative, enable caching“with prefetch” on the embedded services rather than on the Java or C/C++ servicesthat call them.

g 3UHIHWFK�$FWLYDWH� If you indicate that you want the server to prefetch the serviceresults, you must also use this setting to indicate when the server should activate theuse of prefetch. This setting specifies the minimum number of times a cached resultmust be accessed before the server will automatically prefetch the service resultswhen the cache timer expires.

If a cached result receives at least the number of hits that you specify by the time thecache expires, the server performs the prefetch. That is, it automatically re-executesthe services using the same set of inputs and re-caches the results. If a cached resultdoes not receive the minimum number of hits that you specify before the cacheexpires, the server does not perform the prefetch; instead, it releases the cachedresults.

� 6HWWLQJ�WKH�&DFKLQJ�&RQWUROV�IRU�D�6HUYLFH

You can indicate that you want the server to cache the results from a service and how tomanage the cache for that service using WKH�6HUYLFH�,QIRUPDWLRQ�IRU�6HUYLFH1DPH screenof the Server Administrator.

�7R�VHW�WKH�FDFKH�FRQWUROV�IRU�D�VHUYLFH



3. Select the name of the interface for the service. The next level of the ,QWHUIDFHV�DQG6HUYLFHV�screen displays. Continue selecting the interface names until the serverdisplays a screen listing the service for which you want to set cache controls.

4. Select the name of the service for which you want to set cache controls.


6. Set the &DFKH�&RQWURO parameters as follows:


6HUYLFHV�<RX�6KRXOG�1RW�&DFKH


)RU�WKLVSDUDPHWHU

6SHFLI\«

&DFKLQJ 2Q to turn caching on; select the 2Q radio button.

&DFKH�([SLUDWLRQ Type the number of minutes that you want theserver to keep the service results in cache.

3UHIHWFK 2Q if you want the server to use Prefetch;2II if you do not want the server to use Prefetch.

3UHIHWFK�$FWLYDWH The minimum number of hits to the cached resultsto activate the use of Prefetch. The server only usesthis value if Prefetch is on.

7. Choose 6XEPLW.

� 5HVHWWLQJ�WKH�&DFKH

You can reset the cache for all services or you can reset the cache for a specific service.When the server resets the cache, it removes all cached service results from memory.

�7R�UHVHW�WKH�FDFKH�IRU�DOO�VHUYLFHV



3. In the 6HUYHU�&DFKH section of the screen, select the 5HVHW link in the 5HVHW�&DFKHfield.

�7R�UHVHW�WKH�FDFKH�IRU�D�VSHFLILF�VHUYLFH



3. Select the name of the interface for the service. The next level of the ,QWHUIDFHV�DQG6HUYLFHV screen displays. Continue selecting the interface names until the serverdisplays a screen listing the service for which you want to reset the cache.

4. Select the name of the service for which you want to reset the cache.

In the &DFKH�&RQWURO section of the screen, follow the 5HVHW link in the 5HVHW�&DFKH field.


9LHZLQJ�6HUYLFH�6WDWLVWLFV


� 9LHZLQJ�6HUYLFH�6WDWLVWLFV

Use the following procedure to monitor the performance of your cache.

�7R�PRQLWRU�WKH�SHUIRUPDQFH�RI�\RXU�FDFKH

1. Select 6WDWLVWLFV on the navigation panel.

2. Select tab page 6HUYLFH�6WDWV.

The $FWLYH�6HUYLFH�6WDWLVWLFV screen displays the current results of your cache controlsettings for each cache-controlled service.

6$3�$* &RQILJXULQJ�$FFHVV�WR�'DWDEDVH�6\VWHPV


&KDSWHU�� &RQILJXULQJ�$FFHVV�WR�'DWDEDVH�6\VWHPV

Database Connection Information.......................................... 13-2

Pre-Loading JDBC Drivers at Server Initialization.................. 13-2

Making the Java Classes for JDBC Drivers Accessible ......... 13-3

Identifying Database Aliases .................................................. 13-3

Updating Information for Database Aliases............................ 13-5

Deleting Database Aliases ..................................................... 13-5

&RQILJXULQJ�$FFHVV�WR�'DWDEDVH�6\VWHPV 6$3�$*

'DWDEDVH�&RQQHFWLRQ�,QIRUPDWLRQ


� 'DWDEDVH�&RQQHFWLRQ�,QIRUPDWLRQ

The server requires information about databases so it can connect to them. You specifydatabase connection information by configuring database aliases. You must configuredatabase aliases if you want to create database flow services using the ServerAdministrator.

The following lists the information you specify for a database alias:

g 7KH�W\SH�RI�GDWDEDVH�DQG�ZKHUH�LW�LV�ORFDWHG� You identify this information by specifyingthe URL for the database. For information about constructing the URL for thedatabase, refer to JDBC documentation and the documentation for your JDBC driver.

g 7KH�XVHU�QDPH�DQG�SDVVZRUG�UHTXLUHG�WR�FRQQHFW�WR�WKH�GDWDEDVH� If the database requires auser name and password to connect to it, you must supply the server with the username and password it should supply.

g 7KH�-'%&�GULYHU� You identify the name of the Java class for the JDBC driver.

The server uses the database connection information to connect to a database when:

g You use the Server Administrator to display information about database tables whencreating a database service (Generate from table). The server must connect to thedatabase to get information about the structure of the database.

g The server executes a database service that was created using the ServerAdministrator.

1RWH

For information about creating services that access database, refer to the 6$3�%&'HYHORSHUV�*XLGH�

�3UH�/RDGLQJ�-'%&�'ULYHUV�DW�6HUYHU�,QLWLDOL]DWLRQ

You can have the server preload the JDBC drivers when it initializes. When the JDBCdrivers are loaded at initialization, it increases the performance of the first run of the firstdatabase service that requires a specific JDBC driver. If the server does not have a JDBCdriver loaded when a database service requires it, the server must load the JDBC driverwhen the database server executes. Also, if you preload JDBC drivers, the server displaysthe list of drivers in a drop down list on the screens that require a JDBC driver name.When the drop down list is available, you can select a driver from it rather than typing inthe name of a driver.

To have the server load JDBC drivers when it initializes, specify a comma delimited listof JDBC drivers that you want preloaded in the watt.server.jdbc.driverList field inthe server.cnf file. If this field does not exist in the server.cnf file, you can add it.The server.cnf file is located in the VDSEF/server/config directory.


0DNLQJ�WKH�-DYD�&ODVVHV�IRU�-'%&�'ULYHUV�$FFHVVLEOH


�0DNLQJ�WKH�-DYD�&ODVVHV�IRU�-'%&�'ULYHUV�$FFHVVLEOH

The server requires access to the Java classes for each JDBC driver that it is to use. Youneed to place the Java classes in a location that the server can access. Typically, you placethe Java classes in the server’s classpath.

To place the classes in the server’s classpath, unzip or unjar them in theVDSEF/server/lib/classes directory. If the classes subdirectory does not exist, createit.

&DXWLRQ

If you are using an ODBC data source on a Windows platform to connect to yourdatabase, you should not have to make changes to the server’s classpath. Both SunJDK and Microsoft’s Jview include bundled JDBC-ODBC bridge drivers. For Sun,the driver is called sun.jdbc.odbc.JdbcOdbcDriver. For Microsoft, the driver iscalled com.ms.jdbc.odbc.JdbcOdbcDriver.

If the server does not have access to the Java classes for the JDBC driver, users receivethe following error when the server attempts to connect to the database:

Couldn’t make connection: No suitable driver

� ,GHQWLI\LQJ�'DWDEDVH�$OLDVHV

Identify a database alias to specify the connection information that the server must supplyto connect to a database. Set up aliases if:

g You want developers to be able to define database flow services using the ServerAdministrator user interface.

g You want to maintain all database connection parameters in one place to allow foreasier maintenance. For example, you can easily update the information if a passwordchanges or a database moves.

�7R�LGHQWLI\�D�GDWDEDVH�DOLDV

1. Select 'DWDEDVH on the navigation panel.

2. Select tab page�$OLDV�0DQDJHPHQW.

3. Choose $GG. The server displays the 1HZ�'%�$OLDV screen.

4. Set the 'HWDLOV parameters as follows:


,GHQWLI\LQJ�'DWDEDVH�$OLDVHV



$OLDV The alias name that you want to use for thedatabase. You can give the database any alias nameyou want. There is no restriction on the charactersyou can specify for or a limit to the length of thealias name.

'%�85/ The URL for the database, for example,jdbc:odbc:Support.

'%�8VHUQDPH The user name that the server must supply to loginto the specified database. If a user name andpassword are not required, leave this field blank.

'%�3DVVZRUG The password that the server must supply to log intothe selected database. If a user name and passwordare not required, leave this field blank.

'%�'ULYHU The name of the Java class for the JDBC driver.

If the server has any drivers currently loaded, theserver displays a /RDGHG�'ULYHUV field that has adrop down list containing the drivers that areloaded. If you select a driver from the list, the serverplaces the driver name in the�'%�'ULYHU field.

If you do not specify a driver, the server uses thedefault driver specified in thewatt.server.jdbc.defaultDriver parameter inthe server.cnf file. If the server.cnf file does notcontain the watt.server.jdbc.defaultDriverfield, the server uses the Sun JDBC-ODBC bridge.

&DXWLRQ

Be sure the server has access to the Java classes for the driver. For more informationmaking the Java classes available, refer to 0DNLQJ�WKH�-DYD�&ODVVHV�IRU�-'%&�'ULYHUV$FFHVVLEOH on page 13-3.

If you are using one of the following JDBC-ODBC bridges on a Windows platform,the server has access to the Java classes for the driver:

If you are using Sun’s JVM, the driver name is sun.jdbc.odbc.JdbcOdbcDriver.

If you are using Microsoft’s Jview, the driver name iscom.ms.jdbc.odbc.JdbcOdbcDriver.

5. Choose 6XEPLW.


0DNLQJ�WKH�-DYD�&ODVVHV�IRU�-'%&�'ULYHUV�$FFHVVLEOH


� 8SGDWLQJ�,QIRUPDWLRQ�IRU�'DWDEDVH�$OLDVHV

If the connection information changes for a database, update the database aliasinformation to identify the new connection information.

�7R�XSGDWH�LQIRUPDWLRQ�IRU�D�GDWDEDVH�DOLDV


2. Select tab page $OLDV�0DQDJHPHQW.

3. Select the database alias for the database you want to update from &XUUHQW�'DWD6RXUFHV.

4. Choose (GLW. The server displays the (GLW�$OLDV�,QIRUPDWLRQ screen.

5. Set the 'HWDLOV parameters. For information about what to specify for each of thefields, refer to the procedure in ,GHQWLI\LQJ�'DWDEDVH�$OLDVHV on page 13-3.

6. Choose 6XEPLW.

� 'HOHWLQJ�'DWDEDVH�$OLDVHV

When you no longer need access to a database, you can delete the database alias for thedatabase.

�7R�GHOHWH�D�GDWDEDVH�DOLDV


2. Select tab page $OLDV�0DQDJHPHQW.

3. Select the database alias for the database you want to delete from &XUUHQW�'DWD6RXUFHV.

4. Choose 'HOHWH. The server issues a prompt to verify that you want to delete thedatabase alias. Select 2. to delete the database alias.


'HOHWLQJ�'DWDEDVH�$OLDVHV


6$3�$* &RQILJXULQJ�*XDUDQWHHG�'HOLYHU\


&KDSWHU�� &RQILJXULQJ�*XDUDQWHHG�'HOLYHU\

About Guaranteed Delivery .................................................... 14-2

Configuring the Server for Guaranteed Delivery .................... 14-3

Administering Guaranteed Delivery........................................ 14-7

Shutting Down Guaranteed Delivery ...................................... 14-7

Reinitializing Guaranteed Delivery ......................................... 14-7

Testing Guaranteed Delivery.................................................. 14-9

Specifying an E-Mail Address for Error Messages ............... 14-10

&RQILJXULQJ�*XDUDQWHHG�'HOLYHU\ 6$3�$*

$ERXW�*XDUDQWHHG�'HOLYHU\


� $ERXW�*XDUDQWHHG�'HOLYHU\

Use the guaranteed delivery capabilities of the SAP Business Connector Server to ensureguaranteed one-time execution of SAP BC services.

The SAP BC guaranteed delivery capabilities ensure the following occur despitetransient failures:

g Requests to execute services from clients are delivered to the server

g Services are executed once, and only once

g Responses from the execution of the services are delivered to the client

The SAP BC guaranteed delivery capabilities protect against transient failures that mightoccur on the network, in the client, or on the server. A transient failure is a failure that cancorrect itself during a specified period of time. If a request cannot be delivered to theserver due to a transient failure, the request is resubmitted; if the problem has correcteditself, the request is successfully delivered on a subsequent attempt. You determine whatconstitutes a transient error by specifying a time-to-live (TTL) period for a guaranteeddelivery transaction and, optionally, the number of times a transaction should be retried.

Because a SAP Business Connector Server can act as either a server or a client in aguaranteed delivery transaction, the guaranteed delivery capabilities of the server handleboth inbound transactions and outbound transactions. When a client invokes a service ona server, the server is acting as a server. If a service uses guaranteed delivery to invoke aservice on another SAP Business Connector Server, the server that invokes the service isthe client.

6$3�%XVLQHVV

&RQQHFWRU�6HUYHU

6HUYLFH�$

6$3�%XVLQHVV

&RQQHFWRU�6HUYHU

6HUYLFH�%&OLHQW$SSOLFDWLRQ

Inboundtransactionsfrom a clientapplication

Acts as a server.For inbound transactions, acts as a server.For outbound transactions, acts as a client.

Acts as a client.

Outboundtransactionsto anotherserver

The guaranteed delivery capabilities allow you to build robust, transaction-based clientapplications without having to embed complex error handling code to respond to transientfailures.

&DXWLRQ

Use the guaranteed delivery capabilities with stateless (i.e., atomic) transactionsbecause state information cannot be maintained from one request to the next. As aresult, guaranteed delivery capabilities cannot be used with multi-requestconversational services.


6HWWLQJV�6KDUHG�E\�%RWK�,QERXQG�DQG�2XWERXQG�7UDQVDFWLRQV


� &RQILJXULQJ�WKH�6HUYHU�IRU�*XDUDQWHHG�'HOLYHU\

This section describes configuration settings that the SAP Business Connector Serveruses for guaranteed delivery transactions. Most of the settings have defaults. In general,you will want to use the defaults; however, you can specify alternate settings in theserver.cnf server configuration file.

There are settings for both inbound and outbound guaranteed delivery transactions.

�6HWWLQJV�6KDUHG�E\�%RWK�,QERXQG�DQG�2XWERXQG�7UDQVDFWLRQV

ZDWW�VHUYHU�W[0DLOUse the watt.server.txMail setting to specify the e-mail address of an administrator tonotify when guaranteed delivery capabilities are disabled due to error (for example, if theserver encounters a disk full condition). An example of using this setting:

([DPSOH

[email protected].

When an administrator receives an e-mail notification of an error, the administratorshould correct the problem, then use the Server Administrator to reinitialize guaranteeddelivery capabilities. For instructions on how to reinitialize guaranteed delivery, refer to5HLQLWLDOL]LQJ�*XDUDQWHHG�'HOLYHU\ on page 14-7.

There is no default for this setting.

�6HWWLQJV�IRU�,QERXQG�7UDQVDFWLRQV

For inbound transactions, the server maintains a MRE�VWRUH of transactions and the status ofeach. Periodically, the server VZHHSV the job store to remove expired transactions; that is,to remove transactions that have an elapsed time-to-live (TTL) period. For inboundrequests, the client must specify the TTL for a transaction.

In addition to the job store, the server maintains an audit-trail log of all operations itperforms for inbound transactions.

The following describes the inbound transaction settings you can configure.

<RX�FDQ�FRQILJXUH� 8VLQJ�WKLV�VHWWLQJ�LQ�VHUYHU�FQI

Where the server maintains the job store watt.server.tx.jobdir

How often the server sweeps the job storeto remove expired transactions

watt.server.tx.sweepTime


&RQILJXULQJ�WKH�6HUYHU�IRU�*XDUDQWHHG�'HOLYHU\



How the server updates the status ofPENDING transactions when a heuristicfailure occurs

watt.server.tx.heuristicFailRetry

Where the server maintains the audit-traillog

watt.server.tx.logfile

ZDWW�VHUYHU�W[�MREGLUUse the watt.server.tx.jobdir setting to specify the directory in which the servermaintains the job store for inbound transactions. The server registers each guaranteeddelivery transaction it receives in the job store. It uses the job store to manage guaranteeddelivery inbound transactions.

The default is: logs/jobsin

ZDWW�VHUYHU�W[�VZHHS7LPHUse the watt.server.tx.sweepTime setting to specify the number of seconds betweensweeps (clean up) of the job store of inbound transactions. The server sweeps the jobstore to remove expired transactions.

The default is: 60 seconds

ZDWW�VHUYHU�W[�KHXULVWLF)DLO5HWU\Use the watt.server.tx.heuristicFailRetry setting to indicate whether the server isto re-execute services for transactions in the job store that are PENDING when the serveris restarted after a failure. If a transaction is PENDING, the service began but did notcomplete execution when the server failed.

Because the server cannot determine the exact status of a service request, the serverconsiders the guaranteed transaction to have encountered a heuristic failure. You canconfigure the server to respond to heuristic failures as appropriate. The defaultwatt.tx.heuristicFailRetry setting causes the server to execute a service at least onetime at the risk of re-executing it a subsequent time after a heuristic failure. Alternatively,you can reconfigure the setting to guarantee that a service is executed at most one time atthe risk of not executing a service due to a heuristic failure.

If the watt.tx.heuristicFailRetry setting is true, the server resets the transactionstatus from PENDING to NEW, and the server will retry the service. When the setting istrue, a request to execute a service can only fail if the transaction expires before theserver executes the service. (The client specifies the settings that indicate when atransaction expires.)

If the watt.tx.heuristicFailRetry setting is false, the server resets the transactionstatus from PENDING to FAIL to indicate the heuristic failure; the server does not retrythe service. When the setting is false, a request to execute a service can fail due to aheuristic failure or due to the transaction expiring.

The default is: true


6HWWLQJV�IRU�2XWERXQG�7UDQVDFWLRQV


ZDWW�VHUYHU�W[�ORJILOHUse the watt.server.tx.logfile setting to specify the file in which the servermaintains an audit-trail log of all operations it processes for inbound guaranteed deliverytransaction.

The default is: logs/txin.log

�6HWWLQJV�IRU�2XWERXQG�7UDQVDFWLRQV

You can disable the use of guaranteed delivery for outbound transactions. However, ifyou allow guaranteed delivery for outbound transactions, the server maintains a separatejob store for the transactions. Similar to the inbound job store, the server keeps the statusof each transaction in the outbound job store. If a service request fails, the server waits aspecified amount of time before resubmitting the request. The server periodicallyprocesses the job store to identify transactions that it needs to submit.

The server maintains a thread pool to service pending outbound requests. You canconfigure how many client threads the server should maintain in the thread pool.

The server also maintains a separate audit-trail log of all operations it performs foroutbound transactions.

The following describes the settings you can configure.


Whether you want to disable guaranteeddelivery for outbound transactions.

watt.tx.disabled

Where the server maintains the job store. watt.tx.jobdir

The default TTL value for outboundtransactions.

watt.tx.defaultTTLMins

How long the server should wait beforeresubmitting failed requests.

watt.tx.retryBackoff

How often the server processes the job storeto identify transactions that it needs tosubmit.

watt.tx.sweepTime

How many client threads the server shouldmaintain in the thread pool that it uses toservice pending requests.

watt.tx.jobThreads

Where the server maintains the audit-traillog.

watt.tx.logfile


&RQILJXULQJ�WKH�6HUYHU�IRU�*XDUDQWHHG�'HOLYHU\


ZDWW�W[�GLVDEOHGUse the watt.tx.disabled setting to specify that you want to disable the use ofguaranteed delivery for outbound requests. By default, the server allows the use ofguaranteed delivery for outbound transactions.

The default is: false

ZDWW�W[�MREGLUUse the watt.tx.jobdir setting to specify the directory in which the server maintains ajob store of outbound transactions. The server registers each guaranteed deliverytransaction it requests in the job store. It uses the job store to manage outboundguaranteed delivery transactions.

The default is: logs/jobsout

ZDWW�W[�GHIDXOW77/0LQVUse the watt.tx.defaultTTLMins setting to specify the default time-to-live (TTL) valuefor outbound guaranteed delivery transactions. Specify the number of minutes you wantthe server to maintain outbound transactions in the job store when a service initiating anoutbound transaction does not specify a TTL value.

The default is: 30

ZDWW�W[�UHWU\%DFNRIIUse the watt.tx.retryBackoff setting to specify the number of seconds to wait after aservice request failure before the Job Manager resubmits the request to execute theservice to the SAP Business Connector Server.

The default is: 60

ZDWW�W[�VZHHS7LPHUse the watt.tx.sweepTime setting to specify the number of seconds between sweeps ofthe job store of outbound transactions. The server sweeps the job store to identifytransactions that it needs to submit.

The default is: 60

ZDWW�W[�MRE7KUHDGVUse the watt.tx.jobThreads setting to specify the number of client threads you want tomake available in a thread pool to service pending requests.

The default is: 5

ZDWW�W[�ORJILOHUse the watt.tx.logfile setting to specify the file in which the server maintains anaudit-trail log of all operations it processes for outbound guaranteed delivery transactions.

The default is: logs/txout.log


6KXWWLQJ�'RZQ�*XDUDQWHHG�'HOLYHU\


� $GPLQLVWHULQJ�*XDUDQWHHG�'HOLYHU\

When you initialize the server, it initializes guaranteed delivery capabilities. You can usethe Server Administrator to shut down, reinitialize, and test guaranteed delivery.

�6KXWWLQJ�'RZQ�*XDUDQWHHG�'HOLYHU\

You can shut down and re-enable guaranteed delivery capabilities without having to shutdown the server.

You might want to shut down guaranteed delivery to perform some administrationfunctions, such as correcting configuration errors or starting a new audit-trail log. (Tostart a new audit-trail log, move or rename the existing log—the server automaticallystarts a new log if one does not already exist.)

�7R�VKXW�GRZQ�JXDUDQWHHG�GHOLYHU\

1. Choose 6HUYLFHV on the navigation panel.

2. Choose tab page�6HUYLFH�/LVW.The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��723�/(9(/� screen.

3. Select the ZP interface name in the ,QWHUIDFHV column.The server displays the�,QWHUIDFHV�DQG�6HUYLFHV��ZP� screen.

4. Select the ZP�VHUYHU interface name in the ,QWHUIDFHV column.The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��ZP�VHUYHU� screen.

5. Select the ZP�VHUYHU�W[ interface name in the ,QWHUIDFHV column.The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��ZP�VHUYHU�W[� screen.

6. Select the icon in the 7HVW column for the VKXWGRZQ service.The server displays the 7HVW�ZP�VHUYHU�W[�VKXWGRZQ screen.

7. Choose 7HVW��QR�LQSXWV��The server disables the guaranteed delivery capabilities.

�5HLQLWLDOL]LQJ�*XDUDQWHHG�'HOLYHU\

Reinitialize guaranteed delivery if it becomes disabled. This section describes theprocedures to reinitialize guaranteed delivery for inbound transactions and outboundtransactions.

�,QERXQG�7UDQVDFWLRQV

If you shut down the guaranteed delivery capabilities to correct a configuration problemor to make an administrative change, you can reinitialize guaranteed delivery using theServer Administrator.


$GPLQLVWHULQJ�*XDUDQWHHG�'HOLYHU\


You can also use this procedure to reinitialize guaranteed delivery if it becomes disableddue to an error (for example, because of a disk full condition or if the server could notlocate the job store). Reinitialize guaranteed delivery after you correct the problem.

�7R�UHLQLWLDOL]H�JXDUDQWHHG�GHOLYHU\�IRU�LQERXQG�WUDQVDFWLRQV


2. Select tab page 6HUYLFH�/LVW.The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��723�/(9(/� screen.

3. Select the ZP interface name in the ,QWHUIDFHV column. The server displays the,QWHUIDFHV�DQG�6HUYLFHV��ZP� screen.

4. Select the ZP�VHUYHU interface name in the ,QWHUIDFHV column. The server displays the,QWHUIDFHV�DQG�6HUYLFHV��ZP�VHUYHU� screen.

5. Select the ZP�VHUYHU�W[ interface name in the ,QWHUIDFHV column. The server displaysthe ,QWHUIDFHV�DQG�6HUYLFHV��ZP�VHUYHU�W[� screen.

6. Select the icon in the 7HVW column for the LQLW service.The server displays the�7HVW�ZP�VHUYHU�W[�LQLW screen.

7. Choose 7HVW��QR�LQSXWV�.The server reinitializes the guaranteed delivery capabilities.

�2XWERXQG�7UDQVDFWLRQV

If guaranteed delivery capabilities for outbound transactions become disabled due to anerror (for example, because of a disk full condition or if the server could not locate thejob store), use this procedure to reinitialize guaranteed delivery after you correct theproblem.

�7R�UHLQLWLDOL]H�JXDUDQWHHG�GHOLYHU\�IRU�RXWERXQG�WUDQVDFWLRQV


2. Select tab page 6HUYLFH�/LVW.The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��723�/(9(/� screen.




6. Select the icon in the 7HVW column for the LQLW service.The server displays the 7HVW�ZP�VHUYHU�W[�UHVHW2XWERXQG screen.

7. Choose 7HVW��QR�LQSXWV��The server reinitializes the guaranteed delivery capabilities.


7HVWLQJ�*XDUDQWHHG�'HOLYHU\


�7HVWLQJ�*XDUDQWHHG�'HOLYHU\

You can invoke a service from the Server Administrator to ensure that the configurationis correct and guaranteed delivery is functioning properly.

�7R�WHVW�JXDUDQWHHG�GHOLYHU\


2. Select tab page 6HUYLFH�/LVW�The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��723�/(9(/� screen.

3. Select the ZP interface name in the ,QWHUIDFHV column.The server displays the�,QWHUIDFHV�DQG�6HUYLFHV��ZP��screen.


5. Select the ZP�VHUYHU�W[�interface name in the ,QWHUIDFHV column.The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��ZP�VHUYHU�W[� screen.

6. Select the icon in the 7HVW column for the VWDUW service. The server displays the7HVW�ZP�VHUYHU�W[�VWDUW screen. Type the number of minutes for the transaction to livein the WWO�(time-to-live) field. Then, choose 7HVW�ZLWK�LQSXWV. The server returns a WLG(transaction id). Copy the WLG; you will need it in the next two steps. Select yourbrowser’s back button to return to the�,QWHUIDFHV�DQG�6HUYLFHV��ZP�VHUYHU�W[��screen.

7. Select the icon in the 7HVW column for the�H[HFXWH service. The server displays the7HVW�ZP�VHUYHU�W[�H[HFXWH�screen. Fill in the input information:

� Paste the TID (transaction id) in the WLG field.

� Type the interface name for the service you want to invoke in the LIF field (e.g��ZP�VHUYHU).

� Type the service name for the service you want to invoke in the VYF field(e.g��SLQJ).

1RWH

Use a service that does not require input.

Then, choose 7HVW�ZLWK�LQSXWV. The server invokes the service. Select your browser’sback button to return to the ,QWHUIDFHV�DQG�6HUYLFHV��ZP�VHUYHU�W[� screen.

8. Choose the icon in the 7HVW column for the HQG service. The server displays the7HVW�ZP�VHUYHU�W[�HQG screen. Paste the tid (transaction id) in the WLG field. Then,choose 7HVW�ZLWK�LQSXWV. Select your browser’s back button to return to the�,QWHUIDFHVDQG�6HUYLFHV��ZP�VHUYHU�W[� screen.




�6SHFLI\LQJ�DQ�(�0DLO�$GGUHVV�IRU�(UURU�0HVVDJHV

When you configure guaranteed delivery, you must specify the e-mail address to whichthe SAP Business Connector Server can issue an error message if guaranteed deliverybecomes disabled. You can specify this address using the Server Administrator or byupdating the watt.server.txMail setting in the server configuration file (server.cnf).

�7R�VHW�WKH�H�PDLO�DGGUHVV�XVLQJ�WKH�6HUYHU�$GPLQLVWUDWRU

1. Choose 6HWWLQJV on the navigation panel.

2. Choose tab page *HQHUDO�6HWWLQJV.

3. Select (GLW�WKHVH�6HWWLQJV.

4. Type the e-mail address for the administrator to whom you want the server to senderror notification in the 7UDQVDFWLRQ�(�PDLO field in the 0DLO section of the screen.

5. Choose 6XEPLW.

�7R�VHW�WKH�H�PDLO�DGGUHVV�LQ�WKH�VHUYHU�FQI�ILOH

1. Shutdown the server. For instructions, refer to 6KXWWLQJ�'RZQ�WKH�6$3�%XVLQHVV&RQQHFWRU�6HUYHU on page 4-5.

2. Edit the server.cnf file, which is located in the VDSEF/server/config directory.

3. Add a line for the watt.server.txMail setting if one does not already exist.

4. Type the e-mail address for the administrator to whom you want the server to senderror notification when guaranteed delivery becomes disabled.

([DPSOH

[email protected]

5. Save the changes to the server.cnf file.

6. Restart the server. For instructions, refer to 5HVWDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU6HUYHU on page 4-5.

�7R�WHVW�HUURU�PHVVDJH�GHOLYHU\

1. Choose 6HUYLFHV�on the navigation panel.

2. Choose tab page 6HUYLFH�/LVW�The server displays the ,QWHUIDFHV�DQG�6HUYLFHV��723�/(9(/� screen.




6SHFLI\LQJ�DQ�(�0DLO�$GGUHVV�IRU�(UURU�0HVVDJHV



6. Choose the icon in the 7HVW column for the VHQG7[(UURU0DLO service.The server displays the�7HVW�ZP�VHUYHU�W[�VHQG7[(UURU0DLO screen.

7. Type a subject for the test e-mail in the VXEMHFW field and text to include in the e-mailnote in the body field. Then, choose 7HVW�ZLWK�LQSXWV. The server sends an e-mail noteto the administrator defined in the watt.server.txMail setting.

6$3�$* 6$3�%XVLQHVV�&RQQHFWRU�6HUYHU�'HSOR\PHQW�&KHFNOLVW

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH A-1

$SSHQGL[�$� 6$3�%XVLQHVV�&RQQHFWRU�6HUYHU�'HSOR\PHQW&KHFNOLVW

Introduction ..............................................................................A-2

STAGE 1: Installation..............................................................A-2

STAGE 2: Basic Configuration ................................................A-3

STAGE 3: Setting Up Users, Groups, and ACLs.....................A-4

STAGE 4: Publishing Packages..............................................A-5

STAGE 5: Configuring Database Connections........................A-6

STAGE 6: Installing Run-Time Classes ..................................A-6

STAGE 7: Setting Up Security ................................................A-7

STAGE 8: Startup and Test.....................................................A-8

STAGE 9: Archive Sources .....................................................A-8

6$3�%XVLQHVV�&RQQHFWRU�6HUYHU�'HSOR\PHQW�&KHFNOLVW 6$3�$*

,QWURGXFWLRQ

A-2 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

� ,QWURGXFWLRQ

This appendix contains a useful checklist for setting up your SAP Business ConnectorServer. It describes the steps to perform to put a SAP Business Connector Server intoproduction. The process is comprised of several stages. You should complete one stagebefore advancing to the next.

� 67$*(��,QVWDOODWLRQ

Complete the following steps to install and test the SAP Business Connector Serverprogram on the server computer.

6WHS $FWLRQ a

� 6HW�XS�7&3�,3�RQ�WKH�VHUYHU�FRPSXWHU� Ensure that network hardwareand software are working properly on the production server.

�� ,QVWDOO�WKH�-DYD�5XQ�WLPH�(QYLURQPHQW��-5(�� Use the latest JREavailable for your platform or one that you are confident operatescompatibly with the services you will be running (e.g., one withwhich your services have been tested successfully).

�� ,QVWDOO�WKH�6$3�%XVLQHVV�&RQQHFWRU�6HUYHU��Install the SAP BusinessConnector Server according to the instructions for your platform.Be sure to install a valid license key.

�� 9HULI\�WKH�VHUYHU�LV�UXQQLQJ�FRUUHFWO\� Start the SAP BusinessConnector Server. Verify that it is running correctly by invokingthe Server Administrator.

For instructions, refer to 6WDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU6HUYHU on page 4-2 and 6WDUWLQJ�WKH�6HUYHU�$GPLQLVWUDWRU on page5-2.

�� &KDQJH�GHIDXOW�SDVVZRUGV� Use the Server Administrator to assignnew passwords to the following user accounts:

The "Administrator" user account.

The "Replicator" user account.

The "Developer" user account.

For instructions on how to change passwords, refer to &KDQJLQJ3DVVZRUGV on page 7-6.




� 67$*(��%DVLF�&RQILJXUDWLRQ

Use the Server Administrator to configure the way in which the server will send outboundrequests, accept inbound requests, expire sessions, and issue error messages.

6WHS $FWLRQ a

�� 6HW�XS�WKH�OLVWHQLQJ�SRUWV� Use the /LVWHQLQJ�3RUWV screen to specifythe port(s) on which the server will listen for requests.

7LS� If you will receive HTTP and/or HTTPS requests on multipleports, you may want to disable all but one port (the one you willuse to interact with the Server Administrator) until the server isready for production.

For instructions on how to set up and disable listening ports, referto &RQILJXULQJ�/LVWHQLQJ�3RUWV on page 6-4.

�� 6SHFLI\�WKH�SUR[\�VHUYHUV� Use the 6HUYHU�6HWWLQJV screen to specifythe proxy server(s) (if any) through which this server will issueoutbound requests.

Specify which URLs (if any) can bypass the proxy server.

For instructions on how to specify proxy servers and bypass lists,refer to 6SHFLI\LQJ�D�3UR[\�6HUYHU on page 6-10

�� &RQILJXUH�VHVVLRQ�WLPHRXWV�DQG�:HE�DXWRPDWLRQ�VHWWLQJV� Use the6HUYHU�6HWWLQJV screen to set the timeout value and Webautomation settings you want the server to use.

For instructions, refer to 6HWWLQJ�WKH�7LPHRXW�/LPLW on page 6-11and�&RQILJXULQJ�:HE�$XWRPDWLRQ�6HWWLQJV on page 6-7.

�� 6SHFLI\�WKH�HUURU�PHVVDJH�UHFLSLHQWV� Use the 6HUYHU�6HWWLQJV screento specify the e-mail address where you want the server to senderror messages when an exception (a critical server error or abinding failure) occurs.

For instructions, refer to 6SHFLI\LQJ�(UURU�0HVVDJH�5HFLSLHQWV onpage 6-16.

�� 6HW�WKH�ORJJLQJ�SDUDPHWHUV� Edit the logging parameters in theserver.cnf file to specify the amount of detail you want theserver to record in the audit log and the way in which you want itto rotate the log files.

For instructions, refer to :RUNLQJ�ZLWK�/RJ�)LOHV on page 6-12.

1RWH� You cannot use the Server Administrator for this step. Youmust edit the server.cnf file, which resides in thesapbc/server/config directory.


67$*(��6HWWLQJ�8S�8VHUV��*URXSV��DQG�$&/V


� 67$*(��6HWWLQJ�8S�8VHUV��*URXSV��DQG�$&/V

Use the Server Administrator to identify user accounts, groups, and access control lists(ACLs) that are required by the services that will run on this server.

6WHS $FWLRQ a

�� ,GHQWLI\�VHFXUH�VHUYLFHV��Determine which services must run"securely"—i.e., access to them will be governed by an accesscontrol list (ACL).

�� &UHDWH�XVHU�,'V�DQG�JURXSV�RU�FRQILJXUH�DQ�H[WHUQDO�GLUHFWRU\� If youhave secure services, identify users and/or client applications thatare authorized to access those services and create groups thatcontain the authorized members.

If your site uses an external directory (either LDAP or NIS), youcan configure the server to access the user and group informationfrom the external directory.

For instructions for creating user IDs, refer to $GGLQJ�8VHU$FFRXQWV on page 7-5. For instruction for creating groups, refer to$GGLQJ�*URXSV on page 7-8. For instructions for using an externaldirectory, refer to8VLQJ�DQ�([WHUQDO�'LUHFWRU\��/'$3�RU�1,6��onpage 9-1

�� &UHDWH�$&/V� If you will run secure services on this server, use the$FFHVV�&RQWURO�0DQDJHPHQW screen to create an access controllist for each secure service.

For instructions, refer to &UHDWLQJ�$&/V on page 8-13.

�� ,GHQWLI\�EDFNXS�DGPLQLVWUDWRUV� Select one or two users who can actas a backup administrator when the primary administrator isunavailable. Use the *URXS�0DQDJHPHQW�screen to add theseusers to the Administrators group.

For instructions on how to grant a user administrator privileges,refer to &RQWUROOLQJ�:KR�&DQ�&RQILJXUH�DQG�0DQDJH�WKH�6HUYHUon page 8-2.




� 67$*(��3XEOLVKLQJ�3DFNDJHV

Install and configure the packages that will run on this server.

6WHS $FWLRQ a

�� ,QVWDOO�VHUYLFHV�RQ�WKH�VHUYHU. Use one of the following methods topublish your services to the production server:

0HWKRG��. Use the 3DFNDJH�3XEOLFDWLRQV�)XQFWLRQV screen toreplicate the packages from the development server to theproduction server.For instructions, refer to &RS\LQJ�3DFNDJHV�IURP�2QH�6HUYHU�WR$QRWKHU on page 10-14.

0HWKRG�� Use the Server Administrator of the publishing server tocreate a zip file containing each package you want to publish;then:

Copy the zip file to following directory on the target server:

VDSEF\server\replicate\inbound

Use the 3DFNDJH�0DQDJHPHQW�)XQFWLRQV screen to install eachpackage.

�� &RQILJXUH�WKH�VHUYLFHV�RQ�WKH�VHUYHU� Ensure that each service isenabled. Then, configure the following operating parameters foreach:

$&/�DVVLJQPHQWFor instructions, refer to $VVLJQLQJ�$&/V�WR�6HUYLFHV�DQG,QWHUIDFHV on page 8-16.

&DFKLQJ�SDUDPHWHUVFor instructions, refer to &DFKLQJ�6HUYLFH�5HVXOWV on page 12-1.

2XWSXW�7HPSODWH�$VVLJQPHQWFor instructions, refer to (GLWLQJ�6HUYLFH�,QIRUPDWLRQ on page 11-8.

;0/�ELQGLQJFor instructions, refer to (GLWLQJ�6HUYLFH�,QIRUPDWLRQ on page 11-8.

�� 'HOHWH�XQQHFHVVDU\�VHUYLFHV� Delete the WmDemos package, whichcontain services that are not needed to support a productionserver.

For instructions, refer to 'HOHWLQJ�D�3DFNDJH on page 10-12.


67$*(��&RQILJXULQJ�'DWDEDVH�&RQQHFWLRQV


� 67$*(��&RQILJXULQJ�'DWDEDVH�&RQQHFWLRQVIf your server will execute services against databases, take the following steps toconfigure the connection between the SAP Business Connector Server and each database.For more information about completing this stage, refer to &RQILJXULQJ�$FFHVV�WR'DWDEDVH�6\VWHPV on page 13-1.

6WHS $FWLRQ a

�� 0DNH�VXUH�WKH�WDUJHW�GDWDEDVH�LV�DFFHVVLEOH�IURP�WKH�6$3�%XVLQHVV�&RQQHFWRU6HUYHU� Ping the database server from the SAP Business ConnectorServer to ensure the connection between the two servers is operational.

�� 9HULI\�WKDW�WKH�UHTXLUHG�XVHU�DFFRXQWV�DUH�VHW�XS�RQ�WKH�WDUJHW�GDWDEDVH�V\VWHP�Make sure that the user IDs, passwords, and database privileges thatthe SAP Business Connector Server will use are set up on the targetdatabase. Consult with the database administrator to verify this.

�� ,QVWDOO�-'%&�'ULYHUV� Obtain the JDBC classes zip or jar file from thedatabase vendor. Copy the zip or jar file to a device or directory thatyour SAP Business Connector Server can access.

1RWH� If you use JDBC to access an ODBC driver, install and configurethe ODBC driver according to the vendor’s instructions.

�� 8SGDWH�WKH�FODVVSDWK� Unzip or unjar the Java classes for the JDBC driverin the VDSEF/server/lib/classes directory. For more information,refer to 0DNLQJ�WKH�-DYD�&ODVVHV�IRU�-'%&�'ULYHUV�$FFHVVLEOH on page13-3.

�� &UHDWH�D�GDWDEDVH�DOLDV�IRU�HDFK�WDUJHW�GDWDEDVH��Use WKH�'%�$OLDV0DQDJHPHQW�screen to create a database alias name for each datasource required by your services.

� 67$*(��,QVWDOOLQJ�5XQ�7LPH�&ODVVHVIf your services use run-time classes beyond those provided by Java or the SAP BusinessConnector Server (e.g., CORBA or MQ Series classes), install those classes on the server.

6WHS $FWLRQ a

�� ,QVWDOO�UXQ�WLPH�FODVVHV� Obtain the zip or jar file from the vendor, andthen copy the zip or jar file to a device or directory that your SAPBusiness Connector Server can access.

�� 8SGDWH�WKH�FODVVSDWK� Update the classpath statement in the server.sh

or server.bat file so that it points to the directory in which you haveinstalled the run-time classes.




� 67$*(��6HWWLQJ�8S�6HFXULW\Take the following steps to ensure that the security measures you want to use are in place.

6WHS $FWLRQ a

�� &KHFN�SDVVZRUGV��Verify that the Administrator and Replicator passwordshave been changed from the default values assigned by SAP AG.

�� (GLW�WKH�LQGH[�KWPO�ILOH�WR�SUHYHQW�DFFHVV�WR�6\VWHP�$GPLQLVWUDWRU� If youwant to prevent a user from inadvertently accessing the ServerAdministrator, edit the following file:

VDSEF\packages\Default\pub\index.html

and change the URL in the <meta http-equiv="refresh"> tag to someinnocuous page you have created (perhaps one that displays an errormessage with alternate links).

Note that if you implement this safeguard, you will not be able to invokethe System Administrator in the standard way (i.e., simply connecting tothe SAP Business Connector Server’s listening port). Instead, you willneed to type the Server Administrator’s complete URL as shown below:

http://6HUYHU�3RUW/WmRoot/index.dsp

where:

6HUYHU is the name of the SAP Business Connector Server, and3RUW is the port on which it listens for HTTP requests.

�� &KHFN�XVHU�DFFRXQWV� Verify that all user accounts have passwords asrequired.

�� &KHFN�$&/�DVVLJQPHQWV� Verify that all secure services have correct ACLassignments.

�� &KHFN�SUR[\�VHUYHU�VHWWLQJV� Verify that proxy server settings and bypasslist are correct.

�� 5HVWULFW�DFFHVV� Configure allow/deny lists to restrict inbound requests asnecessary.

�� ,QVWDOO�DQG�FRQILJXUH�GLJLWDO�FHUWLILFDWHV� If you are deploying an SSL-enabled server, install the server’s cert.der and privkey.der files inthe following directory:

VDSEF\server\config\

Then, use the 6HFXULW\�6HWWLQJV screen to configure X.509 features.For information about setting up the server to use SSL, refer to6HFXULQJ�&RPPXQLFDWLRQV�ZLWK�WKH�6HUYHU on page 8-4.


67$*(��6WDUWXS�DQG�7HVW


6WHS $FWLRQ a

�� &RQILJXUH�+773�URXWLQJ�V\VWHPV� If your server sits behind a routing, load-balancing, or URL-filtering system, consult with the administrator ofthat system to ensure that it will pass inbound requests to the SAPBusiness Connector Server.

� 67$*(��6WDUWXS�DQG�7HVWStart the server and test services to ensure that they operate as expected.

6WHS $FWLRQ a

�� 9HULI\�WKDW�OLVWHQLQJ�SRUWV�DUH�HQDEOHG� If you disabled the listening ports toprevent access to the server during the setup phase, use the ListeningPort page to enable them now.

7LS� After you enable a listening port, ping it to verify that it isoperational.

�� 5HVWDUW�WKH�VHUYHU� Use the Server Administrator to restart the server toensure all settings that you have made are in effect.For instructions, refer to 5HVWDUWLQJ�WKH�6$3�%XVLQHVV�&RQQHFWRU6HUYHU on page 4-5.

�� 7HVW�VHUYLFHV� Perform tests to ensure that user/client applications canaccess the server successfully.

1RWH� During this test you may also want to verify that your currentlicense will accommodate the expected concurrency demands on thisserver. Contact SAP AG to increase number of licensed seats ifnecessary.

�� *R�/LYH�

� 67$*(��$UFKLYH�6RXUFHVArchive a master copy of the packages on the server and the source files that were used tobuild them.

6WHS $FWLRQ a

�� Copy the contents of the server\packages directory to another devicefor backup and archival purposes.

�� Archive a copy of all the source files that went into producing theservices deployed on this server.

6$3�$* 6HUYHU�&RQILJXUDWLRQ�3DUDPHWHUV

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH B-1

$SSHQGL[�%� 6HUYHU�&RQILJXUDWLRQ�3DUDPHWHUV

Introduction ..............................................................................B-2

watt.debug................................................................................B-2

watt.debug2..............................................................................B-2

watt.net.....................................................................................B-2

6HUYHU�&RQILJXUDWLRQ�3DUDPHWHUV 6$3�$*

67$*(��$UFKLYH�6RXUFHV

B-2 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

watt.proxy. .......................................................................................B-4

watt.server. ...............................................................................B-4

watt.security............................................................................B-10

watt.tx. ....................................................................................B-10




� ,QWURGXFWLRQThis appendix contains a description of the parameters you can specify in the serverconfiguration file (server.cnf), which is located in the VDSEF/server/config directory.

The server uses default values for many of the parameters. If a parameter has a default, itis listed with the description of the parameter. Many of these parameters are set as youadminister the SAP Business Connector Server using the Server Administrator.

To update the server configuration by editing the server.cnf file, you should firstshutdown the SAP Business Connector Server; then update the server.cnf file. Afteryou make the changes, restart the server.

� ZDWW�GHEXJ�ZDWW�GHEXJ�OHYHOSets level of debugging information recorded in the server’s log file. The default is 4.

ZDWW�GHEXJ�ORJILOHSpecifies the name of the file to receive debugging information. The default islogs/server.log.

� ZDWW�GHEXJ��ZDWW�GHEXJ��IDF/LVWSpecifies a comma delimited list of enabled facilities for which the server logsinformation. The facilities are numbered. Specify the numbers for the facilities. Thedefault is 999, which indicates the server is to log information for all facilities. Specify1000 to prohibit the server from logging information for any service.

To view the names of facilities, use the /RJ�6HWWLQJV screen of the Server Administrator toenable and disable facilities for which you want the server to log information

ZDWW�GHEXJ��ORJVWULQJILOHSpecifies the name (without the extension �W[W) for the dictionary file that contains errorcodes and facilities. The default is lib/logstr (English Version).

ZDWW�GHEXJ��PD[ORJVL]HSpecifies the maximum size for the server log file. The default is 5000000.

� ZDWW�QHW�ZDWW�QHW�PD[5HGLUHFWVSpecifies the maximum number of HTTP redirects to allow before throwing an I/Oexception. The default is 5.

ZDWW�QHW�SUR[\+RVWSpecifies the host that this server should use for outbound HTTP requests. There is nodefault.

ZDWW�QHW�SUR[\3DVVSpecifies the password to use for authentication with the HTTP proxy host. There is nodefault.


ZDWW�QHW�


ZDWW�QHW�SUR[\3RUWSpecifies the port number on the proxy host to use for outbound HTTP requests. There isno default.

ZDWW�QHW�SUR[\6NLS/LVWSpecifies a list of domain names for which the SAP Business Connector Server shouldnot use proxy servers.. The default is localhost.

ZDWW�QHW�SUR[\8VHUSpecifies the user name to use for authentication with the HTTP proxy host. There is nodefault.

ZDWW�QHW�UHWULHVSpecifies the number of times to retry a server that times out. This can be overridden bythe client. The default is 0.

ZDWW�QHW�VHFXUH3UR[\+RVWSpecifies the host that this server should use for outbound HTTPS requests. There is nodefault.

ZDWW�QHW�VHFXUH3UR[\3DVVSpecifies the password to use for authentication with the HTTPS proxy host. There is nodefault.

ZDWW�QHW�VHFXUH3UR[\3RUWSpecifies the port number on the proxy host to use for outbound HTTPS requests. Thereis no default.

ZDWW�QHW�VHFXUH3UR[\8VHUSpecifies the user name to use for authentication with the HTTPS proxy host. There is nodefault.

ZDWW�QHW�WLPHRXWSpecifies the number of seconds to wait before a service is considered timed out. Thedefault is 180.

ZDWW�QHW�XVHU$JHQWSpecifies the value the server uses in the HTTP User Agent request header when itrequests a Web document from a Web server. The default is Mozilla/4.0 [en] (WinNT; I).

ZDWW�QHW�XVH&RRNLHVAccept ("true") or deny ("false" or null) cookies when communicating with Web servers.It is almost never a good idea to turn this off. Defaults to "true".




� ZDWW�SUR[\�ZDWW�SUR[\�FDFKHSpecifies the directory name for the cache file. The default is cache.

ZDWW�SUR[\�FDFKH5XOHVSpecifies the name of the file that defines proxy rules. The default is config/proxy.cnf.

� ZDWW�VHUYHU�ZDWW�VHUYHU�FDFKH�IOXVK0LQVSpecifies how often (in minutes) the server sweeps the cache to remove expired cacheentries and to prefetch cache service entries. The default is 10 minutes.

ZDWW�VHUYHU�FDFKH�JF0LQVSpecifies how often (in minutes) the server sweeps the cache to perform garbagecollection. The default is 60 minutes.

ZDWW�VHUYHU�FDFKH�LV3HUVLVWHQWSpecifies whether you want server cache to be persistent ("true") or not ("false"). Thedefault is "true".

ZDWW�VHUYHU�FDFKH�VWRUDJH7KUHVKROG.%Specifies the size (in kilobytes) of the persistent server cache threshold. There is nodefault.

ZDWW�VHUYHU�FOLHQW7LPHRXWSpecifies the amount of time (in minutes) after which an idle user session times out. Thedefault is 10.

ZDWW�VHUYHU�FOXVWHU�DZDUHSpecifies whether you want the server to participate in a cluster. The default is “false”.

You must be using the B2B High-Availability Option to use this setting. For moreinformation, refer to the ZHE0HWKRGV�%�%�+LJK�$YDLODELOLW\�2SWLRQ�8VHU�*XLGH.

ZDWW�VHUYHU�FOXVWHU�FRQ)DFWRUSpecifies how important open connections are for determining whether the server is busyor not. Specify a number from 0 (least important) through 1 (most important). The valuesyou specify for watt.server.cluster.conFactor, watt.server.cluster.memFactor5,watt.server.cluster.reqComplFactor, and watt.server.cluster.threadFactormust add up to 1. The default is 0.25.

You must be using the B2B High-Availability Option to use this setting. For moreinformation, refer to the ZHE0HWKRGV�%�%�+LJK�$YDLODELOLW\�2SWLRQ�8VHU�*XLGH.

ZDWW�VHUYHU�FOXVWHU�GESpecifies location of the cluster database that the servers in a cluster use to shareinformation. The default is datastore/Cluster.

You must be using the webMethods B2B High-Availability Option to use this setting. Formore information, refer to the ZHE0HWKRGV�%�%�+LJK�$YDLODELOLW\�2SWLRQ�8VHU�*XLGH.

ZDWW�VHUYHU�FOXVWHU�GLVDEOH/RDG%DODQFLQJSpecifies whether you want the clustered servers to perform load balancing by redirecting


ZDWW�VHUYHU�


requests. The default is “false”, which indicates that the servers will perform loadbalancing.


ZDWW�VHUYHU�FOXVWHU�/RFN7LPHRXWSpecifies the number of seconds that a clustered server waits to get access to the clusterobject in the cluster database to update its status information. The default is 10 seconds.


ZDWW�VHUYHU�FOXVWHU�PD[&RQVSpecifies the maximum number of connections to the server before it is considered busy.If the server has more than the number of open connections you specify, it redirectsrequests to another server in the cluster. The default is 50.


ZDWW�VHUYHU�FOXVWHU�PD[7KUHDGVSpecifies the maximum number of threads in use by the server before it is consideredbusy. If the server is using more threads than the number you specify, it redirects requeststo another server in the cluster. The default is 50.


ZDWW�VHUYHU�FOXVWHU�PHP)DFWRUSpecifies how important availability of memory is for determining whether the server isbusy or not. Specify a number from 0 (least important) through 1 (most important). Thevalues you specify for watt.server.cluster.conFactor,watt.server.cluster.memFactor5, watt.server.cluster.reqComplFactor, andwatt.server.cluster.threadFactor must add up to 1. The default is 0.25.


ZDWW�VHUYHU�FOXVWHU�PLQ)UHHPHPSpecifies minimum number of bytes of memory that a server has available before it isconsidered busy. If the server has fewer bytes of available memory than the number ofbytes you specify, it redirects requests to another server in the cluster. The default is32768.


ZDWW�VHUYHU�FOXVWHU�SDVVZRUGSpecifies the password the SAP Business Connector Server must supply when connectingto the machine where the cluster database is located. The default is "Cluster".





ZDWW�VHUYHU�FOXVWHU�UHIUHVK5DWHSpecifies number of seconds the server waits between attempts to refresh its statusinformation in cluster object in the cluster database. The default is 25.

ou must be using the webMethods B2B High-Availability Option to use this setting. Formore information, refer to the ZHE0HWKRGV�%�%�+LJK�$YDLODELOLW\�2SWLRQ�8VHU�*XLGH.

ZDWW�VHUYHU�FOXVWHU�UHT&RPSO)DFWRUSpecifies how important past completions of requests are for determining whether theserver is busy or not. Specify a number from 0 (least important) through 1 (mostimportant). If the percentage of completed requests is high, the server is keeping up withthe rate of requests. If the percentage of completed requests is low, the server is notkeeping up with the rate of requests, and potentially might have to redirect incomingrequests to other servers in the cluster.

The values you specify for watt.server.cluster.conFactor,watt.server.cluster.memFactor5, watt.server.cluster.reqComplFactor, andwatt.server.cluster.threadFactor must add up to 1. The default is 0.25.


ZDWW�VHUYHU�FOXVWHU�6HVV7LPHRXWSpecifies number of minutes that the server allows inactive session objects to remain inthe cluster database before removing them. The default is 60.


ZDWW�VHUYHU�FOXVWHU�WKUHDG)DFWRUSpecifies how important thread usage is for determining whether the server is busy or not.Specify a number from 0 (least important) through 1 (most important). The values youspecify for watt.server.cluster.conFactor, watt.server.cluster.memFactor5,watt.server.cluster.reqComplFactor, and watt.server.cluster.threadFactormust add up to 1. The default is 0.25.


ZDWW�VHUYHU�FOXVWHU�XVHUSpecifies user name the SAP Business Connector Server needs to supply whenconnecting to the machine where the cluster database Server is located. The default is"Cluster".

ZDWW�VHUYHU�HUURU0DLOSpecifies the additional port numbers on which the SAP Business Connector Serverlistens for FTP requests. The list is comma delimited. There is no default.

ZDWW�VHUYHU�IWS3RUW/LVWSpecifies the e-mail address of administrator to notify when the server encounters aninternal fault. There is no default.

ZDWW�VHUYHU�KRVW$OORZSpecifies the name of the host that is allowed service. There is no default.


ZDWW�VHUYHU�


ZDWW�VHUYHU�KRVW'HQ\Specifies the name of the host that is denied service. There is no default.

ZDWW�VHUYHU�LOOHJDO16&KDUVSpecifies the characters that you can use when naming a SAP BC package, interface orservice. The default is ?‘-#&@^!%*:$.\ /’;,~+=)(|}{][><.

ZDWW�VHUYHU�MGEF�GHIDXOW'ULYHUSpecifies the name of the Java class for the driver you want to use to connect to databaseswhen no driver name is supplied for a database alias. The default is the driver name forSun’s JVM: sun.jdbc.odbc.JdbcOdbcDriver.

ZDWW�VHUYHU�MGEF�GULYHUVSpecifies a colon-delimited list of JDBC drivers you want the server to load when itinitializes. There is no default.

ZDWW�VHUYHU�NH\Specifies the license key for the server. There is no default.

ZDWW�VHUYHU�OGDS�DWWU�PHPEHUSpecifies the name of the variable (e.g., member) from which the SAP BusinessConnector Server is to get the group membership information for a user ID. There is nodefault.

ZDWW�VHUYHU�OGDS�DWWU�SDVVZRUGSpecifies the name of the variable (e.g., password) from which the SAP BusinessConnector Server is to get the password for a user ID. This value must match the name ofthe attribute in which the LDAP server expects to receive passwords. There is no default.

ZDWW�VHUYHU�OGDS�DWWU�XVHULGSpecifies the name of the variable (e.g., uid) from which the SAP Business ConnectorServer is to get the User ID. This value must match the name of the attribute in which theLDAP server expects to receive user IDs. There is no default.

ZDWW�VHUYHU�OGDS�GLUHFWRU\5RRWSpecifies the distinguished name (DN) that defines the top entry of your LDAP directoryhierarchy (e.g., o=sap, c=US).

ZDWW�VHUYHU�OGDS�JURXS)LOWHUSpecifies a filter that the SAP Business Connector Server uses to narrow down theselection of groups within the group root that is specified by thewatt.server.ldap.groupRoot parameter. For more information about LDAP searchfilters, consult 5)&��6HDUFK�)LOWHUV�IRU�/'$3. To set a group filter, type the nameof the filter—e.g., (&(objectclass=rfc822mailgroup) (objectclass=homeGrownGroup).There is no default.

ZDWW�VHUYHU�OGDS�JURXS5RRWSpecifies the name of the root where group entries are located, relative to the specifieddirectory root, which is identified by the watt.server.ldap.directoryRoot parameter.Specify the name of the group root entry (e.g., ou=Groups). There is no default.

ZDWW�VHUYHU�OGDS�VHFXULW\�FUHGHQWLDOSpecifies the password the SAP Business Connector Server uses when submitting arequest to the LDAP server. There is no default.




ZDWW�VHUYHU�OGDS�VHFXULW\�SULQFLSDOSpecifies the user name the SAP Business Connector Server uses when submitting arequest to the LDAP server.. There is no default.

ZDWW�VHUYHU�OGDS�VHUYHUSpecifies the URL of the LDAP server. Specify the complete URL for your LDAP server.There is no default.

ZDWW�VHUYHU�OGDS�XVHU)LOWHUSpecifies a filter that the SAP Business Connector Server uses to narrow the selection ofusers within the user root that is specified by the watt.server.ldap.userRootparameter. When you specify a filter, the LDAP server searches only those user entriesmatching the filter criteria. For more information about LDAP search filters, refer to5)&��6HDUFK�)LOWHUV�IRU�/'$3. To set a user filter, type the name of the filter—e.g.,(objectclass=inetOrgPerson) or (uid=*). There is no default.

ZDWW�VHUYHU�OGDS�XVHU5RRWSpecifies the name of the root where user entries are located, relative to the specifieddirectory root, which is identified by the watt.server.ldap.directoryRoot parameter.Specify the name of the user root entry (e.g., ou=People). There is no default.

ZDWW�VHUYHU�OLFHQVHVSpecifies the number of licenses. The default is 1.

ZDWW�VHUYHU�ORJ5RWDWHSpecifies how the server rotates the log files. Specify “rename” to have the server renamethe log files to include the date and time it closes the logs and keep the log files in thesame directory. Specify “move” to have the server create a new subdirectory with a namethat represents the date and time it closes the log files and move the closed log files to thenew directory. If this parameter is not included in the server.cnf file, the server uses"rename".

ZDWW�VHUYHU�ORJ5RWDWH)LUVW,QWHUYDOSpecifies the number of milliseconds after the server is started when the server is to rotatethe log files for the first time. If this parameter is not included in the server.cnf file, theserver rotates the log files for the first time at 00:00 (midnight).

ZDWW�VHUYHU�ORJ5RWDWH,QWHUYDOSpecifies the number of milliseconds after the first log rotation when the server is tocontinue to rotate the log files. If this parameter is not included in the server.cnf file,the server continues to rotate the log files every 24 hours.

ZDWW�VHUYHU�ROGNH\Specifies the license key that was in use prior to the current key. There is no default.

ZDWW�VHUYHU�SRUWSpecifies the port number of the SAP Business Connector Server’s primary listening port.The default is 5555.

ZDWW�VHUYHU�SRUW/LVWSpecifies the additional port numbers on which the SAP Business Connector Serverlistens for HTTP requests. The list is comma delimited. There is no default.

ZDWW�VHUYHU�UHTXHVW&HUWVSpecifies whether the SAP Business Connector Server requests a digital certificate from


ZDWW�VHUYHU�


clients that connect to it through SSL. Set this parameter to "true" if you want the serverto request certificates. Set it to "false" if you do not want the server to request certificates.The default is false.

ZDWW�VHUYHU�VHFXUH3RUWSpecifies the port number of the SAP Business Connector Server’s primary securedlistening port. The default is 0.

ZDWW�VHUYHU�VHFXUH3RUW/LVWSpecifies the additional port numbers on which the SAP Business Connector Serverlistens for HTTPS requests. The list is comma delimited. There is no default.

ZDWW�VHUYHU�VHUYLFH0DLOSpecifies the e-mail address of an administrator to notify when a service no longer bindsto a target site correctly. There is no default.

ZDWW�VHUYHU�VPWS6HUYHUSpecifies the SMTP server to use for server error logging and service error e-mailnotification. There is no default.

ZDWW�VHUYHU�VWDWV�DYJ7LPHSpecifies the time period (in seconds) for which performance metrics are averaged. Thedefault is 10.

ZDWW�VHUYHU�VWDWV�ORJILOHSpecifies the name of the file to receive statistics. The default is logs/stats.log.

ZDWW�VHUYHU�VWDWV�SROO7LPHSpecifies the number of seconds between updates of statistics loggings. The default is 10.

ZDWW�VHUYHU�W[0DLOSpecifies the e-mail address of an administrator to notify when guaranteed deliverycapabilities are disabled due to an error (for example, if the SAP Business ConnectorServer encounters a disk full condition or if the audit-trail log is full). There is no default.

ZDWW�VHUYHU�W[�KHXULVWLF)DLO5HWU\Specifies whether the SAP Business Connector Server is to re-execute SAP BC servicesfor guaranteed delivery transactions in the job store that are PENDING when the SAPBusiness Connector Server is restarted after a failure. If a transaction is PENDING, theSAP BC service began execution before the SAP Business Connector Server failed.

If the setting is TRUE, the SAP Business Connector Server resets the transaction statusfrom PENDING to NEW, and the SAP BC service will be re-executed. If the setting isFALSE the SAP Business Connector Server resets the transaction status from PENDINGto FAIL to indicate the heuristic failure, and the SAP BC service will not be re-executed.The default is “true”.

ZDWW�VHUYHU�W[�ORJILOHSpecifies the file in which the server maintains an audit-trail log of all operations itprocesses for inbound guaranteed delivery transactions. The default is logs/txin.log.

ZDWW�VHUYHU�W[�MREGLUSpecifies the directory in which the server maintains the job store for inbound guaranteeddelivery transactions. The default is logs/jobsin.




ZDWW�VHUYHU�W[�VZHHS7LPHSpecifies the number of seconds between sweeps (clean up) of the job store for inboundguaranteed delivery transactions. The server sweeps the job store to remove expiredtransactions. The default is 60.

� ZDWW�VHFXULW\�ZDWW�VHFXULW\�FD&HUWSpecifies the path and file name of the file containing the certificate of the CertificateAuthority (CA) that issued the SAP Business Connector Server’s digital certificate. Thedefault is config/cacert.der.

ZDWW�VHFXULW\�&$'LUSpecifies the path name of a directory that contains the digital certificates of CAs thatyour SAP Business Connector Server trusts. When you indicate that you want the serverto request client certificates (watt.server.requestCerts), the server automatically presentsthe list of certificates in this directory to the client when it submits its own certificate.There is no default.

ZDWW�VHFXULW\�&$)LQJHUSULQWVSpecifies the path and file name that contains a list of fingerprints (digital signatures) inplain text. The fingerprints in this file combined with the fingerprints that the server isshipped with constitute the certificate authorities that the server knows about. There is nodefault.

ZDWW�VHFXULW\�SULYDWH.H\Specifies the path and file name of the file that contains the RSA private key associatedwith the SAP Business Connector Server’s digital certificate. The default isconfig/privkey.der.

ZDWW�VHFXULW\�VLJQHG&HUWSpecifies the path and file name of the file containing the SAP Business ConnectorServer’s digital certificate. The default is config/cert.der.

� ZDWW�W[�ZDWW�W[�GHIDXOW77/0LQVSpecifies the default time-to-live (TTL) value for outbound guaranteed deliverytransactions. Specify the number of minutes you want the server to maintain outboundtransactions in the job store when a service initiating an outbound transaction does notspecify a TTL value. The default is 30.

ZDWW�W[�GLVDEOHGSpecifies whether you want to disable the use of guaranteed delivery for outboundtransactions. By default, the server allows the use of guaranteed delivery for outboundtransactions. The default is "false".

ZDWW�W[�MREGLUSpecifies the directory in which the SAP Business Connector Server maintains the jobstore of outbound guaranteed delivery transactions. The default is logs/jobsout.


ZDWW�W[�


ZDWW�W[�MRE7KUHDGVSpecifies the number of client threads you want to make available in a thread pool toservice pending requests in the outbound guaranteed delivery job store. The default is 5.

ZDWW�W[�ORJILOHSpecifies the path and file in which the SAP Business Connector Server maintains anaudit-trail log of all the outbound guaranteed delivery transaction operations it requests.The default is logs/txout.log.

ZDWW�W[�UHWU\%DFNRII7LPHSpecifies the number of seconds to wait after a service request failure before the JobManager resubmits the request to execute the service to the SAP Business ConnectorServer. The default is 60.

ZDWW�W[�VZHHS7LPHSpecifies the number of seconds between sweeps of the job store of outbound guaranteeddelivery transactions. The server sweeps the job store to identify transactions that it needsto submit. The default is 60.

6$3�$* 6HUYHU�/RJ�)LOHV

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH C-1

$SSHQGL[�&� 6HUYHU�/RJ�)LOHV

The Audit Log...........................................................................C-2

The Error Log ...........................................................................C-3

The Server Log ........................................................................C-4

The Session Log ......................................................................C-5

The Statistics Log.....................................................................C-6

The Transaction Logs...............................................................C-8

6HUYHU�/RJ�)LOHV 6$3�$*

7KH�$XGLW�/RJ

C-2 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

� 7KH�$XGLW�/RJThe Audit Log (audit.log) maintains an audit trail for all services that the serverexecutes. For each service, the server adds two records that contain information about theservice. It adds one when it begins execution; this record includes the timestamp of whenexecution began. It adds the second record when the service terminates; this recordincludes the timestamp of when the service terminated.

([DPSOH�RI�DXGLW�ORJ

000000d9415f605f --- Start ---000000d9416bb234 23878555569 00134db3 wm.server.ui:getMenus begin000000d9416bb234 23878555569 00134db3 wm.server.ui:getMenus ok000000d9416bb52d 23878555569 00134db3 wm.server.query:getStats begin000000d9416bb52d 23878555569 00134db3 wm.server.query:getStats ok000000d9416bbc1a 23878555569 00134db3 wm.server.ui:getMenus begin000000d9416bbc1a 23878555569 00134db3 wm.server.ui:getMenus ok000000d9416bbc74 23878555569 00134db3 wm.server.access:userList begin000000d9416bbc7e 23878555569 00134db3 wm.server.access:userList ok

.

.

.

Information for asingle service.

Timestamp Thread identifier ofthe thread thatinvoked the service

Name of theservice

Description of theaudit event

Session identifier ofthe session thatinvoked the service

When the server begins auditing




� 7KH�(UURU�/RJThe Error log (error.log) maintains information about all errors and exceptions thathave occurred in the SAP BC system.

([DPSOH�RI�HUURU�ORJ

000000d9416bb849 java.lang.NoSuchMethodError:com.wm.app.b2b.server.Manifest: methodgetInterfaceInfo()Lcom/wm/util/Values; not found at com.wm.app.b2b.server.PackageManager.registerSpecImplementers(CompiledCode) atcom.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:312) atcom.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:243) at com.wm.app.b2b.server.PackageManager.loadPackages(Compiled Code) at com.wm.app.b2b.server.PackageManager.init(Compiled Code) at com.wm.app.b2b.server.Server.run(Server.java:157)

000000d9416bc3bf java.lang.NoSuchMethodError:com.wm.app.b2b.server.Manifest: methodgetInterfaceInfo()Lcom/wm/util/Values; not found at com.wm.app.b2b.server.PackageManager.registerSpecImplementers(CompiledCode) atcom.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:312) atcom.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:243) at com.wm.app.b2b.server.PackageManager.loadPackages(Compiled Code) at com.wm.app.b2b.server.PackageManager.init(Compiled Code) at com.wm.app.b2b.server.Server.run(Server.java:157)

�

�

�

Timestampand exception

Stack trace thatshows the callsequence leadingto the exception


7KH�6HUYHU�/RJ


� 7KH�6HUYHU�/RJThe Server Log (server.log) maintains information about the version of the SAPBusiness Connector Server that is running and operations that the server has performed.You can use this information for general debugging purposes.

([DPSOH�RI�VHUYHU�ORJ

000000 ----------- Mon Aug 02 13:50:41 EDT 1999000001 ----------- Mon Aug 02 13:50:41 EDT 1999000002 SRVINI0001C B2B Integration Server 3.0.0 Build 990802.000003 LICMGR0001C Start.000004 STAMGR0001C Start.000005 SRVMGR0001C Start.000006 WIDLSM0001C Start.000007 SRVINI0004C Flow Service Manager000008 SRVINI0002C Package Manager000009 PKGRPL0001C Start.00000A PCKGES0001C Loading packages.00000B PCKGES0005C Loading package Default from namespace.00000C PCKGES0005C Loading package WmUtil from namespace.00000D PCKGES0005C Loading package WmRoot from namespace.00000E PCKGES0012C Starting WmRoot. Invoke (wm.server.net.http:init).00000F HTTPLS0003D Starting to listen on port 5555.000010 PCKGES0012C Starting WmRoot. Invoke (wm.server.net.https:init).000011 PCKGES0012C Starting WmRoot. Invoke (wm.server.net.remote:init).000012 PCKGES0012C Starting WmRoot. Invoke (wm.server.net.ftp:init).000013 PCKGES0012C Starting WmRoot. Invoke (wm.server.tx:init).000014 TXJOBM9999O Start000015 PCKGES0012C Starting WmRoot. Invoke (wm.server.schedule:init).000016 PORMGR0001C Start. (PortManager)000017 B2BSRV0002C Initialization complete.

�

�

�

Log Sequence Facility Information Log Message

&ROXPQ 'HWDLOV

/RJ�6HTXHQFH Six-digit sequence number in hexidecimal

)DFLOLW\,QIRUPDWLRQ

Code that describe the facility or component that addedthe log message and the log message identifier, forexample:

SRVINI00001C

� � �




&ROXPQ 'HWDLOV

� Six-character abbreviation of the facility orcomponent that issued the log message.

� Four-digit message number of the log message

� One-digit severity code of the log message:

C Critical

D Debug

E Error

V Verbose

W Warning

/RJ�0HVVDJH Message that indicates the action the server performed.

� 7KH�6HVVLRQ�/RJThe Session Log (session.log) maintains information about all sessions in the SAP BCsystem. The SAP Business Connector Server creates a session when a developer connectsto the server from the SAP BC Developer or a SAP BC client connects to the server toexecute services. Each record in the Session Log includes a timestamp indicating when auser established a connection with the SAP Business Connector Server.


7KH�6WDWLVWLFV�/RJ


([DPSOH�RI�VHVVLRQ�ORJ

000000d9415f604b --- Start ---000000d9416bb158 Begin 23878555569 Default localhost000000d9417ab0f7 Expire 23878555569 rpcs=16 age=8931613000000d9417ab101 End 23878555569 rpcs=16 age=8931623000000d9458bed01 --- Start ---000000d9458cfe5e Begin 222735555569 Default localhost000000d9458da477 End 222735555569 rpcs=8 age=42521000000d9458dc35f Begin 222735555569 Administrator localhost000000d9458dc43b Begin 222735555569 Administrator localhost000000d94594b33e End 222735555569 rpcs=2 age=505056

.

.

.

Timestamp Session ID

How long the session existed(in milliseconds) before itexpired or ended

Action for the session:– beginning (Begin)– ending (End)– expiring (Expire)

Identity of the userthat is connected forthis session

Number of times theservice has beeninvoked in this session

When theserver beganlogging sessioninformation atserver startup

� 7KH�6WDWLVWLFV�/RJThe Statistics Log (stats.log) maintains statistical information about the consumptionof system resources.

([DPSOH�RI�VWDWV�ORJ

000000d9415f6069 --- Start ---000000d941602483 67108856 65135904 30 2 0 2238971 0 0 27 0 0000000d941610edf 67108856 65133488 30 2 0 2238971 0 0 27 0 0000000d94161f93c 67108856 65067664 30 2 0 2238971 0 0 27 0 0000000d94162e3a2 67108856 65065248 30 2 0 2238971 0 0 27 0 0000000d94163cdfe 67108856 64999088 30 2 0 2238971 0 0 27 0 0000000d94164b85b 67108856 64996672 30 2 0 2238971 0 0 27 0 0000000d94165a2cb 67108856 64930848 30 2 0 2238971 0 0 27 0 0000000d941668d1d 67108856 64928432 30 2 0 2238971 0 0 27 0 0000000d941677783 67108856 64862272 30 2 0 2238971 0 0 27 0 0000000d9416861e0 67108856 64859856 30 2 0 2238971 0 0 27 0 0

.

.

.��

When the server begins logging




&ROXPQ 'HVFULSWLRQ

� Timestamp

� Total memory

� Free memory

� Number of threads in use

� Number of current connections

� Lifetime average of number of connections

� Average number of connections for last poll cycle

� Number of current requests

� Lifetime average of number of requests

�� Average number of requests in last poll cycle

�� New requests per minute at the beginning of the poll cycle

�� New requests per minute at the end of the poll cycle


7KH�7UDQVDFWLRQ�/RJV


� 7KH�7UDQVDFWLRQ�/RJVThe Transaction Logs (txin.log and txout.log) maintain information aboutguaranteed delivery transactions. They contain a record of all critical operations that theserver performs for each guaranteed delivery transaction. The server maintains one logfor inbound guaranteed delivery transactions (txin.log) and a separate log for outboundtransactions (txout.log).

You can use these logs in conjunction with the appropriate job store to identify specificinformation about a transaction. For example, if a transaction fails, you can use the log todetermine how far the transaction got before failing so you can take appropriate measuresto recover a transaction.

1RWH

The server contains a job store for inbound transactions and a separate job store foroutbound transactions.

The server uses the watt.server.tx.logfile configuration setting in the server.cnf forthe location of the job store of inbound transaction. If this setting is not in theserver.cnf file, the server maintains the log in the VDSEF/server/logs/txin.log file.

The server uses the watt.tx.logfile configuration setting in the server.cnf for thelocation of the job store of outbound transaction. If this setting is not in the server.cnffile, the server maintains the log in the VDSEF/server/logs/txout.log file.

([DPSOH�RI�W[�ORJ

000000d9415f6069 START TXJobManager000000d941602483 CREATE tid=171191592i524310 (NEW)000000d941610edf JOB SUCCESS tid=171191592i524310 (DONE)000000d94161f93c END tid=171191592i524310 (DONE)000000d94162e3a2 CREATE tid=171191592i524481 (NEW)000000d94163cdfe JOB SUCCESS tid=171191592i524481 (DONE)000000d94164b85b END tid=171191592i524481 (DONE)000000d94165a2cb CREATE tid=171191592i524502 (NEW)000000d941668d1d JOB SUCCESS tid=171191592i524502 (DONE)000000d941677783 END tid=171191592i524502 (DONE)

.

.

.

When the server begins logging

Timestamp Operation theserverperformed

Each line contains a WLG, the transactionid for a transaction. All lines with thesame tid are for the same request.

Status of thetransaction

6$3�$* ,1'(;

6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH D-1

$SSHQGL[�'� ,1'(;

$Access Control Lists (ACLs)

ACL used when none assigned to service .........8-13, 8-15Administrators ........................................................... 8-12assigning to files ........................................................ 8-17assigning to interfaces................................................ 8-15assigning to services .................................................. 8-16creating ...................................................................... 8-13Default ....................................................................... 8-13default action ............................................................. 8-11deleting ...................................................................... 8-14description of use ....................................................... 8-10Developers ................................................................. 8-13how they work with services...................................... 8-15inherited ..................................................................... 8-15Precedence setting, changing ..................................... 8-12Precedence setting, description .................................. 8-11predefined .................................................................. 8-12Replicators ................................................................. 8-13updating ..................................................................... 8-13

access filedescription ................................................................. 8-17using to control access to files ................................... 8-17

accessingexternal user and group information ............................9-3

ACLs..................................6HH Access Control Lists (ACLs)activating

packages................................................................... 10-10server to prefetch service results ................................ 12-4

addingAccess Control Lists (ACLs) ..................................... 8-13additional listening ports..............................................6-5database aliases .......................................................... 13-3groups ..........................................................................7-8package dependencies.............................................. 10-13packages................................................................... 10-10port restrictions .......................................................... 8-18services to server manually ........................................ 11-9startup/shutdown services to packages..................... 11-12user accounts................................................................7-5

Administrator Port access ............................................... 8-18Administrator user account...............................................7-4administrators

adding alternate administrators ....................................3-4defining external users as........................................... 9-10e-mail address for guaranteed delivery ...................... 14-3password for predefined user account..........................3-3predefined ACL, description...................................... 8-12predefined group, description ......................................7-7predefined user account, description.....................3-3, 7-4receiving messages, overview......................................3-3

responsibilities .............................................................3-2role ...............................................................................3-2setting administrator listening port.............................8-18specifying who receives messages .............................6-16

Administrators ACL........................................................8-12Administrators group ........................................................7-7aliases, database

adding.........................................................................13-3deleting.......................................................................13-5information to supply for............................................13-2updating......................................................................13-5

Allow By Default access, for listening ports...................8-18architecture, SAP Business Connector Server...................2-2assigning

Access Control Lists (ACLs) to files..........................8-17Access Control Lists (ACLs) to interfaces .................8-15Access Control Lists (ACLs) to services....................8-16startup/shutdown services.........................................11-12

audit logdescription..........................................................6-12, C-2example .......................................................................C-2field descriptions .........................................................C-2location of ..................................................................6-13log rotation .................................................................6-14

audit-trail loggingdescription of log................................................6-12, C-2inbound guaranteed delivery transactions ..................14-5outbound guaranteed delivery transactions ................14-6overview.......................................................................2-5writing log to screen.....................................................4-3

authenticatingbasic authentication....................................................8-23client certificates ........................................................8-21description..................................................................8-21reasons server cannot use client certificates ...............8-22using user names and passwords ................................8-23when invalid password supplied.................................8-23when invalid user name supplied ...............................8-23when it occurs ............................................................8-21when user name not supplied .....................................8-23when using external directories ....................................9-9when using LDAP ........................................................9-9when using NIS............................................................9-9

%basic authentication.........................................................8-23blocking incoming requests to server ................................6-7

&C/C++ services, adding to server manually.....................11-9caching service results

activating when service prefetches .............................12-4controlling how server caches ....................................12-3overview.....................................................................12-2resetting for all services..............................................12-5

,1'(; 6$3�$*

D-2 6$3�%XVLQHVV�&RQQHFWRU�$GPLQLVWUDWLRQ�*XLGH

services suited for caching..........................................12-2services you should not cache ....................................12-3setting controls for services ........................................12-4viewing statistics ........................................................12-6when cache expires.....................................................12-3whether server prefetches results................................12-3

cancelingpackage subscriptions...............................................10-21when services scheduled to execute .........................11-18

certificate authorities (CAs)certificates to validate client certificates.....................8-22fingerprints .................................................................. 8-8requesting digital certificate from................................ 8-7

certificate signing request (CSR), creating....................... 8-7certificates, digital

certificates required to validate client certificates.......8-22configuring server to request client certificates ..........8-23obtaining certificate authority’s................................... 8-7reasons server cannot use to authenticate ...................8-22requesting for server.................................................... 8-7requesting using OpenSSL project SSL toolkit ........... 8-8using for authentication ..............................................8-21

changingAccess Control Lists (ACLs)......................................8-13database aliases ..........................................................13-5license key................................................................... 6-3membership for groups................................................ 7-9password for user accounts.......................................... 7-6Precedence setting for ACLs ......................................8-12service information.....................................................11-8when services scheduled to execute .........................11-18

checking if server is running ............................................ 4-4checklists

configuring database connections................................A-6configuring server........................................................A-3for deploying the server...............................................A-2installing server ...........................................................A-2installing services ........................................................A-5security ........................................................................A-7setting up user accounts, groups, and ACLs................A-4using client certificates...............................................8-22

classpath, updating servers ..............................................13-3client certificates

certificates required to validate...................................8-22Common Name field for user name............................8-21configuring server to request ......................................8-23description..................................................................8-21information required to use ........................................8-22reasons server cannot use to authenticate ...................8-22

clients, authenticating......................................................8-21closing log files ...............................................................6-14code subdirectory ............................................................10-3command line

parameters for starting server ...................................... 4-2starting server from ..................................................... 4-2

communications with serversecuring with SSL ....................................................... 8-4

configuration settingsbypass list for proxy servers .......................................6-10controlling who can set................................................ 8-2

descriptions................................................................. B-2guaranteed delivery.................................................... 14-3how long to keep inactive sessions ............................ 6-11how much information in server log.......................... 6-13how to set..................................................................... 5-4how to store closed log files....................................... 6-14LDAP...........................................................................9-4license keys.................................................................. 6-2listening ports .............................................................. 6-4log file rotation .......................................................... 6-14NIS............................................................................... 9-7overriding when starting server ................................... 4-2proxy servers.............................................................. 6-10server.cnf file ............................................................... 5-4SMTP server to use for e-mail ................................... 6-17Web automation........................................................... 6-7when to close log files ............................................... 6-14who receives error messages...................................... 6-16

configuringadditional listening ports.............................................. 6-5bypass list for proxy servers ...................................... 6-10checklist ...................................................................... A-3controlling who can configure the server..................... 8-2description of all settings ............................................ B-2guaranteed delivery.................................................... 14-3how long to keep inactive sessions ............................ 6-11how much information in server log.......................... 6-13how to store closed log files....................................... 6-14listening ports .............................................................. 6-4log file rotation .......................................................... 6-14proxy servers.............................................................. 6-10server ........................................................................... 6-1SMTP to use for e-mail.............................................. 6-17SSL .............................................................................. 8-9SSL, required information ........................................... 8-7to request client certificates ....................................... 8-23use of LDAP or NIS .................................................... 9-4user account to use....................................................... 7-4Web automation settings.............................................. 6-7when to close log files ............................................... 6-14who receives error messages...................................... 6-16

controllingaccess to services and files......................................... 8-10access to services by listening port ............................ 8-17how server caches service results............................... 12-3servers that can receive published packages ............ 10-15who can configure the server ....................................... 8-2who can develop services ............................................ 8-3

conventions used in this document ................................... 1-2copying packages

ACL used................................................................... 8-13group used ................................................................... 7-7how to ...................................................................... 10-18publisher tasks ......................................................... 10-16requesting subscriptions to packages ....................... 10-20subscriber tasks........................................................ 10-20to other servers......................................................... 10-14user account used......................................................... 7-4

creatingAccess Control Lists (ACLs) ..................................... 8-13

6$3�$* ,1'(;


certificate signing request (CSR) .................................8-7packages................................................................... 10-10packages distribution files........................................ 10-18

CSR (certificate signing request), creating .......................8-7

'database aliases

adding ........................................................................ 13-3deleting ...................................................................... 13-5information to supply for ........................................... 13-2updating ..................................................................... 13-5

database connectionschecklist for configuring ............................................. A-6information to supply................................................. 13-2making JDBC driver classes accessible ..................... 13-3preloading JDBC drivers at server initialization ........ 13-2specifying database location ...................................... 13-4specifying JDBC driver.............................................. 13-4

debug mode of the server..................................................4-3Default ACL ................................................................... 8-13Default user account .........................................................7-4defining

Access Control Lists (ACLs) ..................................... 8-13administrators listening port ...................................... 8-18database aliases .......................................................... 13-3groups ..........................................................................7-8how server caches service results............................... 12-3package dependencies.............................................. 10-13packages................................................................... 10-10user accounts................................................................7-3

deletingAccess Control Lists (ACLs) ..................................... 8-14database aliases .......................................................... 13-5groups ..........................................................................7-8listening ports...............................................................6-6packages................................................................... 10-12startup/shutdown services from packages ................ 11-12user accounts................................................................7-5

Deny By Default access for listening ports..................... 8-18dependencies, package.................................................. 10-13deploying SAP Business Connector Server ..................... A-2Developer user account.....................................................7-4developers

defining external users as........................................... 9-11predefined ACL, description...................................... 8-13predefined group, description ......................................7-7predefined user account, description............................7-4

Developers ACL ............................................................. 8-13Developers group..............................................................7-7digital certificates

certificates required to validate client certificates ...... 8-22client certificates for authentication ........................... 8-21configuring server to request client certificates.......... 8-23obtaining certificate authority’s ...................................8-7reasons server cannot use to authenticate...................8-22requesting.....................................................................8-7requesting using OpenSSL project SSL toolkit............8-8

digital signaturesdescription of use.........................................................8-5

obtaining ......................................................................8-8predefined.....................................................................8-8

disablingguaranteed delivery for outbound requests.................14-6listening ports...............................................................6-7packages...................................................................10-11

displayingactive license seats .......................................................6-4active sessions ..............................................................4-5documentation for packages.......................................10-8interfaces ....................................................................11-4license key....................................................................6-2license seat limit ...........................................................6-4log information on screen.............................................4-3membership for groups.................................................7-9package information...................................................10-6package subscriptions...............................................10-20packages residing on your server ...............................10-5service information.....................................................11-4service statistics..........................................................12-6services.......................................................................11-4subscribers to packages ............................................10-17when services scheduled to execute .........................11-18when system tasks execute .......................................11-18whether packages are enabled/disabled......................10-6whether packages are loaded/unloaded ......................10-5

distribution files for packagescreating.....................................................................10-18sending .....................................................................10-18

doc subdirectory..............................................................10-4documentation

for your packages .......................................................10-8related manuals.............................................................1-3

(editing service information .............................................11-8e-mail

address for guaranteed delivery..................................14-3address for messages when guaranteed delivery fails.6-17address for messages when internal errors occur........6-17address for messages when output binding fails.........6-17SMTP server to use ....................................................6-17

Enabled? icon, color descriptions....................................10-6enabling

listening ports...............................................................6-7packages...................................................................10-11

error logdescription..........................................................6-12, C-3example .......................................................................C-3field descriptions .........................................................C-3location of ..................................................................6-13log rotation .................................................................6-14

errorslog ......................................................................6-12, C-3specifying who receives messages .............................6-16

Everybody group...............................................................7-7executing

services.........................................................................2-4services at scheduled times.......................................11-12

,1'(; 6$3�$*


shutdown services.....................................................11-11startup services .........................................................11-11

external directoriesconsiderations for user accounts and groups ............... 9-8granting users access to services and files ..................9-12granting users administrator privileges.......................9-10granting users developer privileges ............................9-11how server authenticates.............................................. 9-9how server uses ........................................................... 9-2overview...................................................................... 9-2to stop using ................................................................ 9-8when server accesses ................................................... 9-3

external groupsassigning administrator privileges ..............................9-10assigning developer privileges....................................9-11assigning to ACLs ......................................................9-12configuring server to use ............................................. 9-4how server uses ........................................................... 9-2when server accesses ................................................... 9-3

external user accountsassigning access to services and files .........................9-12assigning administrator privileges ..............................9-10assigning developer privileges....................................9-11configuring server to use ............................................. 9-4how server uses ........................................................... 9-2when server accesses ................................................... 9-3

)fingerprints

description of use ........................................................ 8-5obtaining...................................................................... 8-8predefined.................................................................... 8-8

FTP listenersassigning to listening ports .......................................... 6-5

*group name

description ................................................................... 7-7specifying for groups................................................... 7-7

groupsadding.......................................................................... 7-8administrator privileges ............................................... 7-7changing membership.................................................. 7-9considerations when using external directories ........... 9-8defining ....................................................................... 7-6deleting........................................................................ 7-8developer privileges .................................................... 7-7externally-defined........................................................ 9-2group name.................................................................. 7-7overview...................................................................... 7-2predefined.................................................................... 7-7privileges that can be shared........................................ 7-6purpose ........................................................................ 7-2replicator privileges..................................................... 7-7settings ........................................................................ 7-7specify members of ..................................................... 7-7specify users that belong to ......................................... 7-3viewing membership ................................................... 7-9

guaranteed deliveryadministering ............................................................. 14-7audit-trail log for inbound transactions...................... 14-5audit-trail log for outbound transactions .................... 14-6configuring ................................................................ 14-3description of ............................................................. 14-2disabling outbound transactions................................. 14-6e-mail address for error notification................14-3, 14-10handling heuristic failures.......................................... 14-4handling restart after a failure .................................... 14-4how often to cleanup inbound job store ..................... 14-4inbound job store, description.................................... 14-3location of inbound job store ..................................... 14-4location of outbound .................................................. 14-6reinitializing for inbound transactions ....................... 14-7reinitializing for outbound transactions ..................... 14-8requests to other servers............................................. 14-2retry after server failure ............................................. 14-4retry wait.................................................................... 14-6server failure .............................................................. 14-4service threads ........................................................... 14-6shutting down ............................................................ 14-7specify how long transactions active ......................... 14-6submitting outbound transactions .............................. 14-6testing ........................................................................ 14-9thread pool ................................................................. 14-6transaction logs .................................................. 6-13, C-8

+heuristic failures, guaranteed delivery

specifying how to handle ........................................... 14-4High-Availability Option.................................................. 2-6HTTP headers, User Agent............................................... 6-8HTTP listeners

assigning to listening ports .......................................... 6-5assigning to primary listening port .............................. 6-4

HTTP proxy serverbypass list .................................................................. 6-10configuring ................................................................ 6-10

HTTPS listenersassigning to listening ports .......................................... 6-5assigning to primary listening port .............................. 6-4

HTTPS proxy serverbypass list .................................................................. 6-10configuring ................................................................ 6-10

,inherited Access Control Lists (ACLs)........................... 8-15installing

package published from another server.................... 10-22run-time classes .......................................................... A-6server .......................................................................... A-2services, checklist ....................................................... A-5

interfacesassigning Access Control Lists (ACLs) to ................. 8-15description ................................................................. 11-2listing ......................................................................... 11-4

6$3�$* ,1'(;


-Java run-time environment .............................................. A-2Java services

adding to server manually .......................................... 11-9settings for ................................................................. 11-8

JDBC driversmaking classes accessible .......................................... 13-3preloading at server initialization............................... 13-2specifying in database alias........................................ 13-4

job storefor inbound guaranteed delivery transactions ............ 14-3how long outbound transactions active ...................... 14-6location of inbound .................................................... 14-4location of outbound transactions .............................. 14-6removing expired inbound transactions ..................... 14-4submitting outbound transactions .............................. 14-6

.key pair used for SSL

description ...................................................................8-7obtaining ......................................................................8-7

/LDAP

assigning groups to ACLs .......................................... 9-12configuration settings...................................................9-4configuring server to use..............................................9-4considerations for user accounts and groups................9-8granting users access to services and files.................. 9-12granting users administrator privileges ...................... 9-10granting users developer privileges............................ 9-11how server authenticates ..............................................9-9how server uses............................................................9-2when server accesses....................................................9-3

license keyschanging.......................................................................6-3description ...................................................................6-2licensed seats ...............................................................6-3renewal reminders........................................................6-3renewing ......................................................................6-3viewing ........................................................................6-2viewing license seat limit.............................................6-4viewing number of active seats ....................................6-4when seat limit reached................................................6-3

listening portsadding additional .........................................................6-5Administrator Port ..................................................... 8-18Allow By Default access............................................ 8-18configuring...................................................................6-4controlling access to services through........................ 8-17default additional ports ................................................6-5default primary port .....................................................6-4deleting ........................................................................6-6Deny By Default access ............................................. 8-18disabling.......................................................................6-7enabling .......................................................................6-7

overview.......................................................................2-2primary.........................................................................6-4reasons to add additional ports .....................................6-5

listingactive sessions ..............................................................4-5interfaces ....................................................................11-4log information on screen.............................................4-3packages residing on your server ...............................10-5services.......................................................................11-4

load balancing, overview...................................................2-6Loaded? icon, color descriptions.....................................10-5loading packages ...........................................................10-11log files

audit log .............................................................6-12, C-2closing ........................................................................6-14error log..............................................................6-12, C-3examples......................................................................C-1field descriptions .........................................................C-1location.......................................................................6-13log rotation .................................................................6-14save closed files in multiple directory ........................6-15save closed files in single directory............................6-15server log............................................................6-12, C-4session log..........................................................6-13, C-5statistics log........................................................6-13, C-6transaction logs...................................................6-13, C-8types ...........................................................................6-12

loggingclosing log files ..........................................................6-14examples of log files ...................................................C-1location of log files.....................................................6-13log rotation .................................................................6-14overview.......................................................................2-5save closed log files in multiple directory ..................6-15save closed log files in single directory......................6-15types of log files .........................................................6-12writing log to screen.....................................................4-3

logging out of Server Administrator .................................5-4

0manifest file, contents .....................................................10-4Max Redirects, setting for Web automation......................6-8messages

internal error messages...............................................6-16service error messages................................................6-16SMTP server to use ....................................................6-17specify who receives when errors occur.....................6-16

1naming services...............................................................11-2NIS

assigning groups to ACLs ..........................................9-12configuration settings ...................................................9-7configuringservertouse .................................................9-7considerations for user accounts and groups ................9-8granting users access to services and files..................9-12granting users administrator privileges.......................9-10granting users developer privileges ............................9-11

,1'(; 6$3�$*


how server authenticates.............................................. 9-9how server uses ........................................................... 9-2when server accesses ................................................... 9-3

ns subdirectory ................................................................10-4

2OpenSSL project SSL toolkit

creating certificate signing request (CSR)................... 8-8requesting digital certificate ........................................ 8-8requesting private key.................................................. 8-8

output bindingsmessages when they fail .............................................6-16

output template for services ............................................11-9overview

audit-trail logging........................................................ 2-5caching service results........................................ 2-5, 12-2external directories ...................................................... 9-2guaranteed delivery ....................................................14-2listening ports .............................................................. 2-2load balancing ............................................................. 2-6package replication...................................................10-14proxy servers ............................................................... 2-3receiving administrator messages ................................ 3-3SAP Business Connector Server.................................. 2-2server security ...................................................... 2-5, 8-2services.......................................................................11-2user and groups ........................................................... 7-2Web automation configuration settings ....................... 6-8

3packages

ACL for package replication ......................................8-13activating ..................................................................10-10assigning startup/shutdown services to.....................11-12canceling subscriptions to ........................................10-21code subdirectory .......................................................10-3copying to another server .........................................10-14creating.....................................................................10-10deleting.....................................................................10-12dependencies on other packages...............................10-13description ..................................................................10-2determining whether enabled/disabled .......................10-6determining whether loaded/unloaded........................10-5directory structure ......................................................10-3disabling ...................................................................10-11displaying documentation for .....................................10-8displaying subscriptions to .......................................10-20doc subdirectory .........................................................10-4Enabled? icon color descriptions................................10-6enabling....................................................................10-11group for package replication...................................... 7-7guidelines for package replication............................10-16information you can view...........................................10-4installing published package.....................................10-22Loaded? icon color descriptions .................................10-5location.......................................................................10-3making available ......................................................10-11manifest file................................................................10-4

ns subdirectory........................................................... 10-4predefined .................................................................. 10-2prohibiting access to ................................................ 10-11pub subdirectory ........................................................ 10-4publishing to other servers ....................................... 10-18recovering ................................................................ 10-13reloading.................................................................. 10-11removing startup/shutdown services from ............... 11-12replicating ..................................................... 10-14, 10-18residing on your server .............................................. 10-5safe delete ................................................................ 10-12sample services .......................................................... 10-2specifying version numbers ..................................... 10-13subscribing to........................................................... 10-20tasks you can perform................................................ 10-9templates subdirectory ............................................... 10-4user account for package replication............................ 7-4viewing information about......................................... 10-6who can subscribe to................................................ 10-15widls subdirectory...................................................... 10-4Windows-specific service samples ............................ 10-2

passwordschanging ...................................................................... 7-6description ................................................................... 7-3predefined Administrator user account ........................ 3-3specifying in user accounts .......................................... 7-3

ports, listeningadding additional ......................................................... 6-5Administrators Port access......................................... 8-18Allow by Default access ............................................ 8-18configuring .................................................................. 6-4default additional ports ................................................ 6-5default primary port ..................................................... 6-4deleting ........................................................................ 6-6Deny by Default access.............................................. 8-18disabling ...................................................................... 6-7enabling ....................................................................... 6-7overview ...................................................................... 2-2primary ........................................................................ 6-4reasons to add additional ports..................................... 6-5

Precedence, for ACLsdescription ................................................................. 8-11setting ........................................................................ 8-12

prefetchservice results ............................................................ 12-3when to activate ......................................................... 12-4

preventingaccess to packages ................................................... 10-11use of listening ports.................................................... 6-7

primary listening portconfiguring .................................................................. 6-4default .......................................................................... 6-4

private/public key pair used for SSLdescription ................................................................... 8-7obtaining...................................................................... 8-7

private/public keypairrequesting using OpenSSL project SSL tookit............. 8-8

privilegesadministrator, description ............................................ 8-2administrator, granting when using external directory9-10

6$3�$* ,1'(;


developer, description ..................................................8-3developer, granting when using external directory .... 9-11replicator......................................................................7-7that groups can share....................................................7-6

proxy serversbypassing ................................................................... 6-10configuring................................................................. 6-10overview ......................................................................2-3

pub subdirectory ............................................................. 10-4publishing packages

creating the distribution file ..................................... 10-18guidelines................................................................. 10-16how to ...................................................................... 10-18installing published package .................................... 10-22requesting subscriptions........................................... 10-20securing what servers can receive ............................ 10-15sending the distribution file...................................... 10-18who can publish ....................................................... 10-16who can subscribe.................................................... 10-15

publishing serverscreating package distribution file ............................. 10-18displaying subscribers.............................................. 10-17publishing packages ................................................. 10-18sending package distribution file ............................. 10-18tasks ......................................................................... 10-16who can publish ....................................................... 10-16

5receiving administrator messages .....................................3-3recovering packages...................................................... 10-13registering services ......................................................... 11-6reinitializing

guaranteed delivery for inbound transactions ............ 14-7guaranteed delivery for outbound transactions .......... 14-8

reloading packages........................................................ 10-11removing

Access Control Lists (ACLs) ..................................... 8-14database aliases .......................................................... 13-5groups ..........................................................................7-8listening ports...............................................................6-6packages................................................................... 10-12scheduled execution of service................................. 11-18startup/shutdown services from packages ................ 11-12user accounts................................................................7-5

renewing license key.........................................................6-3replicating packages

ACL ........................................................................... 8-13group............................................................................7-7guidelines................................................................. 10-16how to ...................................................................... 10-18overview .................................................................. 10-14publisher tasks ......................................................... 10-16Replicator user account............................................ 10-16Replicators ACL ...................................................... 10-16Replicators group..................................................... 10-16requesting subscriptions to packages ....................... 10-20subscriber tasks ........................................................ 10-20user account .................................................................7-4who can subscribe.................................................... 10-15

Replicator group................................................................7-7Replicator user account .....................................................7-4Replicators ACL .............................................................8-13requesting

digital certificate...........................................................8-7private/public key pair..................................................8-7

resettingcache for all services ..................................................12-5

resources, systemlog showing use..................................................6-13, C-6

restartingguaranteed delivery for inbound transactions.............14-7guaranteed delivery for outbound transactions...........14-8reasons for restarting server..........................................4-5server............................................................................4-5

restrictingaccess to Server Administrator.....................................8-2access to server from SAP Business Connector

Developer ................................................................8-3access to services and files .........................................8-10access to services by port ...........................................8-17

retry guaranteed delivery.................................................14-4role

of administrator ............................................................3-2of SAP Business Connector Server ..............................2-2

rotation of log files..........................................................6-14run-time classes, installing ...............................................A-6

6SAP BC services .................................................6HH servicesSAP Business Connector Developer

predefined user account to use .....................................7-4privilege required to access server from.......................8-3

SAP Business Connector Serverarchitecture...................................................................2-2audit-trail logging, overview ........................................2-5clustering servers, description ......................................2-6determining if running..................................................4-4license keys ..................................................................6-2process for executing services ......................................2-4recovery after hardware or software failure..................4-6restarting.......................................................................4-5retrieving data for services ...........................................2-3role ...............................................................................2-2shutting down...............................................................4-5when to restart ..............................................................4-5

SAP Business Connector Serverconfiguration settings ..................................................B-2configuring ...................................................................6-1debug mode ..................................................................4-3deploying.....................................................................A-2how it authenticates clients.........................................8-21how it maintains log files ...........................................6-14how SSL is used ...........................................................8-5installing......................................................................A-2log showing server information..........................6-12, C-4overview.......................................................................2-2preventing use of listening ports...................................6-7process when starting ...................................................4-4

,1'(; 6$3�$*


requesting digital certificate ........................................ 8-7security overview ................................................. 2-5, 8-2specify who receives messages when errors occur .....6-16starting from command line......................................... 4-2testing installation .......................................................A-8when it authenticates clients.......................................8-21

scheduling execution of servicescanceling scheduled user task...................................11-18changing scheduled times.........................................11-18complex scheduling options .....................................11-14description ................................................................11-12examples of complex scheduling options .................11-15execute one time.......................................................11-13execute repeated times..............................................11-13how often to execute.................................................11-13system tasks..............................................................11-13user tasks ..................................................................11-12viewing scheduled times...........................................11-18viewing when system tasks execute .........................11-18

seats, licensedlimit ............................................................................. 6-3viewing active ............................................................. 6-4viewing limit ............................................................... 6-4

Secure Sockets Layer (SSL)background information .............................................. 8-4certificate signing request (CSR)................................. 8-7checklist to request client certificates .........................8-22client certificates.........................................................8-21configuring server to request client certificates ..........8-23configuring server to use ............................................. 8-9creating CSR using OpenSSL project SSL tookit........ 8-8how server uses ........................................................... 8-5information required to implement.............................. 8-7information required to use client certificates ............8-22obtaining certificate authority’s certificate .................. 8-7obtaining fingerprint files............................................ 8-8obtaining private/public key pair................................. 8-7OpenSSL project ......................................................... 8-7predefined fingerprint files .......................................... 8-8private/public key pair................................................. 8-7requesting digital certificate ........................................ 8-7requesting private key using OpenSSL project SSL tookit

................................................................................ 8-8SSL toolkit .................................................................. 8-7use of fingerprint files ................................................. 8-5

securitychecklist.......................................................................A-7controlling access to services and files.......................8-10controlling access to services by listening port ..........8-17controlling servers that can receive published packages

.............................................................................10-15controlling who can configure the server .................... 8-2controlling who can develop services.......................... 8-3information required to implement SSL...................... 8-7overview............................................................... 2-5, 8-2securing server communications ................................. 8-4

sending distribution files ...............................................10-18server............................6HH SAP Business Connector ServerServer Administrator

controlling access to .................................................... 8-2

description ............................................................3-3, 5-2how to use.................................................................... 5-3logging out of............................................................... 5-4picture of...................................................................... 5-3starting ......................................................................... 5-2

server clusteringdescription ................................................................... 2-6

server logconfiguring how much information is recorded......... 6-13description ......................................................... 6-12, C-4example....................................................................... C-4field descriptions......................................................... C-4location of.................................................................. 6-13log rotation................................................................. 6-14

server security......................................................6HH securityserver.cnf

description of settings ................................................. B-2guaranteed delivery settings....................................... 14-3how to set configuration settings ................................. 5-4location ....................................................................... B-2

servicesACL used when no assigned ACL....................8-13, 8-15assigning Access Control Lists (ACLs) to ................. 8-16caching results, overview........................................... 12-2caching service results overview.................................. 2-5canceling scheduled user task .................................. 11-18changing scheduled times of execution ................... 11-18controlling access to by listening port........................ 8-17controlling caching .................................................... 12-3controlling who can access ........................................ 8-10controlling who can develop........................................ 8-3deleting its Access Control List (ACL)...................... 8-14denying access to external users ................................ 9-12fully-qualified names ................................................. 11-2granting access to external users................................ 9-12guaranteeing delivery of requests to server................ 14-2guaranteeing delivery of responses from services...... 14-2guidelines for using startup/shutdown ..................... 11-11how Access Control Lists (ACLs) work .................... 8-15how server executes..................................................... 2-4how server retrieves data for........................................ 2-3how to control access to............................................. 8-10identifying startup/shutdown services...................... 11-12information to schedule user tasks........................... 11-13inherited Access Control Lists (ACLs) ...................... 8-15listing......................................................................... 11-4making available........................................................ 11-6making unavailable.................................................... 11-7manually adding to server.......................................... 11-9naming ....................................................................... 11-2output templates......................................................... 11-9overview .................................................................... 11-2registering .................................................................. 11-6resetting cache for all services ................................... 12-5samples in WmDemos ............................................... 10-2scheduling to execute............................................... 11-12setting cache controls................................................. 12-4settings for Java services............................................ 11-8shutdown.................................................................. 11-11startup ...................................................................... 11-11

6$3�$* ,1'(;


stateless setting .......................................................... 11-8suited for caching....................................................... 12-2tasks you can perform ................................................ 11-6testing....................................................................... 11-10types you should not cache ........................................ 12-3unregistering .............................................................. 11-7updating information about........................................ 11-8viewing information about ......................................... 11-4viewing scheduled times of execution ..................... 11-18viewing service statistics............................................ 12-6viewing when system tasks execute ......................... 11-18Web automation configuration settings........................6-7when cached results expire ........................................ 12-3when shutdown services are executed...................... 11-11when startup services are executed .......................... 11-11whether server prefetches results ............................... 12-3

session logdescription ......................................................... 6-13, C-5example....................................................................... C-6field descriptions......................................................... C-6location of .................................................................. 6-13log rotation................................................................. 6-14

sessionshow long to keep inactive sessions ............................ 6-11log file................................................................ 6-13, C-5maximum number allowed per license.........................6-3stopping all ..................................................................4-5timeout limit............................................................... 6-11viewing ........................................................................4-5

shutdown servicesguidelines for use ..................................................... 11-11what they are............................................................ 11-11

shutting downguaranteed delivery.................................................... 14-7SAP Business Connector Server ..................................4-5server with restart.........................................................4-5

SMTP server to use for e-mail ........................................ 6-17SSL ..................................... 6HH Secure Sockets Layer (SSL)starting

command line parameters ............................................4-2guaranteed delivery for inbound transactions ............ 14-7guaranteed delivery for outbound transactions .......... 14-8Server Administrator....................................................5-2server from command line ...........................................4-2server, overriding configuration settings......................4-2server, process..............................................................4-4

startup servicesguidelines for use ..................................................... 11-11what they are............................................................ 11-11

stateless parameter for services....................................... 11-8statistics log

description ......................................................... 6-13, C-6example....................................................................... C-6field descriptions......................................................... C-6location of .................................................................. 6-13log rotation................................................................. 6-14

stoppingactive sessions..............................................................4-5server ...........................................................................4-5server with restart.........................................................4-5

use of external directories.............................................9-8subscribing servers

canceling subscriptions ............................................10-21displaying .................................................................10-17installing published package.....................................10-22requesting subscriptions ...........................................10-20tasks..........................................................................10-20who can subscribe ....................................................10-15

subscribing to packagesdisplaying current subscriptions ...............................10-20guidelines .................................................................10-16how to.......................................................................10-20who can subscribe ....................................................10-15

subscriptionscanceling ..................................................................10-21displaying .................................................................10-20installing published package.....................................10-22requesting from a remote server ...............................10-20

system resourceslog showing use..................................................6-13, C-6

system tasksdescription................................................................11-13viewing when scheduled to execute .........................11-18

7templates subdirectory ....................................................10-4templates, output

for services .................................................................11-9testing

guaranteed delivery ....................................................14-9installation of server ....................................................A-8services.....................................................................11-10

time to live (TTL), guaranteed deliveryspecifying ...................................................................14-6

timeout limitssessions ......................................................................6-11Web automation ...........................................................6-8

transaction logsdescription..........................................................6-13, C-8example .......................................................................C-8field descriptions .........................................................C-8location of ..................................................................6-13log rotation .................................................................6-14

TTL (time to live), guaranteed deliveryspecifying ...................................................................14-6

typographical conventions ................................................1-2

8unregistering services......................................................11-7updating

Access Control Lists (ACLs)......................................8-13database aliases ..........................................................13-5license key....................................................................6-3membership for groups.................................................7-9service information.....................................................11-8when services scheduled to execute .........................11-18

user accountsaccount to configure and manage server ......................7-4

,1'(; 6$3�$*


account to use when connecting from SAP BusinessConnector Developer.............................................. 7-4

adding.......................................................................... 7-5Administrator .............................................................. 3-3considerations when using external directories ........... 9-8deleting........................................................................ 7-5description ................................................................... 7-3externally-defined........................................................ 9-2group membership....................................................... 7-3overview...................................................................... 7-2password...................................................................... 7-3predefined.................................................................... 7-4purpose ........................................................................ 7-2settings ........................................................................ 7-3user name .................................................................... 7-3using to authenticate...................................................8-23when client does not supply a user name..................... 7-4

User Agent setting for Web automation ........................... 6-8user name

Common Name field of client certificate ...................8-21externally-defined........................................................ 9-2specifying in user account ........................................... 7-3using to authenticate...................................................8-23

user taskscanceling scheduled execution .................................11-18changing when scheduled to execute........................11-18complex scheduling options .....................................11-14examples of complex scheduling options .................11-15information to schedule services ..............................11-13schedule to execute one time....................................11-13schedule to execute repeated times...........................11-13viewing when scheduled to execute .........................11-18

users ...........................................................6HH user accountsauthenticating .............................................................8-21

9version numbers for packages .......................................10-13viewing

active license seats....................................................... 6-4active sessions ............................................................. 4-5documentation for packages .......................................10-8interfaces ....................................................................11-4license key................................................................... 6-2license seat limit .......................................................... 6-4membership for groups................................................ 7-9package information ...................................................10-6package subscriptions...............................................10-20packages residing on your server................................10-5service information.....................................................11-4service statistics..........................................................12-6services.......................................................................11-4subscribers to packages ............................................10-17when services scheduled to execute .........................11-18when system tasks execute .......................................11-18whether packages are enabled/disabled ......................10-6whether packages are loaded/unloaded ......................10-5

:watt.debug.level.............................................................B-2watt.debug.logfile ..........................................................B-2watt.debug2.facList .......................................................B-2watt.debug2.logstringfile ...............................................B-2watt.debug2.maxlogsize ................................................B-2watt.net.maxRedirects ...................................................B-2watt.net.proxyHost.........................................................B-2watt.net.proxyPass .........................................................B-2watt.net.proxyPort .........................................................B-3watt.net.proxySkipList...................................................B-3watt.net.proxyUser.........................................................B-3watt.net.retries ...............................................................B-3watt.net.secureProxyHost ..............................................B-3watt.net.secureProxyPass...............................................B-3watt.net.secureProxyPort ...............................................B-3watt.net.secureProxyUser ..............................................B-3watt.net.timeout .............................................................B-3watt.net.useCookies .......................................................B-3watt.net.userAgent .........................................................B-3watt.proxy.cache............................................................B-4watt.proxy.cacheRules...................................................B-4watt.security.caCert ....................................................B-10watt.security.CADir....................................................B-10watt.security.CAFingerprints......................................B-10watt.security.privateKey.............................................B-10watt.security.signedCert .............................................B-10watt.server.cache.flushMins ..........................................B-4watt.server.cache.gcMins...............................................B-4watt.server.cache.isPersistent ........................................B-4watt.server.cache.storageThresholdKB .........................B-4watt.server.clientTimeout ..............................................B-4watt.server.cluster.aware ...............................................B-4watt.server.cluster.conFactor .........................................B-4watt.server.cluster.db.....................................................B-4watt.server.cluster.disableLoadBalancing......................B-4watt.server.cluster.LockTimeout ...................................B-5watt.server.cluster.maxCons..........................................B-5watt.server.cluster.maxThreads .....................................B-5watt.server.cluster.memFactor.......................................B-5watt.server.cluster.minFreemem....................................B-5watt.server.cluster.password..........................................B-5watt.server.cluster.refreshRate.......................................B-6watt.server.cluster.reqComplFactor ...............................B-6watt.server.cluster.SessTimeout ....................................B-6watt.server.cluster.threadFactor.....................................B-6watt.server.cluster.user ..................................................B-6watt.server.errorMail .....................................................B-6watt.server.ftpPortList ...................................................B-6

6$3�$* ,1'(;


watt.server.hostAllow ....................................................B-6watt.server.hostDeny .....................................................B-7watt.server.illegalNSChars ............................................B-7watt.server.jdbc.defaultDriver .......................................B-7watt.server.jdbc.drivers..................................................B-7watt.server.key...............................................................B-7watt.server.ldap.attr.member..........................................B-7watt.server.ldap.attr.password........................................B-7watt.server.ldap.attr.userid.............................................B-7watt.server.ldap.directoryRoot.......................................B-7watt.server.ldap.groupFilter ...........................................B-7watt.server.ldap.groupRoot............................................B-7watt.server.ldap.security.credential................................B-7watt.server.ldap.security.principal .................................B-8watt.server.ldap.server ...................................................B-8watt.server.ldap.userFilter..............................................B-8watt.server.ldap.userRoot ..............................................B-8watt.server.licenses ........................................................B-8watt.server.logRotate .....................................................B-8watt.server.logRotateFirstInterval..................................B-8watt.server.logRotateInterval .........................................B-8watt.server.oldkey..........................................................B-8watt.server.port ..............................................................B-8watt.server.portList ........................................................B-8watt.server.requestCerts.................................................B-8watt.server.securePort....................................................B-9watt.server.securePortList..............................................B-9watt.server.serviceMail ..................................................B-9watt.server.smtpServer...................................................B-9watt.server.stats.avgTime ..............................................B-9watt.server.stats.logfile ..................................................B-9watt.server.stats.pollTime ..............................................B-9watt.server.tx.heuristicFailRetry.......................... 14-4, B-9watt.server.tx.jobdir ............................................. 14-4, B-9watt.server.tx.logfile ............................................ 14-5, B-9watt.server.tx.sweepTime ................................. 14-4, B-10watt.server.txMail ................................................ 14-3, B-9watt.tx.defaultTTLMins.................................... 14-6, B-10watt.tx.disabled................................................. 14-6, B-10watt.tx.jobdir..................................................... 14-6, B-10watt.tx.jobThreads ............................................ 14-6, B-11watt.tx.logfile.................................................... 14-6, B-11watt.tx.retryBackoff ........................................................ 14-6watt.tx.retryBackoffTime............................................B-11watt.tx.sweepTime............................................ 14-6, B-11Web automation

configuration settings...................................................6-8Max Redirects setting ..................................................6-8number of allowed redirected requests.........................6-8number of times to reissue requests .............................6-9Retries setting ..............................................................6-9

time to wait for responses.............................................6-8Timeout setting.............................................................6-8User Agent setting........................................................6-8

widls subdirectory...........................................................10-4WmDemos package ........................................................10-2WmPublic package..........................................................10-2WmRoot package............................................................10-2WmWin32s package .......................................................10-2

=zip files for packages

creating.....................................................................10-18sending .....................................................................10-18

sap bc administration guide

Documents

user names

file names

sap earlywatch

sap archivelink

sap system

table names

path names

includeprogram names