BIS Developer Studio Installation

August 21, 2008

Table of Contents

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.2.1 The BIS Developer Studio Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
2.2.2 The BIS Process Designer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 First Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4 Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5 De-Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1.1 Error Message No JDK found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1.2 Error Message No Developer Studio found before installing this plug-in . . . . . . . . . . . . . 21
6.1.3 Error Message Error opening file for writing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1.4 Error Message after Starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.2 Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Copyright (c) 2008 SEEBURGER AG (http://www.seeburger.de). All rights reserved.

If (registered or pending) trademarks are named in this document, the rights of the respective
proprietors apply.
Note: False configuration and/or improper use of communication components may cause high
costs. Also consider configuration changes initiated by your telecommunication provider.
SEEBURGER is not liable for related additional costs.
Note: We expressly declare that the document "SEEBURGER Legal Information" (delivered
also with your BIS installation media) is part of this documentation.

BIS Developer Studio Installation 1

Figures

2-1 Welcome screen of the BIS Developer Studio Setup Wizard 6

2-2 Previous installation found 7
2-3 VM List 8
2-4 VM Selection 8
2-5 Choose Install Location (Studio) 9
2-6 Choose Start Menu Folder 10
2-7 Welcome Screen of BIS Process Designer's setup procedure 11
2-8 Choose Install Location (Plug-in) 11
3-1 Workspace Selection 13
3-2 BIS Developer Studio Java Perspective 14
3-3 Process Designer Perspective 15
3-4 New Project Wizard 16
3-5 Process Designer Help 18
6-1 Error Message in Case of Missing JRE/JDK 21
6-2 Error Message in Case of Missing BIS Developer Studio 22
6-3 Error opening file for writing (cutout) 22
6-4 Sample Error Message after Startup 22

BIS Developer Studio Installation 2

1 Overview

BIS Developer Studio is an integrated development environment (IDE) for the creation of
processes and components for SEEBURGER BIS 6, which is a B2B process management
system.
In this manual, you learn how to install, update and uninstall the BIS Developer Studio with the
BIS Process Designer Plug-in.
The installation of the BIS Developer Studio and the BIS Process Designer Plug-in is
recommended for computers of process analysts and developers. Please keep in mind that the
BIS Developer Studio is licensed per seat. It can communicate with an existing SEEBURGER
BIS 6 installation over the network. You may also want to set up a central repository to allow
team work with a supported version control system (CVS via SSH).
Please refer to the Updates (page 19) section if you want to update/upgrade an existing BIS
Developer Studio installation.

BIS Developer Studio Installation 3

2 Installation

2.1 Installation Requirements

Note: For current information, also refer to the Release Notes for your software
version.

• 200 MB free disk space on the installation drive for installation of this software.
• Sun® J2SETM Runtime (JRETM) or Development Kit 5 (JDKTM), which requires up to
additional 250MB. Also refer to
http://java.sun.com/j2se/1.5.0/install-windows-diskspace.html
• A computer that is supported by Microsoft® Windows® 2000, Windows® XP or Windows®
2003 (x86 32bit).
• Intel® Pentium® III 2GHz compliant CPU regarding the processor speed.
• Min. 1 GB physical memory (RAM). If you intend to run other applications parallel, you
need to increase your resources accordingly.
• Graphics hardware with 16bit color depth and a resolution of 1024x768 pixels.
• For installation: Write access to the Program Files folder and some HKLM registry keys.
You should therefore start the installer as local administrator.
• For installation: Access to files on installation media (The installer is delivered on CD-ROM,
but you can also distribute the content of the installation media via a network or other media.
The verification phase at the beginning of the installation can be significantly shortened, if
you use a local copy of the installation files.)

The above list are minimum requirements. It is recommended to plan for more RAM and screen
resolution if you need to work with the tool on a daily base.

2.2 Installation Procedure

To install the BIS Developer Studio with the Process Designer plug-in, follow these steps:

1. Verify the installation requirements. (Particularly make sure that you are logged in as local
administrator, see also Installation Requirements (page 4)).

BIS Developer Studio Installation 4

2. Download the Sun Java2 JRE or the Java2 Development Kit 5 (JDK) from the website
http://java.sun.com/j2se/1.5.0/download.jsp.1
3. Install JRE or JDK. The installer offers multiple installation options, e. g. demos, source
code and the public JRE. We recommend the installation of the complete product.
4. Execute the BISDevStudioSetup.exe file either on the installation media, or the network
drive, or the local copy of the corresponding installer. The procedure is described in detail
below (page 5).
5. Execute the BisProcessDesignerSetup.exe file either directly from the installation media, the
network drive, or the local copy of the corresponding installer. The procedure is described in
detail below (page 10).

If this is not the first time you install the BIS Developer Studio or the BIS Process
Designer plug-in, you should consult the Updates (page 19) section before you
follow this procedure.

For the operation of the BIS Developer Studio and the BIS Process Designer plug-in, refer to the
topic First Steps (page 13).

2.2.1 The BIS Developer Studio Installation

Before you can install the SEEBURGER Process Designer plug-in, you need to install the BIS
Developer Studio. This is an integrated development environment (IDE) for process modeling as
well as custom development.

1. Start the setup wizard by executing the file BISDevStudioSetup.exe from the installation
source media. The following welcome screen will be displayed.

BIS Developer Studio Installation 5

 Figure 2-1: Welcome screen of the BIS Developer Studio Setup Wizard
Click Next.
2. The setup wizard will check, if there is already an installation of the BIS Developer Studio.
In this case it will ask for confirmation to uninstall it. If this is the initial Install (no BIS
Developer Studio found), this step will be skipped.
Deleting the program files will not delete your existing workspaces, so it safe to proceed.
Check the section on how to update for more details.

BIS Developer Studio Installation 6

 Figure 2-2: Previous installation found
Click Next. During the now executed de-installation, the dialog may not respond to user
input.
3. If the installer can identify existing Java VM installations, it will display a list of possible
locations. Pick the location with an recent Java 5 installation. You can chose a Java Runtime
Environment (JRE), but a Java Development Kit (JDK) is recommended.
See the Troubleshooting section on how to change the installation to a differen Java VM later
on.

BIS Developer Studio Installation 7

 Figure 2-3: VM List
Select from the list and click Next.
4. If no suitable Java VM installation can be found by the installer, you wont be able to select
one from the drop down list box, but you will have to enter the full path to javaw.exe
executable from a Java 5 JDK or JRE.

Figure 2-4: VM Selection

BIS Developer Studio Installation 8

 Enter the path and click Next.
5. In the dialog that follows, enter the destination folder. By default, this is
%ProgramFiles%\SEEBURGER\BIS Developer Studio.
You can change this location, but we recommend keeping the relative location of the BIS
Developer Studio and the BIS Process Designer. I.e., install both under the same general
parent directory. If the Next button is disabled, you most likely trying to install on a drive
that lacks free memory. Then you need to select another drive, or free some memory.

Figure 2-5: Choose Install Location (Studio)

Click Next.
6. In the dialog that follows enter the name of the start menu. We recommend using the
SEEBURGER folder.

BIS Developer Studio Installation 9

 Figure 2-6: Choose Start Menu Folder
Click Next.
The BIS Developer Studio will install a single Start Menu entry for the BIS Developer
Studio.
Background Information: The start menu entry points to the executable
...\eclipse\bisdevstudio.exe under the BIS Developer Studio installation directory.

At this point the installation of the BIS Developer Studio is finished, and you can continue to
install the BIS Process Designer plug-in.

2.2.2 The BIS Process Designer Installation

After the successful installation of the BIS Developer Studio, you can continue with the
installation of the BIS Process Designer plug-in:

1. Start the setup wizard by executing the file BisProcessDesignerSetup.exe from the
installation source media. The following welcome screen will be displayed.

BIS Developer Studio Installation 10

 Figure 2-7: Welcome Screen of BIS Process Designer's setup procedure
Click Next.
2. In the dialog that follows, enter the destination folder. You can pick an arbitrary one;
however, we recommend using the same parent directory as the BIS Developer Studio.

Figure 2-8: Choose Install Location (Plug-in)

Click Next.

BIS Developer Studio Installation 11

After this step, BIS Developer Studio with the BIS Process Designer plug-in is ready for
operation. Now take the first steps (page 13).

Notes
1. http://java.sun.com/j2se/1.5.0/download.jsp

BIS Developer Studio Installation 12

3 First Steps

The BIS Developer Studio has the concept of a workspace, i.e. a location where all the current
projects are stored, and where all the current settings are persistent.
You can have multiple workspaces to separate different work units or developers. If you start the
BIS Developer Studio via Start | SEEBURGER | BIS Developer Studio, you will be asked about
the workspace's location.

Figure 3-1: Workspace Selection

The default location is %USERPROFILE%\workspace\. Pick a directory where you want to store
your work in progress. This directory should be used exclusively for the BIS Developer
Studio.
Background: If you want to work with more than one workspace, you can start the BIS
Developer Studio multiple times. (There is a command line option called -data which can be
used to specify the workspace location on start, so you do not get asked about the location. Make
a copy of the existing Start Menu entry, and modify its properties to include the -data C:\...
command line option, if you want to use this advanced feature).
The BIS Developer workspace will open a perspective which controls the views you see initially:

BIS Developer Studio Installation 13

 Figure 3-2: BIS Developer Studio Java Perspective

In the illustrated example, the BIS Developer Studio’s title bar indicates the name of the Java
perspective, the workspace location C:\WS, and the product name BIS Developer Studio.

1. Switch to the Process Designer Perspective using Window | Open Perspective | Other…

BIS Developer Studio Installation 14

 Figure 3-3: Process Designer Perspective
2. In the Process Designer Perspective, you can see the Navigator view in the upper right,
where you can select or create projects. Open File | New | Project… | Process Designer |
New Process Designer Project

BIS Developer Studio Installation 15

 Figure 3-4: New Project Wizard

The following figure shows the Process Designer perspective with a new (empty) sample
process.

BIS Developer Studio Installation 16

See the Process Designer’s Help menu that is available under Help | Help Content for an online
version of the BIS Developer Studio and the BIS Process Designer plug-in.

BIS Developer Studio Installation 17

 Figure 3-5: Process Designer Help

BIS Developer Studio Installation 18

4 Updates

Before you update an existing BIS Developer Studio with the BIS Process Designer Plug-in
installation, ensure that your new version complies with your BIS 6 installation. Corresponding
information is given in the Release Notes. Generally the first three digits of the version number
of the BIS 6 installation and the BIS Process Designer should match (e. g. 6.2.2).
If you are sure that you can update your BIS Developer Studio, apply the usual installation
procedure. The setup wizard will detect an existing installation and de-install it as shown in this
figure (page 0). This will delete the application, but the projects in your workspace will not be
touched.
Please check the Release Notes whether you have to apply manual steps after an upgrade.
You might experience problems or missing functionality after an upgrade. Then, you can “clean”
conflicting settings by starting BIS Developer Studio with the -clean argument applied.
%ProgramFiles%\SEEBURGER\BIS Developer Studio\eclipse\bisdevstudio.exe -clean

There is currently no upgrade site for online updates. The re-install feature is required to get the
latest version.

BIS Developer Studio Installation 19

5 De-Installation Procedure

The BIS Process Designer plug-in and the BIS Developer Studio provide a de-install function
that is available over (Windows) Start (menu) | Settings | Control Panel | Add/Remove Programs.

You can also use the uninstall.exe program in the target directory of both applications. Your
complete work will be stored in the workspace and not be affected by the de-installation
procedure. You will have to delete the workspace manually. Also if you manually set up a
location for configuration data, you will have to clean up this location by deleting the files.

BIS Developer Studio Installation 20

6 Appendix

6.1 Troubleshooting

6.1.1 Error Message No JDK found

A situation where the JRE or JDK cannot be found may occur when starting the BIS Developer
Studio. You may face an error message similar to the one shown in the illustration below.

Figure 6-1: Error Message in Case of Missing JRE/JDK

In this case, the applied JDK is no longer available on the given location. Maybe somebody has
installed a newer version and removed the old one. You can fix the BIS Developer Studio’s
configuration using the corresponding ini file:

1. Open the file %ProgramFiles%\SEEBURGER\BIS Development

Studio\eclipse\bisdevstudio.ini. This file contains line-separated arguments.
2. Search for two lines, starting with:
...
-vm
C:\Programme\Java\jdk1.5.0_07\bin\javaw.exe
...

3. Modify the second line accordingly to refer to the proper location.

6.1.2 Error Message No Developer Studio found before installing this plug-in

If you try to install the BIS Process Designer plug-in, and the setup is not able to find the BIS
Developer Studio, you may receive a message similar to the one shown in the illustration below.

BIS Developer Studio Installation 21

 Figure 6-2: Error Message in Case of Missing BIS Developer Studio

In this case, (re)install the BIS Developer Studio.

The installer of the plug-in is actually looking for the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Seeburger\BIS Developer Studio\path to find the
location of the BIS Developer Studio. It will create a file ...\eclipse\links\BIS Process
Designer.link in the directory that contains the location of the Process Designer Plug-in:
path=C:/Programme/SEEBURGER/BIS Process Designer

6.1.3 Error Message Error opening file for writing

The setup wizard of the BIS Developer Studio may display an error message indicating that it is
unable to open a file. This may be caused by insufficient permissions, or by the fact that the
application is running while you try to perform an update.

Figure 6-3: Error opening file for writing (cutout)

In the latter case, you can exit the application and re-try the installation. If it is a permission
problem, make sure you are assigned local administrator rights for installation.

6.1.4 Error Message after Starting

If you get an error message on startup similar to the one shown in the illustration below, this
might have the reason that you (i.e. the related user) is not allowed to write to the configuration
files of the BIS Developer Studio’s installation. (Then, no log file is written).

Figure 6-4: Sample Error Message after Startup

The configuration area is used to store some global settings which cannot be stored in the
workspace, e. g. the actual name of the last used workspace and the flag, if the workspace should

BIS Developer Studio Installation 22

be used without asking. In a multi-user installation with a restrictive administration, it is quite
usual that the configuration directory (below the installation target directory) is not write-able.
Then you will only find the read-only configuration/config.ini file.
In order to force the BIS Developer Studio Program launcher to use a different (write-able)
location for the configuration, you can set the -configuration command line option. You can add
this option to the Start menu's shortcut, or better once modify the bisdevstudio.ini file by adding
the following two (bold) starting lines:
-configuration
@user.home/bisdevstudio/configuration
-showlocation -vm C:\Programme\Java\jdk1.5.0_07\bin\javaw.exe
-vmargs
-Xms40m
-Xmx256m

In this case, the @user.home pattern is replaced with the profile of the current user, and the
directory is created there.

6.2 Contact

If you have questions or need assistance for installing or using SEEBURGER solutions, please
do not hesitate to contact SEEBURGER’s Customer Service and Support. To accelerate
processing of your request, please ensure you have the exact Version number of the product as
well as your Customer Number available. In case you encountered an error condition a
screenshot or logfile should be provided as well.
SEEBURGER AG SEEBURGER, Inc.
Edisonstr. 1 Five Concourse Parkway
D-75015 Bretten Suite 2400
Germany Atlanta, GA 30328, USA
URL: http://www.seeburger.de1 URL: http://www.seeburger.com2
Tel: +49 (0)7252 96 – 0 Phone: +1 770-604-3888
Fax: +49 (0)7252 96 – 2222 Fax: +1 770-604-3885
Support Support
URL: http://support.seeburger.de3 URL: http://support.seeburger.com5
Mail: support@seeburger.de4 Mail: support@seeburger.com6

Notes
1. http://www.seeburger.de/
2. http://www.seeburger.com/
3. http://support.seeburger.de/
4. mailto:support@seeburger.de
5. http://support.seeburger.com/
6. mailto:support@seeburger.com

BIS Developer Studio Installation 23