Server Exploitation Guide
DROPS
Version 2.6
Publication Date: December, 2016
Prepared by the DROPS Software Documentation Team
FRANCE (HQ)
GERMANY
SWEDEN
USA
HONG KONG
55 Rue Adrastée 74650 Annecy/Chavanod
Richardstr. 84 22089 Hamburg
Prostvägen 36 141 43 HUDDINGE
1 Phoenix Mill Lane, Suite 203 Peterborough, NH 03458
Room 22, Smart-Space 3F, 100 Cyberport Road
Tel. +33 4 50 57 83 96
Tel. +49 40 357 09 10-2
Tel. +46(0) 70-793 6570
Tel. +1 (603) 371-9074
Tel. +852 3618 6118
Server Exploitation Guide v2.6 |
Copyright © 2015-2016 by DROPS Software All rights reserved.
The following terms are names owned by International Business Machines Corporation in the United States, other
countries, or both: AS/400®, ClearCase, ClearQuest®, DB2, DB2 Connect™, DB2 Universal Database™, ibm.com,
IBM i, iSeries, System i, OS/400, Rational®, SP2, Service Pack, WebSphere. Java and all names based on Java are
owned by Oracle Corp. in the United States, other countries, or both. Eclipse is a registered trademark of Eclipse
Foundation, Inc. Other names of companies, products or services are the property of their respective owners.
Page 2 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Contact DROPS Software | Server Exploitation Guide v2.6
Contact DROPS Software
drops-software.com
DROPS Software is a subsidiary of Arcad Software, a French company and leader in the ALM market.
Headquartered in France at the foot of the Alps, DROPS Software offers global services and has offices on
three continents.
Country
FRANCE (HQ)
Address
DROPS Software
55 Rue Adrastée
74650 Annecy/Chavanod
DROPS Software
67 Rue du Bourbonnais
69009 Lyon
GERMANY
ARCAD Software Deutschland GMBH
Richardstr. 84
22089 Hamburg
SWEDEN
ARCAD Software Nordic AB
Prostvägen 36
141 43 HUDDINGE
USA
ARCAD Software Inc.
1 Phoenix Mill Lane, Suite 203
Peterborough, NH 03458
ASIA
Telephone
Tel. +33 4 50 57 83 96
Fax +33 4 50 57 52 79
sales-eu@drops-software.com
Tel. +33 9 72 42 09 57
Tel. +49 40 357 09 10-2
sales-de@drops-software.com
Tel. +46(0) 70-793 6570
sales-se@drops-software.com
Tel. +1 (603) 371-9074
Toll Free +1 (800) 676-4709
sales-usa@drops-software.com
ARCAD Software Asia
Tel. +852 3618 6118
Room 22, Smart-Space 3F,
Unit 908-915, Level 9, Cyberport 3,
sales-asia@drops-software.com
100 Cyberport Road HONG KONG
Table 1: Contact DROPS Software
ARCAD Software guarantees consultant support 24 hours a day, 5 days a week (24/5) to DROPS Software
registered members. Calls received on the numbers for France, USA and Asia are redirected to a central
system which, according to the hour, puts you in contact with a consultant in or near your timezone.
Country
E-mail
Telephone
FRANCE
support-eu@drops-software.com
Tel. +33 4 50 57 28 00
GERMANY
support-de@drops-software.com
Tel. +49 40 357 09 10-2
SWEDEN
support-se@drops-software.com
Tel. +46(0) 70-793 6570
USA
support-usa@drops-software.com
Tel. +1 (603) 574-4860
ASIA
support-asia@drops-software.com
Tel. +852 8192 5740
Table 2: Contact the DROPS Software support team
Page 3 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Server Exploitation Guide v2.6 | Preface
Preface
Document Purpose
This document is intended to guide DROPS Server Administrators through admin-level server
management procedures.
Intended Audience
This document is intended for System Admins, DROPS Administrators and/or the person in charge of
managing the DROPS Server.
Related Documentation
Related Documentation
DROPS Configuration Guide
DROPS Datasheet
DROPS Installation Guide
DROPS Script Reference Guide
DROPS System Requirements
DROPS User Guide
DROPS White Paper
Table 3: Related Documentation
Publication Record
Unless stated otherwise, this document is valid for the most current version of DROPS listed as well as
every subsequent version.
Product Document Publication
Version Version
Date
≥ 2.6
1.3
December,
2016
Update Record
No functional changes.
No functional changes.
2.5
1.2
October,
2016
Corrections:
l
Added Archived Files Storage Area to the list of directories to
take into account when Migrating the DROPS repositories
2.4
1.1
September, Documentation updated for product evolution:
2016
l Updated Migrating the DROPS Database
2.3
1.0
September,
Initial publication.
2016
Table 4: DROPS Server Exploitation Guide Publication Record
Page 4 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Contents | Server Exploitation Guide v2.6
Contents
Contact DROPS Software
3
Preface
4
Contents
5
1 Backing Up/Restoring the DROPS Server
6
2 Reclaiming unused space in the DROPS Database
7
3 Migrating the DROPS Database
8
3.1 The default method for Windows and Linux
3.2 The alternative method for Linux only
8
10
4 Migrating the DROPS repositories
12
5 Purging the DROPS Server's directories
13
Page 5 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Server Exploitation Guide v2.6 | 1 Backing Up/Restoring the DROPS Server
1 Backing Up/Restoring the DROPS Server
Backing up the DROPS Server is an important part of ensuring that none of your content is lost. The
backed up content can also be used to restore the Server to another location. How the DROPS Server is
backed up is up to you but be careful to include the content from the following directories. Below is a list of
all the default paths that contain essential content for the DROPS Server. They house all of the necessary
information required to reproduce your Server in a functional state.
Before backing up the DROPS Server, shut it down (some files will be locked if it is running).
Note
The paths listed below are relative to the Server's root directory. Paths in
bold are default values that can be changed, so make sure they have not
been changed before backing them up.
Reference
For more information about changing the default paths, refer to Migrating
the DROPS repositories on page 12.
l
l
l
The Server's configuration settings (repository path, license key, etc):
configuration/org.eclipse.osgi/bundles/1
The DROPS Database: database/rm4os.h2.db
The Deployment Process Instances' files: deploymentprocess
l
The default DROPS ant scripts and the Deployment Processes' XML descriptions: files/bin/rm4os
The Import Instances' artifacts list: imports/xmllists
l
The DROPS repository root folder: repository
l
Page 6 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
2 Reclaiming unused space in the DROPS Database | Server Exploitation Guide v2.6
2 Reclaiming unused space in the DROPS Database
The H2 database engine does not automatically reclaim unused space after a delete operation. This space
is left allocated for reuse. Consequently, the database's size never decreases, even after a purge. It may be
necessary to reclaim this unused space to free some space on the file system that houses the database.
Follow the subsequent steps to reclaim this unused space.
Warning!
You must shut down the DROPS Database before beginning. Reclaiming
unused space in the DROPS Database while DROPS is in use must be
avoided at all costs!
Step 1 Before beginning, activate and allow access to the H2 remote console.
Step 2 Open the DROPS Studio or the DROPS Web Console and connect to the DROPS Server.
Step 3 Right-click on the
view.
Step 4 Select
server and select
Database >
Configure.... to open the
H2 Database Server to open the
Configuration Category
H2 Database Server editor.
Step 5 Under the H2 SQL Console section, make sure the settings are set as follows. If the port has been
changed, modify it here so it’s 8082.
Step 6 Access the H2 SQL web console through this URL: http://<drops_server_address>:8082
Step 7 Enter the following JDBC URL and credentials:
l
l
l
JDBC URL: jdbc:h2:database/rm4os
User name: sa
Password: quadra
Step 8 In the SQL statement text area, type the following statement: SHUTDOWN COMPACT.
Step 9 Click Execute. Once the operation is finished, the SQL console must show the following message:
"Database is already closed".
Step 10 Close the H2 SQL console.
Step 11 Restart the DROPS Server.
Page 7 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Server Exploitation Guide v2.6 | 3 Migrating the DROPS Database
3 Migrating the DROPS Database
It is possible to migrate the DROPS Database from its default location to anywhere your organization
requires on a Windows or Linux machine. The DB’s default location is in the database directory located in
the DROPS Server's root directory. Any server can be used to host the DROPS Database.
3.1 The default method for Windows and Linux
Important!
If it is migrated using this method, the target URLs for the data source in
the DROPS Studio and for the DROPS Web Server must both be updated
so that they point to the new location of your DB.
Follow the subsequent steps to migrate the DROPS Database on either Windows or Linux.
Step 1 Open the DROPS Studio or the DROPS Web Console and connect to the DROPS Server which
reads into the DB you will migrate.
Step 2 Modify the data source’s URL to point to the future location of the DB.
1. Right-click on the
Category view.
2. Select
server and select
Database >
Configure... to open the
Data Sources to open the
Configuration
Data Sources editor.
3. Select the rm4os datasource and select Edit from the Actions drop-down menu.
4. Change the datasource's URL to point on the new location of the database.
5. Keep in mind that the default URL is relative to the DROPS Server’s root directory, so you
may need to specify the absolute path to the new location. For example, if the database will
be located in a directory named /new/database/location, the URL should be:
jdbc:h2:/new/database/location/rm4os.
6. Click the Actions drop-down menu and select Save and close the DROPS Studio or the
DROPS Web Console.
Step 3 Stop the DROPS Server.
For Windows:
Open the Local Services Management Console.
Page 8 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
3 Migrating the DROPS Database | Server Exploitation Guide v2.6
Figure 1: Stop the DROPS Server service on Windows
For Linux:
If the Linux distribution uses the systemd initialization system:
- systemctl stop drops-server
If the Linux distribution uses the System V initialization system:
- /etc/init.d/drops-server stop
Step 4 Move the file database/rm4os.h2.db to the new location.
Step 5 Modify the odaURL that the DROPS Web Server jetty uses to access and create DROPS reports.
1. Navigate to the report directory if the DROPS Web Server installation location.
The default location of this file is C:\Program Files\ARCAD Solutions\Jetty\webapps\birt\report.
Note
If you are using a Web Application Container other than the
DROPS Web Server (a Jetty or Tomcat) this file is found in
that web application’s directory.
2. Modify the profilestore.xml. Change the odaURL value to point to the new location of the DB.
<profile autoconnect="No"
desc="DROPS Datasource" id="e7a2e0c0-217f-11e1-be1a-91dd0c9468ab"
name="DROPS DataSource"
providerID="org.eclipse.birt.report.data.oda.jdbc">
<baseproperties>
<property name="odaJndiName" value="java:comp/env/jdbc/drops"/>
<property name="odaDriverClass" value="org.h2.Driver"/>
<property name="odaURL"
value="jdbc:h2:tcp://localhost/database/rm4os"/>
<property name="odaUser" value="sa"/>
Page 9 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Server Exploitation Guide v2.6 | 3 Migrating the DROPS Database
<property name="odaPassword" value="quadra"/>
</baseproperties>
</profile>
3. Save the changes made.
Step 6 Restart the DROPS Server.
For Windows:
Open the Local Services Management Console.
Figure 2: Start the DROPS Server service on Windows
For Linux:
If the Linux distribution uses the systemd initialization system:
- systemctl start drops-server
If the Linux distribution uses the System V initialization system:
- /etc/init.d/drops-server start
Result The DROPS Database is migrated and all of the functions that depend on it are updated.
3.2 The alternative method for Linux only
If you use Linux, an alternative way to migrate the DROPS Database is also available which does not require
you to change the data source configuration nor the report’s profilestore.xml.
Note
This alternative option is not available for Windows.
Follow the subsequent steps to migrate the DROPS Database on Linux only.
Step 1 Stop the DROPS Server.
Page 10 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
3 Migrating the DROPS Database | Server Exploitation Guide v2.6
If the Linux distribution uses the systemd initialization system:
- systemctl stop drops-server
If the Linux distribution uses the System V initialization system:
- /etc/init.d/drops-server stop
Step 2 Move the file database/rm4os.h2.db to the new location.
Step 3 Delete the database folder from the original DROPS root directory.
The default location is: rm -rf /opt/drops/server/database
Step 4 Create a symbolic link to the new database directory in the DROPS root directory:
cd /opt/drops/server
ln -s /new/database/location database
Step 5 Restart the DROPS Server.
If the Linux distribution uses the systemd initialization system:
- systemctl start drops-server
If the Linux distribution uses the System V initialization system:
- /etc/init.d/drops-server start
Page 11 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Server Exploitation Guide v2.6 | 4 Migrating the DROPS repositories
4 Migrating the DROPS repositories
To move the DROPS repositories from their default locations after they are already in use, you must
migrate them. There are five locations used by the DROPS Server that can be redefined using either the
DROPS Studio or the DROPS Web Console. Every location is a directory which is a root for the various files
stored by the DROPS Server.
l
l
l
l
l
l
The Deployment XML List Storage Area. When Releases are deployed, DROPS creates a
Deployment List and stores it in a predefined path.
The Update Repository Root Path. The path to the root location of the new repository in which the
server will store files downloaded from the Update Server.
The Repository Storage Area. The path to the root location of the Artifact Repository. A centralized
directory that regroups defined Applications (Components and Artifacts) and Releases.
The Import Root Directory. If an Import Strategy uses the default *AUTO as its Root Directory, the
path defined here will be used.
The Import XML List Storage Area. When Artifacts are imported, DROPS creates an Artifact List and
stores it in a predefined path.
The Archived Files Storage Area. The path to the root location where archived deployment logs
should be stored. By default, this repository is automatically created in the DROPS Server.
Follow the subsequent steps to migrate each location.
Step 1 Shutdown the DROPS Server.
Step 2 Move the content of the repository to migrate from its current location to its new location
Step 3 Restart the DROPS Server.
Step 4 Open the DROPS Studio or the DROPS Web Console and connect to the DROPS Server.
Step 5 Right-click on the
view.
server and select
Configure.... to open the
Configuration Category
Step 6 Select the corresponding configuration editor and modify the path to point on the new location:
l
l
l
l
l
l
To modify the Deployment XML List Storage Area, select
General settings.
To modify the Update Repository Root Path, select
Module Update Management.
DROPS - General Functions →
DROPS - Import Process →
To modify the Repository Storage Area, select
Repository Settings.
To modify the Import Root Directory, select
Import Settings.
DROPS - Deployment Process >
DROPS - Import Process →
To modify the Import XML List Storage Area, select
General Import Settings.
To modify the Archived Files Storage Area, select
Archiving Settings.
Artifact
General
DROPS - Import Process →
DROPS - Artifact Settings→
Page 12 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com
Release
5 Purging the DROPS Server's directories | Server Exploitation Guide v2.6
5 Purging the DROPS Server's directories
Deleting temporary/useless files from the DROPS Server installation directory regularly to prevent it from
becoming too bloated can be done manually or automatically by a script. How the DROPS Server is purged
is up to you but be careful to only delete the content from the following directories.
The list below identifies the files and directories that contain mostly contain temporary files and can be
safely purged.
Note
The paths listed below are relative to the Server's root directory. Paths in
bold are default values that can be changed, so make sure they have not
been changed before backing them up.
Reference
For more information about changing the default paths, refer to Migrating
the DROPS repositories on page 12.
l
l
l
l
OSGi runtime log files: .log files in configuration
Import Instances’ temporary root directory: imports/tmp
The DROPS Server’s log directory: logs
The general purpose temporary directory: tmp
Page 13 / 13
DROPS Software • Copyright © 2016 • All Rights reserved. • drops-software.com