Integration framework for SAP Business One 01 Development Environment

Integration framework
for SAP Business One

Guide 01

Development Environment

Author: Heinz Pauly Version: 1.0 Date: June 21, 2010

-1-

Integration framework for SAP Business One 01 Development Environment

Content
1. The BizStore ................................................................................................3 1.1 The Physical Storage of B1i ...................................................................3 1.2. The Logical Storage of B1i ....................................................................3 2. External Development Environment.............................................................5 2.1 Development Environment in the File System........................................5 2.2 Syntax Check and Intellisense ...............................................................6 3. Internal Development Environment via WebDAV.........................................7 3.1 What is WebDAV?..................................................................................7 3.2 BizStore Access under Windows Explorer .............................................7 3.3 High efficient Development with WebDAV support.................................7 3.4 How to activate WebDAV enablement ...................................................8 3.5 WebDAV and Authentication ..................................................................9 4 Document Handling ....................................................................................10 4.1 Upload a Document..............................................................................11 4.2 Download a Document .........................................................................12 4.3 List Documents of the BizStore ............................................................13 4.4 Delete Documents in the BizStore........................................................15 4.5 Import a ZIP with multiple Documents..................................................17 4.6 Export a ZIP with multiple Documents..................................................19 4.7 Import a Scenario Package ..................................................................22 4.8 Export a Scenario Package ..................................................................23 5. The B1i XSLT Library.................................................................................24 6. The B1i Execution Tools ............................................................................27 6.1 Execute Stylesheet...............................................................................27 6.2 Execute BizFlow...................................................................................27 6.3 Execute IPO-Step.................................................................................27 6.4 Put msg in Queue.................................................................................27 7. Configuration of the Development Environment.........................................27 7.1 Framework Configuration .....................................................................27 7.2 Technical Configuration........................................................................27 Copyrights, Trademarks, and Disclaimers .....................................................28

-2-

Integration framework for SAP Business One 01 Development Environment

1. The BizStore
1.1 The Physical Storage of B1i
The complete B1i Framework (program code and data), including customer extensions is stored in the B1i database in the following 8 database tables. This is similar to the SAPs R/3 technology where the ABAP program code and data is stored in the database. BZSTDOC BZSTIDXH BZSTIDXP DBQITEMS DBQSTREAMS XCLTRINQ XCLTRLOG XCLTRPOS

This persistency is named BizStore. The complete framework (program code, and data) consists out of documents, typically in xml format (beside some gif/jpg) which are covering e.g. repository entries or instructions how to map a concrete message. All theses documents are stored in the BZST* tables, each document is one record in these tables.

1.2. The Logical Storage of B1i

The chapter 1.1 describes the physical, low level storage of the documents of the B1i framework, which is an internal storage format only. This chapter is explaining the logical storage on top of this physical storage. This logical view is the structure for you to work with. This logical view is a 2-level hierarchy. The directories in the first level are named dataset; the directories of the second level are named group. In the groups youll find all documents. The names of the datasets are following the Inverse Domain URL Convention (e.g. com.sap.b1i.system). The B1i Framework consists out of multiple datasets which have multiple different groups. Pre-shipped with the installation of the B1i Framework there are many datasets, groups and documents available already. During your work adational dataset, groups and documents will be created. Beside the physical name, a document in the BizStore can have multiple logical names. A logical name is called alias. The location of a document is uniquely defined by the BizStore-URI, which consists out of the full path /dataset/group/document. -3-

Integration framework for SAP Business One 01 Development Environment

With the installation the following datasets will be available: com.sap.b1i.vplatform.ide (administration console) com.sap.b1i.vplatform.repository (repository) com.sap.b1i.vplatform.runtime (runtime functionality) com.sap.b1i.vplatform.system (APIs) com.sap.b1i.vplatform.ui (ui functionality) com.sap.b1i.system.sld (system landscape admin) com.sap.b1i.system.sld.api (system landscape admin) com.sap.b1i.system.sld.directory (system landscape admin) com.sap.b1i.system.sld.repository (system landscape admin) com.sap.b1i.system.eventdispatcher (B1 event dispatcher) com.sap.b1i.system.eventdispatcher.api (B1 event dispatcher) com.sap.b1i.internal (B1i library) com.sap.b1i.internal (B1i technology) com.sap.b1i.internal.xc (B1i technology) com.sap.b1i.system (B1i technology) com.sap.b1i.system.cc (B1i technology) com.sap.b1i.system.uiframework (B1i technology) com.sap.b1i.system.xc (B1i technology) com.sap.b1i.system.xc.iodata (B1i technology) com.sap.b1ip.system.cc (B1i technology)

During runtime, the following datasets will be created: com.sap.b1i.vplatform.directory (directory) com.sap.b1i.vplatform.scenarios.authen (authentication functionality) com.sap.b1i.vplatform.scenarios.design (scenario packages) com.sap.b1i.vplatform.scenarios.setup (setup specification) com.sap.b1i.b1imessage.errorinbox (error inbox) com.sap.b1i.b1imessage.logs (message log) com.sap.b1i.system.eventdispatcher.directory (B1 event dispatcher)

-4-

Integration framework for SAP Business One 01 Development Environment

2. External Development Environment

There are two options for the Development Environment. The internal Development Environment is directly in the B1i BizStore whereas the external Development Environment is in your File System. Typically you should go for the internal Development Environment. Only in cases you cannot support the requirements, you should go for the External Environment.

2.1 Development Environment in the File System

Corresponding to the explanations in chapter 1, your development environment needs to be a folder structure of two levels, which represents your individual XML documents in the required dataset/group structure. For your development environment, please create a folder, e.g. my_B1i on any place in the overall filesystem/folder structure of your computer. This folder will contain your complete development. Please create sub-folder in the overall my_B1i folder for the datasets, which are involved in your development. Inside the dataset folders, please create sub-folder for the groups, which are involved in your development. There is no need for completion. Its sufficient to create only the datasets and groups that you need. Please make sure, that the folder names are exactly the same as required in the BizStore. Now you can create the needed XML documents in the particular group folders. To edit the XML documents you can use any editor, its strongly recommended to use an XML editor as this editor can validate your input.

As your Development Environment is external in the File System, you need to exchange the relevant documents once in a while. To exchange the data between the BizStore and the File System, you will use the administration console of the B1i Framework. How to work with the tools is described in chapter 4.

-5-

Integration framework for SAP Business One 01 Development Environment

2.2 Syntax Check and Intellisense

If you are working directly in the xml documents, its always recommended to use the syntax check and the automatic completion via XML schema validation (Intellisense). This avoids syntax errors in your definition from beginning on and helps you in choosing only supported values for particular tags. To use this powerful functionality, you need to provide the schema definition documents (XSD) in your development environment.
/com.sap.b1i.vplatform.repository/xsd/*.xsd

Please download these xsd documents with the administration console (please refer to chapter 4) and make them available in your development environment (in the folder e.g. my_B1i). If you want to save an XML document, your XML editor will notify you in case, the xsd documents are missing. If you want to store the XML document without validation against the xsd documents, you need to choose the option save anyway.

-6-

Integration framework for SAP Business One 01 Development Environment

3. Internal Development Environment via WebDAV

3.1 What is WebDAV?
WebDAV is a standard interface specification to expose data. If a persistency supports WebDAV as a server, you can use all standard software, which supports WebDAV as a client to access the data. The B1i BizStore supports WebDAV as a server. This allows you to access the datasets, groups and documents from the B1i BizStore with all webdav clients, e.g. the Windows Explorer. In this case you can work with the datasets and groups like you work with folders and you can work with documents like you work with files in the file system. Please refer to chapter 3.2 BizStore Access under Windows Explorer If you choose an XML editor, which supports WebDAV (e.g. Altova XMLSpy) you will have a high efficient development environment. Please refer to chapter 3.3 High efficient Development with WebDAV support

3.2 BizStore Access under Windows Explorer

In general, you can use your Windows Explorer to transfer documents between your Development Environment and the BizStore in the same way as if you would transfer files between folders of your file system. So you can just list all your documents in the normal Windows Explorer tree, you can drag and drop, delete and create the documents, the groups and the datasets. In this case you can ignore the chapter 2. There are two main restrictions which you should know. As the normal file system doesnt support the concept of alias, documents with alias are not exposed via WebDAV. This means these documents will not be visible (e.g. the message log documents). Please notify, that whenever you did some changes in the scenario definition and functionality, its not enough to drag and drop the modified documents to the B1i Bizstore. In this case please run the Scenario Package activation/setup again.

3.3 High efficient Development with WebDAV support

As the B1i Framework is a model driven, declarative approach, the development effort is reduced to a minimum. Nearly all development work is done by definitions in particular XML documents. The only development part is the XSLT document, belonging to the Business Integration Unit (vBIU). Changes in the XSLT documents will have immediate affect without any re-activation. Therefore, its ideal, to work -7-

Integration framework for SAP Business One 01 Development Environment

directly with the active documents in the B1i BizStore. With your editor, you just click the [Save] button, the B1i Framework will immediately re-load the document and the new functionality is active with zero development roundtrip which is the most efficient way of programming. How to work with a document in an XML editor, please check the hints in following chapter.

3.4 How to activate WebDAV enablement

Its highly recommended to switch on WebDAV during your design- and development phase. As you can see the huge benefits are: Easy transfer of documents between your Development Environment and the BizStore High efficient development in XSLT directly in the BizStore with zero development roundtrip

Its also recommended to switch it on for trouble shooting to get very fast an overview of the situation. For the normal runtime of the project, you should switch it off to avoid that users manipulate documents by accident.

Switch on WebDAV in the B1i Framework Activation of WebDAV is very easy. Please open the overall configuration file for the B1i Framework. Its a text file in the file system in the basis directory of B1i, typically in a folder C:\ ... \tomcat\webapps\B1iXcellerator. The name of this file is xcellerator.cfg. You open this file with a normal editor, e.g. Notepad. The first section in this file is named #== Xcellerator-Parameters: === Please set the parameter xcl.webdav to full. In case the parameter doesnt exist, please add it to the configuration file at any place in this section to introduce the WebDAV parameter and to switch it on. xcl.webdav=full After changing settings in the xcellerator.cfg, you always need to re-start the B1i Framework. Please start the Windows Services. Control Panel -> Administrative Tools -> Services Windows Services opens and displays all registered services. The B1i Framework is registered with the name SAP Business One Integration Service. Please select this service by clicking on the name and re-start it with the functions left to it in the upper corner.

-8-

Integration framework for SAP Business One 01 Development Environment

Activate BizStore access via Internet Explorer To enable access via your Windows Explorer, please open your My Network Places (just select the entry in the tree of your Internet Explorer) and run the Add Network Places wizard. Please add the Internet or network address of the B1i BizStore, which is http://localhost:8080/B1iXcellerator/exec/dummy After activation, you will find your B1i BizStore in your Windows Explorer tree, directly under the first level tree node My Network Places. You need to activate it only once. Next times, when you open the Windows Explorer, you will always have access to the B1i BizStore. Remark: In case the Add Network Place function doesnt work as expected under MS Windows 2003 Server, the reason could be that the Microsoft Web Folders are not installed by default. In this case please download and install the Microsoft Web Folders.

Work with a BizStore document directly in your XML Editor. The B1i Framework allows you to define the integration scenarios by configuration and with the inbuilt graphical design user interfaces. For developing the transformation in XSLT, SAP recommends to load and edit the generated XSLT by an XML editor of your choice. SAPs recommendation is: The XML editor should support WebDAV. This allows you to direct edit and store a BizStore document. As the change will take effect immediately, you will have zero development roundtrip. The XML editor should support projects. Especially in case you have to develop and maintain multiple integration scenarios, a project will allow you to administer in a structured way all relevant documents.

To open a BizStore document via WebDAV, typically XML editors provide you an option to open a URL. In this case please type in the network address of the B1i BizStore (http://localhost:8080/B1iXcellerator/exec/dummy) and browse for the appropriate document.

3.5 WebDAV and Authentication

During runtime, the B1i Framework is using an authentication mechanism to protect the B1i BizStore against unauthorized access. The B1i Framework is is using basic authentication. Also the WebDAV access is under control of the authentication. Typically, an XML editor supports WebDAV access with authentication by providing the possibility to define user/password information when you open a document from the BizStore.

-9-

Integration framework for SAP Business One 01 Development Environment

4 Document Handling
Please use the administration console of the B1i Framework for the document handling between your File System and the B1i BizStore. You start the Administration Console in the Windows Internet Explorer with the following url: http://localhost:8080/B1iXcellerator/exec/dummy/com.sap.b1ip.system.cc/bfd/ AdminConsole.bfd?!defdoc=/com.sap.b1i.vplatform.ide/ui/vIDE.xml In case the B1i Framework is running on another computer in the network, please replace localhost with the name or ip address of the server. Remote access is disabled per installation. Please refer to chapter 7.2. how to switch it on.

Before you can use the administration console of the B1i Framework, you need to logon. Pre-configured with the installation, the user name is B1iadmin and the password is B1iadmin. Its strongly recommended to change the password and/or to add new accounts. Please refer to reference guide 04, chapter 4.4. The following functions are available for document handling: Upload a document (File System -> BizStore) Download a document (BizStore -> File System) List Documents in the BizStore Delete documents in the BizStore Import a zip, containing multiple documents (File System -> BizStore) Export a zip, containing multiple documents (BizStore -> File System Import a Scenario Package (File System -> BizStore) Export a Scenario Package (BizStore -> File System) - 10 -

Integration framework for SAP Business One 01 Development Environment

4.1 Upload a Document

This function is used to copy a single XML document from the file system to the B1i BizStore. If the document already exists, it will be overwritten. Control Center Maintenance BizStore Upload

Payload-Type Settings Typically, the document payload gets detected automatically by its extension (xml, bfd, ipo, xsl, ) and there is no need to explicitly define it. By supplying explicit payload-type conversion settings, it is possible to supersede the default detection and settings. This e.g. is necessary for files with a missing / wrong / unknown name-extension that shall be treated as a specific (known) payload-type. The settings are specified in a 'key=value' manner, separated by comma. For a further description of the explicit settings that can be done here, please also refer to the description of the various inbuilt payload-type converters of the BizProcessor in the Programmer's Reference (Control Center Development BPC Reference). File-Name With the Browse button, you can choose the document from the file system.

- 11 -

Integration framework for SAP Business One 01 Development Environment

BizStore-URI The Upload function detects automatically the BizStore-URI and will propose it, composed out of the document's name. Optional you can overwrite it. If you want to create a document with an alias, please edit the BizStore-URI and add the alias in parenthesis, e.g. /dataset/group/document.xml(alias_1). [Submit!] Please click the Submit! button to trigger the upload. After the upload you will get the status of the operation.

4.2 Download a Document

This function is used to copy a single XML document from the B1i BizStore to the file system. Control Center Maintenance BizStore Download

BizStore-URI You can type in the correct URI or you can use the button on the right to select first a dataset, then the group and then the document, you want to download.

- 12 -

Integration framework for SAP Business One 01 Development Environment

dataset group alias document

name of the dataset, where the document is stored name of the group, where the document is stored alias of the document, default is unified name of the document

Payload-Type Conversion By stating that no payload-type conversion shall happen, the document will be retrieved as it is in the BizStore in its internal XML-representation. Payload-Type Settings By supplying explicit payload-type conversion settings, it is possible to supersede the default settings. This e.g. is necessary for files with a missing / wrong / unknown name-extension that shall be treated as a specific (known) payload-type, or if some details for the conversion shall be adjusted. The settings are specified in a 'key=value' manner, separated by comma. For a further description of the explicit settings that can be done here, please also refer to the description of the various inbuilt payload-type converters of the BizProcessor in the B1iP Programmer's Reference (Control Center Development BPC Reference).

Please click on the icon left beside the text Selection Criteria. This initiates the tool to open a new window. [Submit!] Please click the Submit! button to trigger the download. A new browser window will open with the retrieved document. Please choose the browser functions File Save As to store the document in the right location in your development environment.

4.3 List Documents of the BizStore

This functionality is creating a list of selected B1i BizStore documents. All documents are listed in a window. Per click on the document name you can open a new browser window with the selected document.

Control Center Monitoring

BizStore Directory

- 13 -

Integration framework for SAP Business One 01 Development Environment

You have the following input fields to define the dataset, the group and the document in the BizStore. With the Browse buttons behind the fields you can select the appropriate entry from a list. Constrain to dataset Name of the dataset you want to list. If the other fields are empty, the complete dataset will be listed. Constrain to group Name of the group you want to list in the dataset that you defined. If the other fields are empty, the complete group of the selected dataset will be listed. Constrain to Index-Alias Name of the alias of the document you want to list in the dataset and the group that you defined. Constrain to Document-Name Name of the XML document you want to list in the dataset and the group that you defined.

Please click on the icon left beside the text Selection Criteria. This initiates the tool to open a new window.

- 14 -

Integration framework for SAP Business One 01 Development Environment

[Submit!] Please click the Submit! button to display the list with the selected documents.

Youll see the total number of documents listed in the header together with the selection criteria. All documents are listed in a table in the following format: dataset group ualias name stored size Name of the dataset where the document is located Name of the group where the document is located Alias of the document Name of the document Timestamp of last modification in the BizStore Size of the document in byte

In addition the list contains the BizStore-URI URL for each document which allows you to open the document by clicking the link.

4.4 Delete Documents in the BizStore

In case you uploaded a wrong document to the BizStore, this function helps you to delete the document in the BizStore. With this function you can also delete a complete dataset or group. So, please be careful in using it. - 15 -

Integration framework for SAP Business One 01 Development Environment

Control Center Maintenance

BizStore Delete

You have the following input fields to define the dataset, the group and the document in the BizStore. With the Browse buttons behind the fields you can select the appropriate entry from a list. Constrain to dataset Name of the dataset you want to delete. If the other fields are empty, the complete dataset will be deleted. Constrain to group Name of the group you want to delete in the dataset that you defined. If the other fields are empty, the complete group of the selected dataset will be deleted. Constrain to Index-Alias, Name of the alias of the document you want to delete in the dataset and the group that you defined. Constrain to Document Name of the XML document you want to delete in the dataset and the group that you defined.

- 16 -

Integration framework for SAP Business One 01 Development Environment

4.5 Import a ZIP with multiple Documents

In addition to the actions, dealing with single documents, the B1i Framework supports the ZIP protocol. This functionality is used to exchange archives of multiple documents. SAP is providing upgrades and patches and also new Scenario Packages in this format. It is also used by SAP partners to provide Add On functionality, e.g. Scenario Packages.

Maintenance

ZIP Import

The functionality imports a .zip -archive to the BizStore and expands it there, possibly using another dataset as specified in the archive.

Choose archive Please click the Browse button of this field and select the zip file from your file system. The file specification of the zip file is carried over into the field. (Relocate to dataset) In case you import one dataset only and you want to change the name of the destination dataset, you type in the name in this field. Typically this field is empty and the datasets and groups get created with the names of the directories.

- 17 -

Integration framework for SAP Business One 01 Development Environment

Preserve existent docs Existing documents of the dataset won't be deleted, but yet existing ones will be overwritten, depending on the setting whether to preserve them or not. Prevent import on erroneous XSL-stylesheets If the import of the archive will be prevented on any contained erroneous XSLstylesheet, no file of the archive will be imported if at least one of such a XSLstylesheet was found: An erroneous XSL-stylesheet is a stylesheet that contains namespace-declarations in its root-element that never are used explicitly (means, that are not visible on XML-level) within the stylesheet. As the XML-processor is not aware of that on disassebly of the archive, it won't supply those unused namespace-declarations to the written targetdocuments then. If such a namespace then later on would be used implicitly (as e.g. referenced within textual XPath-expressions on execution of the stylesheet), a runtime error would occur, as the namespace cannot be resolved by the XSLT-processor then. In order to force the inclusion of such an implcitly used namespace, please e.g. supply an (empty) attribute within the root-element that is bound to the particular namespace. Assume file-system friendly naming Default to import upgrades/patches from SAP. If a file-system friendly encoding of the entry-names in the archive will be assumed, it is possible in this way to omit file-name extensions w/o the loss of payload-type information and to supply distinct alias-information w/o having sacrificed the usability of the document in the file-system. In such a case, the file-names must have been composed in the following way in order to achieve the particular result in the BizStore: (BizStore <-> File-System) hugo <-> hugo..ext hugo(alias) <-> hugo(alias)..ext hugo.ext <-> hugo.ext hugo.ext(alias) <-> hugo(alias).ext

Unescape unsafe URL-chars in names If an unescaping for unsafe URL-characters encoded within the components of the entry-name shall be performed, this typically could be necessary when the archive formerly was created by B1i and if the entry-names of the archive originally contained such unsafe characters.

Controlled import via processing Instructions in documents There do exist several import directives on a per document level that can be stated via processing-instructions to a particular document (note that all of the enlisted processing-instructions have to reside on the hierarchy-level below of the root-element; only the first one of each kind will be considered):

- 18 -

Integration framework for SAP Business One 01 Development Environment

<?com.sap.b1i.system_import protect?> It is possible to state whether a particular already existing document shall be protected from being overwritten by its imported version. This can be stated eiher by the document to be imported: <?com.sap.b1i.system_import protected?> Alternatively, this also can be stated by the already existing document. <?com.sap.b1i.system_import force?> Also, it is possible for the to be imported document to state whether it shall enforce an overwriting of an already existing document, no matter what the directive for the already existing document is (if it has any at all). <?com.sap.b1i.system_autorun <URI>?> As another feature, it is possible to state URI's in documents to be imported that shall be auto-run in new Browser windows after the import of the whole archive has happened: This can be faciliated by stating as many processing-instructions as needed. Note that if relative URI's are specified, they are resolved to HTTP URL's relative to the particular document's HTTP-exposed BizStore-URI. Absolute URL's do not need such a resolving, they will be invoked as they are.

Using the Import functionality for your own documents To use this function, first you need to archive all relevant documents, including all sub folders into one zip file. Please make sure, that your zip application is supporting relative path and switch it on; typically this is switched on by default.

4.6 Export a ZIP with multiple Documents

With this function, you can export complete datasets with all included groups and documents from the BizStore to the file system. All the documents will be provided in one zip file, including a two level hierarchy with relative directory information. The name of the zip file is always export.zip. Please unpack this zip file in your appropriate location, e.g. in your development environment. To unzip the archive choose the options to create sub directories with relative path information, typically set as default.

Control Center Maintenance

BizStore Export

- 19 -

Integration framework for SAP Business One 01 Development Environment

dataset You can type in a dataset or you can use the button on the right to select a dataset, you want to export. group You can type in a group or you can use the button on the right to select a group, you want to export. Include Alias Default setting is to export the documents with no explicit alias (alias=unified) only. In case you want to export also documents with explicit alias, you can specify the alias names in the field Include Alias. In this case, the documents will include the alias in parenthesis, e.g. document(alias).xml Exclude Alias Default setting is to export the documents with no explicit alias (alias=unified) only. In case you want to export documents without explicit alias, you can specify the alias names in the field Exclude Alias. In this case, the documents will exclude the alias in parenthesis, e.g. document(alias).xml Perform file-system friendly naming A file-system friendly encoding of the entry-names in the archive allow to omit file-name extensions w/o the loss of payload-type information and to supply distinct alias-information w/o having sacrificed the usability of the document in the file-system. - 20 -

Integration framework for SAP Business One 01 Development Environment

In such a case, when the BizStore document-names have been composed in the following way, it will be achieved the particular result in the File-System: (BizStore <-> File-System) hugo <-> hugo..ext hugo(alias) <-> hugo(alias)..ext hugo.ext <-> hugo.ext hugo.ext(alias) <-> hugo(alias).ext

[Submit!] After clicking the Submit button, a zip file with the name export.zip gets created. The browser window Download will pop up. Please click the button Save to save the export.zip file to the desired location in your file system.

- 21 -

Integration framework for SAP Business One 01 Development Environment

4.7 Import a Scenario Package

This functionality allows you to import a complete Scenario Package. It can be a Scenario Package from SAP, from an SAP partner or an own package, developed in the customer namespace. You can also use the standard Import function, described in chapter 4.5.

Scenarios

Scenario Package Import

Name of the Scenario package zip file Please click the Browse button of this field and select the zip file from your file system. The file specification of the zip file is carried over into the field. [Submit!] Please click this button to import the zip archive. After the import you will get a list of all imported documents.

- 22 -

Integration framework for SAP Business One 01 Development Environment

4.8 Export a Scenario Package

This functionality allows you to export a complete Scenario Package. It can be a Scenario Package from SAP, from an SAP partner or an own package, developed in the customer namespace.

Scenarios

Scenario Package Export

Scenario Package Identifier Please click the button of this field and select the Scenario Package you want to export as a zip file to your file system. Add test messages If you check this box, possible existing test messages will be included. Default this box is unchecked.

[Submit!] Please click this button to trigger the export. After clicking this button, a zip file with the name Scenario_Export.zip gets created. The browser window Download will pop up. Please click the button Save to save the export.zip file to the desired location in your file system.

- 23 -

Integration framework for SAP Business One 01 Development Environment

5. The B1i XSLT Library

For frequently used tasks in the area of transformation, the Integration framework provides a library to be used inside your XSL stylesheets. The following library functions are available: String Operations Date-Time Functionality System Functionality SAP Business One

Please use the administration console of the Integration framework to check the available functions. Help XSLT Library

Library functions are called templates in XSL. To have the templates available for your usage, you need to include the library document by using the include command at the end of the XSL.
<xsl:template name="transform"> ... </xsl:template> <xsl:include href="../../co m.sap.b1i.system.lib/xsl/string.xsl"/>

- 24 -

Integration framework for SAP Business One 01 Development Environment

The String operations are providing some very helpful functions to manipulate strings, respectively to retrieve some information from them, e.g. to delete leading zeros in a string. The Date/Time operations are providing functions around the date and time. E.g. you can retrieve the current date and time and it allows you to calculate some special dates or to provide formatted output. The System operations are more technical, e.g. to generate a globally unique identifier (GUID). The drop-down list displays all available libraries. Please choose the library you are interested in. You can test the library, available in your installation directly by clicking the Test button. Click the Load Docu button to open the documentation. The documentation displays a list of all existing templates with a short description. All templates are starting with the abbreviation b1ilib., followed by the actual name.

- 25 -

Integration framework for SAP Business One 01 Development Environment

At the beginning of the documentation, the exact include command is given. Just copy it from the documentation and paste it to the appropriate place in your XSL stylesheet. Without this include instruction, the template will not be accessible during the runtime and a runtime error will occurs.

If you are interested in a particular functionality, just click on the name which will position the document to the detailed description. E.g. if you are interested in detailed information about the template b1ilib.today_minus, just click on the name to get information about how to call it, a detailed description, the parameters, the default settings and a usage example. The Usage-Example is very helpful because you can just copy it to paste it directly to your XSL stylesheet.

With Back to Top you navigate back to the overall list. If you want to use a template, just copy the Usage-Example from the documentation and paste it into your XSL stylesheet.

- 26 -

Integration framework for SAP Business One 01 Development Environment

6. The B1i Execution Tools

Short description of IPO, BFD, XSL, queues

6.1 Execute Stylesheet 6.2 Execute BizFlow 6.3 Execute IPO-Step 6.4 Put msg in Queue

7. Configuration of the Development Environment

7.1 Framework Configuration
Screen

7.2 Technical Configuration

Xcellerator.cfg

- 27 -

Integration framework for SAP Business One 01 Development Environment

Copyrights, Trademarks, and Disclaimers

Copyright 2010 SAP AG. All rights reserved. The current version of the copyrights, trademarks, and disclaimers at http://service.sap.com/smb/sbocustomer/documentation is valid for this document.

- 28 -