activevos installation and upgrade tips · activevos installation and upgrade tips an active...

ActiveVOS

Installation and

Upgrade Tips AN ACTIVE ENDPOINTS TECHNICAL NOTE

© 2011 Active Endpoints Inc. ActiveVOS is a trademark of Active Endpoints, Inc. All other company and product names are the property of their respective owners.

Version 1.0, Dated 2 May 2011

2011

0

Copyright © 2011, Active Endpoints, Inc. of 15

Contents Overview.............................................................................................................................. 2 Pre-Requisites ...................................................................................................................... 2 Headless Mode Installation ................................................................................................. 2 Non-Headless Mode Installation ......................................................................................... 4 Installation and Upgrade Tips .............................................................................................. 5

Preparing for Future Upgrades and Installations ............................................................ 5 Database Considerations during Upgrades ..................................................................... 6 Reinstalling ActiveVOS .................................................................................................... 6

Appendix A: GUI Mode Installation Example ....................................................................... 7 Appendix B: Console Mode Installation Example ............................................................. 11 Appendix C: install.properties File Example ...................................................................... 13 About Active Endpoints ..................................................................................................... 15

Overview This document contains helpful hints and notes on how to proceed with

an ActiveVOS Install/Upgrade. This supplements the install/configuration

quick start server guideline that comes along with the installer utility also

available with our product documentation

http://www.activevos.com/developers/documentation/activevos.

Pre-Requisites The existing configuration must be verified against the list provided in

the Certified Systems Support in the

http://www.activevos.com/products/activevos/certified-system-support.

Headless Mode Installation ActiveVOS relies on GUI components from the Java's SWT package, such

as Fonts, etc. If you are running on a headless server (i.e., a server which

does not have a graphic subsystem), you may see one of the following

errors while trying to run the configuration:

java.lang.NoClassDefFoundError: sun/awt/X11GraphicsEnvironment

Can't connect to X11 window server using ':0.0' as the value of

the DISPLAY variable

org.eclipse.birt.report.service.api.ReportServiceException

http://www.activevos.com/developers/documentation/activevos

http://www.activevos.com/products/activevos/certified-system-support


Use one of the following techniques to correct these errors:

Option A:

Configure the JVM system property java.awt.headless=true and

at the command line, start the JVM with the argument:

-Djava.awt.headless=true

OR

Add the system property "-Djava.awt.headless=true" setting to the

installer script/batch file -> config_deploy.sh or

config_deploy.bat you will find in the “bin” directory of your

installation.

Example of a config_deploy.sh:

#!/bin/sh

$JAVA_HOME/bin/java -Xms128m -Xmx512m -

Djava.awt.headless=true -jar config.jar $1

Option B:

Run an X-windows virtual frame buffer (Xvfb). For details please

see your System Administrator.

Option C:

You can opt to run the installer in silent or console mode, as

explained in the next section.


Non-Headless Mode Installation There are three options to run the installer. Choose the one you find

most convenient.

Option A: GUI Mode

This is a default mode of installation, where in the config_deploy

file is executed as a batch or a script file, and the GUI screen

displays the various options to choose from and complete the

installation.

At any point of time before starting the actual installation (the

last screen), the user can go back and forth between the screens

to review and modify the properties.

Sample screen shots of the GUI Mode are shown in Appendix A.

Option B: Console Mode

In some cases, depending on the Operating System speed and

configuration, it may take a long time for the GUI Mode to

launch and continue further. The best option, in such a case,

would be to use the console mode of installation.

Console Mode is a textual/ command line mode, where in you

would be prompted with the configuration related questions and

the options that you can choose from.

Once the configuration is completed, all the options that you

have chosen as stored within install.properties file that could be

re-used later in a different environment, by editing very minor

changes.

Like the GUI Mode, at any point of time before starting the

actual installation (the last step of configuration), the user can go

back and forth between the previous configuration steps to

review and modify the properties.

Sample screen shot of the console mode installation are shown

in Appendix B.


Option C: Silent Mode

Silent Mode is a mode where the installation runs in the

background requiring no user interaction. This option requires

that you have already run the Configuration utility in the console

mode or the GUI Mode, which sets configuration options in the

install.properties file that the Silent Mode can refer to.

Unlike the GUI Mode and the Console mode, once the

installation starts, the user can't change any of the properties

that are configured. Prior to executing the configuration in the

silent mode, it is a good idea to double check the details in the

install properties file, like host and details if any.

A sample of the install.properties is shown in the Appendix C.

Installation and Upgrade Tips

Preparing for Future Upgrades and Installations After your initial installation backup your install.properties. This will save

you some time during upgrade.

The install.properties file will come handy the next time you

install/upgrade the server the next time in a different environment.

When you install/upgrade the next time, you could replace the existing

install.properties, with the one you need. These properties will be used

as the defaults the next time the application is configured. This will avoid

some time typing in the values once again (and make mistakes).


Database Considerations during Upgrades Install a new database schema

This will drop the existing schema and recreate a new one

according to the ActiveVOS version that the user is installing. The

installer utility provides a check box option to take of this.

Upgrade the existing schema

This means that that user would like to retain the existing

schema as is, and juts upgrade them to be compatible with the

version of ActiveVOS. It should be noted that in most of the

cases, the database upgrade would apply only when upgrading

to a major version of ActiveVOS. For example: You are currently

running version 7.x and would like to upgrade to 8.x.

Please note that in the case of upgrade there is no option in the installer

to run the upgrade scripts. It is the user's responsibility to uncheck the

‘install database option’ (if enabled, see Appendix A – Deployment

options screen, would drop and recreate the database) and execute the

upgrade scripts as explained in the installation guide.

Refer to the Configuration > 'Manual Install or Update of Database

Schema' section of for your application server in the documentation

(http://www.activevos.com/developers/documentation/activevos).

It is suggested to execute the upgrade scripts prior to upgrading the

ActiveVOS.

Reinstalling ActiveVOS If you choose to perform a fresh install of database as explained above,

the existing schema holding all your values will be dropped and

recreated. In this case all your existing server configuration values like

URN Mappings, Function Contexts, etc would be lost. Therefore, it is

suggested that even before you shut down the ActiveVOS server for the

upgrade process, that take a backup of the existing server configuration

from the ActiveVOS admin console > Home > Server Status > Download

Configuration file.

This file contains all the configuration details in this server and can be

later merged with the new configuration file, so that you could save

some time on reconfiguring the server related configurations.


Appendix A: GUI Mode Installation Example


Appendix B: Console Mode Installation Example


Appendix C: install.properties File Example This sample of install.properties performs an installation of ActiveVOS on

a Linux server using Apache Tomcat and MySQL. The schema and

installation directories need to be customized to your environment

# ant.install.config.version=5.0 #panels to be visited install.path.engine=true install.path.b4p=true install.path.database=true install.path.deployment=true #security security.admin.services=true security.process.services=true security.task.services=true security.identity.service=true #config tasks configuration.engine=true configuration.b4p=true configuration.database=true #paths – configure the path to Apache Tomcat and ActiveVOS Installation directory #[TOMCAT-DIR] example: /var/activevos/installs/apache-tomcat-6.0.29 #[ACTIVEVOS-DIR] example: /var/activevos/installs/ActiveVO805/server-enterprise appserver.location=[TOMCAT-DIR] basedir=[ACTIVEVOS-DIR]/tomcat_config/bin/. #engine configuration database.type=mysql #b4p configuration b4p.url=http\://localhost\:8080/active-bpel/services/AeB4PTaskClient-taskOperations b4p.timeout=0 #jdbc jdbc.database.driver.class=com.mysql.jdbc.Driver jdbc.database.url=jdbc\:mysql\://[dbhostname]\:3306/[SCHEMAHERE]?useUnicode\=true&charactorEncoding\=UTF-8&characterSetResults\=utf-8 jdbc.database.name=[SCHEMAHERE] jdbc.database.driver.jar=[TOMCAT-DIR]/lib/mysql-connector-java-5.1.5-bin.jar jdbc.database.username=[username – bpeluser by default] jdbc.database.password=[password – bpel by default] jdbc.database.connection.timeout=1000 jdbc.database.min.connections=10 jdbc.database.max.connections=100 jdbc.validate.connection=true


# cluster cluster.enabled=false cluster.multicast=228.1.221.1 cluster.port=45566 cluster.binding= #deploy install.task.application=true install.web.application=true install.database.descriptor=true #database schema (set both to false for upgrades) install.database.schema=true install.socrates.schema=true progress-targets=install,


About Active Endpoints Active Endpoints (www.activevos.com) ActiveVOS is the leader in service-

oriented BPM software for process automation. ActiveVOS empowers

project teams to create business process management (BPM)

applications using services, making their businesses more agile and

effective. ActiveVOS promotes mass adoption of SOA-enabled BPM

applications by focusing on accelerating project delivery time with a

complete, affordable and easy-to-use system. Active Endpoints is

headquartered in Waltham, MA with development facilities in Shelton,

CT.

To find out how Active Endpoints can help your business, visit

http://www.activevos.com, call +1 781 547 2900 and press 1 for Sales, or

email us at [email protected].

http://www.activevos.com/

activevos installation and upgrade tips · activevos installation and upgrade tips an active...

Documents