installation guide sap business one integration

PUBLIC

Installation Guide

Solutions from SAP

SAP Business One 2007integration platform

June 2009

SAP Business One 2007 integration platform Installation Guide

© SAP AG 2009 2

ContentsInstallation Guide for SAP Business One 2007 integration platform ...................................................... 3

Introduction................................................................................................................................................ 3

Target Audience....................................................................................................................................... 3

SAP B1iSN 2007 Server Installation - Step by Step.................................................................................. 4

Preparing for Installation........................................................................................................................... 4

Installing SAP Business One integration Server........................................................................................ 7

SAP B1iSN 2007 EventSender, DI-Proxy Installation - Step by Step ....................................................... 9

Uninstalling SAP Business One integration platform.............................................................................11

Appendix I: B1iSN Components Setup and Deployment Options..........................................................12

Components of the B1iSN Solution..........................................................................................................12

B1iP B1 Client Components ....................................................................................................................13

B1iP R/3 Client Components ...................................................................................................................17

Appendix II: Deployment Scenarios.........................................................................................................18

Choosing a Scenario: Considerations ......................................................................................................18

The Deployment Scenarios in Detail ........................................................................................................19

Icons and Typographic Conventions.......................................................................................................26

Copyrights, Trademarks, and Disclaimers ..............................................................................................27


© SAP AG 2009 3

Installation Guide for SAP Business One 2007integration platformIntroductionThis document describes the technical installation of SAP Business One integration platform (B1iP).

It is recommended that you install B1iP on a different machine other than the SAP BusinessOne 2007 server.

If you do need to install B1iP on the same machine as the SAP Business One 2007 server,which has the embedded B1iP installed by default, you must remove the embedded B1iP first.However, this might cause the Bank Statements Processing and Legal List of SAP BusinessOne 2007 stop working anymore. Consult the related support before you remove theembedded B1iP.

To remove the embedded B1iP, choose Control Panel Add/Remove Program, select SAPBusiness One integration platform from the list, and choose Change/Remove.

From on B1iSN 2007 patch level 03, the B1iSN 2007 Technology components are separated for installation:

SAP Business One integration Server

SAP Business One integration EventSender

SAP Business One integration DI-Proxy

The complete B1iSN 2007 installation process generally can be separated into two parts:

1. B1iSN 2007 server installation, which include only one component:


2. B1iSN 2007 components installed on the SAP Business One server, which includes:


SAP Business One integration DI-Proxy

Target AudienceThis document is intended for system administrators and those responsible for the proper installation andfunctioning of SAP Business One integration platform.


© SAP AG 2009 4

SAP B1iSN 2007 Server Installation - Step by StepHardware and Software RequirementsRequirement Type Requirement

Hardware requirements 1x Intel Pentium III

Minimum 512MB, 2 GB RAM (for typical production usage)

500M free disk space

24x or higher CD-ROM

Software requirements IA32

Microsoft Windows 2003 Server Standard/Enterprise 32Bits orMicrosoft Windows XP Professional/Home Edition or VistaBusiness Edition 32Bits or Vista Ultimate Edition 64Bits

X64

Microsoft Windows 2003 Server Standard 64Bits or MicrosoftWindows XP Professional Edition 64Bits

Microsoft SQL Server 2005 / Microsoft SQL Server 2008 /MaxDB 7.7 or higher version

If you choose to install B1iSN server with Microsoft SQLServer 2008, then you need to prepare JDBC driver forMicrosoft SQL Server 2008 and SAP Java CryptographyExtension Jurisdiction Policy files

MS XML 4.0 (MS XML Toolkit) or higher

Preparing for InstallationBefore installing SAP Business One integration platform, you must perform the following preliminary steps:

To install and configure the database server, see the relevant installation guide and the helpdocumentation of the database product.

Install SAP Business One DI API (Java Connector).

For information, see Installation Guide for SAP Business One DIAPI.

On the Setup Type screen of the SAP Business One DIAPI InstallShield Wizard, select theCustom type.

To install the latest DI API version, on the Select Components screen of the SAP Business OneDIAPI InstallShield Wizard, deselect the DI API previous versions checkbox.

Set up the database.

If you are using MS SQL Server 2005 or 2008, make sure the database TCP/IP protocol isenabled.

In SQL Server 2005, the TCP/IP protocol is disabled by default


© SAP AG 2009 5

To enable the TCP/IP protocol in SQL Server 2005, proceed as follows:

i. Choose Start All Programs Microsoft SQL Server 2005 Configuration ToolsSQL Server Configuration Manager.

ii. On the SQL Server Configuration Manager screen, expand SQL Server 2005 NetworkConfiguration and choose Protocols for MSSQLSERVER.

iii. Right-click TCP/IP, and choose Enable.

iv. Restart Microsoft SQL Server 2005.

If you are using MS SQL Server 2005 with an instance, and you want to install SAP BusinessOne integration server on it, you must set the IP port to the default port value 1433.

To set the IP port in SQL Server 2005, proceed as follows:

i. Choose Start All Programs Microsoft SQL Server 2005 Configuration ToolsSQL Server Configuration Manager.

ii. On the SQL Server Configuration Manager screen, expand SQL Server 2005 NetworkConfiguration and choose Protocols for <instance name>.

iii. Open TCP/IP Properties by double-clicking TCP/IP, or by right-clicking TCP/IP andchoosing Properties.

iv. On the IP Address tab, in the section IPALL:

Leave TCP Dynamic Ports blank.

In TCP Port enter 1433.

During the installation of SAP Business One integration server, enter localhost as the servername, rather than localhost\instance name.

If you are using MS SQL Server 2008, make sure you have the JDBC driver for MS SQL Server2008 and the SAP Java Cryptography Extension Jurisdiction Policy files.

To download the SAP Java Cryptography Extension Jurisdiction Policy files, refer to SAP Note1240081.

If you are using MaxDB, make sure you have created a database user name SBOCOMMON.

To create a new user name SBOCOMMON, proceed as follows:

i. Choose Start All Programs MaxDB Database Studio.

ii. From the Database Studio screen, choose the Explorer tab, and select the databaseinstance on which you are going to install B1i.

iii. Log on to the database with the user name and password, which you defined during theinstallation of MaxDB.

iv. Choose the Users group, right click and choose New User.

v. On the new user screen, enter user name SBOCOMMON and set a password for it.

vi. Grant user SBOCOMMON the privilege to create and drop tables.

Install MSXML 4.0 SP2 or higher.

You can download it from www.microsoft.com/downloads by searching for MSXML.

http://www.microsoft.com/downloads


© SAP AG 2009 6

Some versions of Microsoft Windows install MS XML 4.0 during the installation of the operatingsystem. If the file msxml4.dll exists in the path <prompt>\WINDOWS\system32, it meansthat MS XML 4.0 is installed.


© SAP AG 2009 7

Installing SAP Business One integration ServerPrerequisites

Before you install SAP Business One integration server, make sure no Tomcat is installed on yourmachine. Setup will exit in case it detects Tomcat installed.

Before you install the B1iSN 2007 on MSSQL 2008 server, make sure that the Microsoft SQL ServerJDBC Driver 2.0 is available in a source directory on your machine.

The JDBC driver for MSSQL 2005 is not applicable for access to MSSQL 2008.

Before you install the B1iSN 2007 on MSSQL 2008 server, make sure that the SAP JavaCryptography Extension Jurisdiction Policy files are available in a source directory on your machine.

Procedure...

1. From the Technology folder, run setup.exe. The InstallShield Wizard screen opens.

2. On the welcome message, choose Next to continue the installation.

3. Enter your user name and company name; choose Next.

4. Choose Browse to set the installation path; and choose Next.

If you have ever installed any component of B1iSN 2007 on this machine before, the installation pathis not editable.

5. On the select components window, choose SAP Business One integration Server.

6. On the Start Setup window, choose Next.

7. Select the type of the database on which to install the B1iSN server.

8. If you choose MS SQL 2008, choose the source directory of JDBC driver and the SAP JavaCryptography Extension Jurisdiction Policy files.

9. Enter the database information (server, database name, user name, and password) to connect to thedatabase; choose Next. The application automatically tests the database connection.

Default information to connect to your database:

Database Type Server Database Name User Name

Microsoft SQL Server2005/2008

localhost SBO-COMMON sa

MaxDB localhost SBS SBOCOMMON

During the installation process, various progress screens appear.

10. To complete the installation of SAP Business One integration server, choose Finish.

ResultYou have successfully installed SAP Business One integration server on your computer:

To access the shortcut to SAP Business One integration Server, choose Start All Programs SAPBusiness One integration platform. From the shortcut menu, you can find the shortcut Administration.

After installation, the application automatically:

Installs the SAP Business One integration service


© SAP AG 2009 8

You find the services by choosing Start Control Panel Administrative Tools Services.

Forms the file structure under your destination folder:


© SAP AG 2009 9

SAP B1iSN 2007 EventSender, DI-Proxy Installation -Step by StepHardware and Software RequirementsRequirement Type Required by

componentsRequirement

Hardware requirements EventSender

DIProxy

1x Intel Pentium III

Minimum 512MB, 2 GB RAM (for typicalproduction usage)

500M free disk space

24x or higher CD-ROM

Software requirements DIProxy Please refer to SAP Business Oneinstallation guide for supported OS

SAP Business One SDK JavaConnector

Prerequisites If you install EventSender with the SAP Business One server that is based on MS SQL 2008 server,

make sure that the Microsoft SQL Server JDBC Driver 2.0 and the SAP Java Cryptography ExtensionJurisdiction Policy files are available in a source directory on your machine.

To download the SAP Java Cryptography Extension Jurisdiction Policy files, refer to SAP Note1240081.

The JDBC driver for MS SQL 2005 is not applicable for the access to MS SQL 2008.

Procedure...

1. From the Technology folder, run setup.exe. The InstallShield Wizard screen opens.

2. On the welcome message, choose Next to continue the installation.

3. Enter your user name and company name; choose Next.

4. Choose Browse to set the installation path; and choose Next.

If you have ever installed any component of B1iSN 2007 on this machine before, the installation pathis not editable.

5. On the select components window, choose SAP Business One integration EventSender or SAPBusiness One integration DI Proxy, multi-selection is supported.

6. On the Start Setup window, choose Next.

7. If you choose to install SAP Business One integration EventSender, select the database type of theSAP Business One server, which EventSender will work with.

If you choose MS SQL 2008, you need to choose the source directory of JDBC driver and the SAPJava Cryptography Extension Jurisdiction Policy files.

8. To complete the installation of SAP Business One integration EventSender and/or DI Proxy, chooseFinish.


© SAP AG 2009 10

Result After the installation of SAP Business One integration EventSender, you can access the shortcut

to SAP Business One integration EventSender, choose Start All Programs SAP BusinessOne integration platform EventSender. From the shortcut menu, you can find the shortcutSetup and Run.

The application automatically:

Installs the SAP Business One EventSender service

Creates a new folder EventSender under your destination folder

EventSender service is not started by default. You have to configure EventSender and thenstart the service.

To configure EventSender, go to the start menu, and then choose SAP Business Oneintegration platform EventSender setup.

After the installation of SAP Business One Integration DI Proxy, the application automatically:

Installs the SAP Business One DI Proxy service

Installs the SAP Business One DI Proxy Service Monitor service

Creates a new folder DI Proxy under your destination folder

DI Proxy service is started by default. You do not have to start it manually.


© SAP AG 2009 11

Uninstalling SAP Business One integration platformThis procedure uninstalls only the SAP Business One integration platform application.

To uninstall the database application, or to remove the database, you must perform the correspondingoperations.

Procedure...

1. Choose Control Panel Add/Remove Programs.

2. Select the application you want to remove from the list, and choose Change/Remove.

The SAP Business One integration platform applications include:



SAP Business One integration DI Proxy

3. Choose OK to confirm.

Remove any components does not affect any other components.


© SAP AG 2009 12

Appendix I: B1iSN Components Setup and DeploymentOptionsThis section contains information on which of the different components belong to SAP Business Oneintegration for SAP NetWeaver (B1iSN); where they should run; and how to set them up.

Components of the B1iSN SolutionThe B1iSN solution consists of the following component blocks:

B1iSN Server (B1i platform + B1iSN services)

B1iP B1 client components

B1iP R/3 client components

B1iSN ServerThe main solution component is B1iSN Server. It runs on a dedicated server, typically at the companyheadquarters. This server provides centralized control over all connected subsidiaries. Since alladministration is browser based, you can choose any computer with access to B1iSN Server to performadministration tasks.

The B1iSN server components include:

The B1iP server components:

B1iP runtime

Multiple B1iP Adapter


© SAP AG 2009 13

EventDispatcher

Apache TomCat Servlet Container

SAP Java runtime environment

JDBC driver to connect the database system

Database system (optional)

The B1iSN services:

B1iSN SIM

B1iSN BIUs (Integration Content)

All components, except the database system, are installed automatically with B1iSN 2007.

Database SystemThe B1iSN server can run with a local database system, installed on the same server; however, this is notmandatory. If the database system is running on a separate server, make sure that the connectivity in thenetwork is optimal.

The database vendor provides the JDBC driver. When the database system is MS SQL Server,the B1iSN installation CD automatically installs the JDBC driver.

EventDispatcher in the Central B1iSN ServerWith the new B1iP kernel (included in Release B1iSN 2005 PL 09 or higher and in Release B1iSN 2007),events from subsidiaries are sent to the central EventDispatcher. If you have a local B1iP server running,then typically, the local EventDispatcher sends the event; otherwise, the local EventSender sends the event.

EventDispatcher triggers the appropriate process relevant for the incoming event. The EventDispatcherregistry table (Event Subscriber) configures EventDispatcher. In the central B1iSN server, creating and thenactivating a BizPackage Instance automatically generates the registry.

If you use a local EventDispatcher in a subsidiary to dispatch between the subsidiary's individual integrationprocesses and B1iSN related processes, you have to maintain the registry of the local EventDispatchermanually.

B1iP B1 Client ComponentsTo interact with SAP Business One, B1iP provides components for enabling SAP Business One for messagebased communication. These components come with the B1iSN solution and with SAP Business One 2007or higher. They need to be installed and configured for each SAP Business One system.

The B1iP SAP Business One client components include:

B1 notification mechanism

EventSender

DI-Proxy

Event Dispatcher in a local B1iP server

B1 Notification MechanismThis mechanism is responsible for generating events in an event log table whenever a modification istriggered in SAP Business One, for example, when a new order is created. If you want to activate a business


© SAP AG 2009 14

scenario that sends data from SAP Business One when triggered by a modification in SAP Business One,then you need to activate this mechanism for the relevant company databases.

SAP Business One 2005

For SAP Business One 2005, the notification mechanism component is a stored procedure in the databasethat you choose for storing the event table during EventSender setup. It is generated automatically when youstart the EventSender setup. Once the notification mechanism is activated on a certain company database, itcollects all the events for all the objects in that company database.

SAP Business One 2007

For SAP Business One 2007, this functionality is inbuilt in the application. You control it by flagging a specifictable field, and you can switch it on/off, either completely or for a particular company database. Once youactivate the notification mechanism on a certain company database, it collects all the events for all theobjects in that company database.

The B1iEnabled field in the SCFG table of the SBO-COMMON database is the flag used to switch thenotification on/off. With the installation of B1 server tools, you get the B1 Service Manager. If you chooseEventSender (SAP Business One EventSender Service) or the local B1iP server (SAP Business Oneintegration Service) and select the Enable checkbox, you automatically switch on the notification mechanism.If you do not select the Enable checkbox then the notification mechanism remains switched off.

The ESEnabled field in the CINF table of a particular company database is the flag used to switch on/off thenotification for that particular company database. The setup of EventSender handles this automatically.

EventSenderThis service maintains the event table. In intervals of 3 seconds (3000 millisecond, you can change this inthe EventSender setup), it retrieves the events from this table and triggers the defined integration process.

If you want to activate a business scenario that sends data from SAP Business One when triggered by amodification in SAP Business One, then you need to install/configure/activate this service.

For one installation of SAP Business One, you run one EventSender to support all company databases.

You install EventSender in one of the following two ways: Automatically, with the installation of SAP Business One (only with Release 2007) With the B1iSN installation CD

B1iSN 2005 PL00, PL01 and PL02

You need to install EventSender with the B1iSN setup.

You need to install the full B1iSN Server application.

EventSender runs as a DOS batch (run.bat).

B1iSN 2005 PL03, PL04, PL05, PL06, PL07, PL08



EventSender runs as a DOS batch (run.bat). You can manually wrap EventSender as a MicrosoftWindows service by running the service.exe in the EventSender folder, with the parameter -install.

EventSender is installed as a service with startup type automatic and, therefore, is activated.

B1iSN 2005 PL09



EventSender is installed as a service with startup type automatic and, therefore, is activated.


© SAP AG 2009 15

B1iSN 2005 PL10 and higher

You need to install EventSender with the B1iSN setup. You have the option of installing EventSender only,not the whole B1iSN Server application.

You use the upgrade CD for patches and new installations. On the first screen, choose the option to upgradeEventSender, even if it is not installed. EventSender is then installed as a service with startup type automaticand, therefore, is activated.

B1iSN 2007 PL00, PL01 and PL02


You need to install the full B1iSN Server application. EventSender is installed as a service with startup typeautomatic and, therefore, is activated.

B1iSN 2007 PL03 and higher

You need to install EventSender with the B1iSN setup. You have the option of installing EventSender only,not the whole B1iSN Server application.

You use the upgrade CD for patches and new installations. On the first screen, choose the option to upgradeEventSender, even if it is not installed. EventSender is then installed as a service with startup type automaticand, therefore, is activated.

SAP Business One 2007 PL00

EventSender comes with the SAP Business One installation. EventSender is installed as a service withstartup type automatic, and, therefore, is activated.

SAP Business One 2007 SP1 and higher (planned)

EventSender comes with the SAP Business One installation. It is installed as a service with startup typedefined as manual and is de-activated. To enable the SAP Business One system to send out notificationevents, you need to change the startup type to automatic.

The following table provides an overview of the different versions:

Default Process Type Optional Process TypeProducts to Install

EventSenderInstallation

Method run type start type run type start type

SAP Business One 2004 - - - - -

SAP Business One 2005 - - - - -

SAP Business One 2007 PL00 with applicationMicrosoftWindows service automatic DOS batch manual

SAP Business One 2007 SP1and higher with application

MicrosoftWindows service manual DOS batch manual

B1iSN 2005 PL00 – PL02 with full B1iSN DOS batch manual - -

B1iSN 2005 PL03 – PL08 with full B1iSN DOS batch manual windows service automatic

B1iSN 2005 PL09 with full B1iSNMicrosoftWindows service automatic DOS batch manual

B1iSN 2005 PL10 and higher ES onlyMicrosoftWindows service automatic DOS batch manual

B1iSN 2007 PL00 – PL02 with full B1iSNMicrosoftWindows service automatic DOS batch manual

B1iSN 2007 PL03 and higher ES onlyMicrosoftWindows service automatic DOS batch manual


© SAP AG 2009 16

DI ProxyThe B1iSN server interacts with SAP Business One through the DI adapter, which is directly connected tothe DI API of SAP Business One.

The DI adapter interacts with the DI API in two ways:

The DI adapter and the DI API run on the central B1iSN server. The DI API is remotely connected tothe local database of SAP Business One.

The DI adapter plays the role of a central controller, while the detailed interaction between the DIadapter and the DI API is delegated to the local machine running DI Proxy.

The section Overall Subsidiary Landscape discusses the pros and cons of each option.

B1iSN 2007 PL01 or lower, and B1iSN 2005 PL08 or lower

DI Proxy is bundled with EventSender.

Installing and running EventSender also activates DI Proxy; however, that does not mean that the centralB1iSN server is necessarily using it.

B1iSN 2007 PL02 or higher, and B1iSN 2005 PL09 or higher

DI Proxy and EventSender are separate components. You install DI Proxy using the B1iSN installation CD.

As of Release B1iSN 2007 PL03 or higher, and Release B1iSN 2005 PL10 or higher, you have the option ofinstalling just DI Proxy. With earlier patches, you need to install the whole B1iSN Server application.


© SAP AG 2009 17

EventDispatcher in a Local B1iP ServerThe new B1iP kernel is included in Release B1iSN 2005 PL09, Release B1iSN 2007, and Release SAPBusiness One 2007. It lets you run a local B1iP server to cover the individual integration needs of asubsidiary or to interact with third parties from SAP Business One.

In such cases, it is not feasible for EventSender to send all events to the central B1iSN server, as someevents need to trigger the non-B1iSN related integration tasks. EventDispatcher runs on the B1iP server anddistributes events to the right processes.

B1iSN 2005 PL00 – PL08

No EventDispatcher is available.

EventSender sends all events directly to the central B1iSN server.

SAP Business One 2007 PL00 or B1iSN 2007 PL00, PL01

EventDispatcher is available.

You can use it for dispatching locally between multiple integration solutions, but not for dispatching betweenthe central B1iSN server and additional local integration solutions. Typically, you configure EventSender tosend all events directly to the B1iSN server.

SAP Business One 2007 SP1 and higher (planned),B1iSN 2005 PL09, B1iSN 2007 PL02 and higher

EventDispatcher is available, with two configuration options.

You can configure EventSender to send all events either directly to the central B1iSN server or to the localEventDispatcher.

Use the latter option only if you have other B1iP-based integration solutions running in the subsidiary.EventDispatcher then distributes the events among the different integration solutions, one of them being thecentral B1iSN server.

You configure EventDispatcher in the EventDispatcher registry table (Event Subscriber).

B1iP R/3 Client ComponentsThe B1iSN solution provides business scenarios for downloading customizing data from R/3. Thesescenarios are not supported from the R/3 side; therefore, B1iSN provides an ABAP function for this purposethat needs to be set up manually in the R/3 system,. For more information, see the scenario guide of this usecase.


© SAP AG 2009 18

Appendix II: Deployment ScenariosThis section describes the different possibilities for combining the previously described components.

Choosing a Scenario: ConsiderationsThe following aspects influence which scenarios, or mix of scenarios, you can use:

Overall subsidiary landscape

Local integration scenarios in the subsidiary

Version of B1iP components

Overall Subsidiary LandscapeWhen choosing a scenario, you need to consider and differentiate between the following two landscapes:

Homogeneous B1 Landscape

In a homogeneous B1 landscape, all B1 installations run the same DI-API version.

The DI-API version is typically bundled to an SAP Business One release. The connectivity betweenthe central B1iSN server running in the headquarters, and the subsidiaries, is an importantconsideration. The scenarios for a homogeneous B1 landscape require good connectivity to allsubsidiaries, which means low latency and high bandwidth.

In a scenario setup using a homogeneous B1 landscape, it is not possible to run different SAPBusiness One releases in different subsidiaries. If you want to upgrade to a newer SAPBusiness One release in the future, you need to consider this aspect in the planning.

Heterogeneous B1 Landscape

In a heterogeneous B1 landscape, each B1 installation can run a different DI-API version.

The DI-API version is typically bundled to an SAP Business One release. If your connectivity to atleast one subsidiary is not good, that is, you have either high latency or low bandwidth, choose thislandscape.

If you plan, at any time in the future, to run different B1 releases in your subsidiaries, or toupgrade to higher SAP Business One releases, you should choose scenarios for theheterogeneous B1 landscape.


© SAP AG 2009 19

Local Integration ScenariosB1iSN supports the business processes between the back-end systems running in the headquarters and theSAP Business One applications running locally in the subsidiaries.

B1iP is a generic integration platform, not used only for B1iSN.

You can use the B1iP server to support the individual integration needs of a particular subsidiary.

SAP Business One or integration products developed by SAP partners (add-ons) can use the B1iP forcertain use cases related to the integration of a particular subsidiary into its ecosystem.

Typically, all SAP Business One events are sent to the B1iSN server. If you have a subsidiary runningadditional integration logic, which is triggered by SAP Business One events, you need a local eventdispatcher for this subsidiary. As such, consider the scenarios with the option “B1 with local B1iP and EventDispatching.”

Version of B1iP ComponentsWhen deciding on a scenario, you need to consider the version of the B1iP server, specifically the B1iP B1client components, which are installed at the subsidiary on the SAP Business One server.

The B1iP components can be installed automatically with Release SAP Business One 2007 or with a partneradd-on using B1iP; or explicitly, as part of the B1iSN installation.

Even if the local installation is done through the B1iSN installation, the subsidiary cannot runthe B1iSN server.

When you consider your scenario options, you need to differentiate between the two main B1iSN versioncombinations:

B1iSN 2007 PL01 or lower and B1iSN 2005 PL08 or lower

B1iSN 2007 PL02 or higher and B1iSN 2005 PL09 or higher

The main differences lie with event dispatching and with the split of DI Proxy and EventDispatcher into singlecomponents. Both functions are available only with the newer version.

The older version bundled the two functions into one component (EventSender). With the new version, youalso have an option to install/upgrade the single components individually.

The Deployment Scenarios in DetailThe table below provides details for the six supported deployment scenarios. After considering all theimportant aspects, we recommend scenarios 01 and 02.

Scenario B1Landscape

B1iSNComponents

Local EventDispatching

01 Heterogeneous New No

02 Heterogeneous New Yes

03 Heterogeneous Old No

04 Homogeneous New No

05 Homogeneous New Yes

06 Homogeneous Old No


© SAP AG 2009 26

Icons and Typographic ConventionsIcons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, pathsand options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics andtables.

EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individualkey words of a programming language, when surrounded by bodytext, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and theirpaths, messages, source code, names of variables andparameters as well as names of installation, upgrade anddatabase tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) orthe ENTER key.

Example text Exact user entry. These are words or characters that you enter inthe system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replacethese words and characters with appropriate entries.


© SAP AG 2009 27

Copyrights, Trademarks, and Disclaimers© Copyright 2009 SAP AG. All rights reserved.

The current version of the copyrights, trademarks, and disclaimers athttp://service.sap.com/smb/sbocustomer/documentation is valid for this document.

http://service.sap.com/smb/sbocustomer/documentation

installation guide sap business one integration

Documents