Академический Документы
Профессиональный Документы
Культура Документы
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
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.
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.
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)).
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).
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.
At this point the installation of the BIS Developer Studio is finished, and you can continue to
install the BIS Process Designer plug-in.
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.
Notes
1. http://java.sun.com/j2se/1.5.0/download.jsp
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.
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:
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…
The following figure shows the Process Designer perspective with a new (empty) sample
process.
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.
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.
6.1 Troubleshooting
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.
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:
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.
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.
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.
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).
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
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