Version 9.5 SP1
 —  Post Installation and Additional Uninstallation Steps for CentraSite  —

Before You Start Using CentraSite

This section provides information on steps to follow after the installation.


CentraSite Application Server Tier Configuration

By default, the CentraSite installation procedure installs the Software AG Runtime on the CentraSite Application Server Tier.

You can configure your Software AG Runtime environment by adding or modifying Java system properties for Software AG Runtime. The procedures for doing this are given in the following sections.

After changing any Java system properties, the Software AG Runtime has to be restarted.

The following topics summarize the configuration possibilities.

Where to find the Java System Properties

The Java system properties are contained in the file wrapper.conf that is located in <SuiteInstallDir>/profiles/CTP/configuration.

In this file, there is a list containing properties with the syntax:

wrapper.java.additional.<n>=<value>

or

wrapper.java.additional.<n>.<string>=<value>

where <n> is an integer and <value> is the value that is assigned to the property. If a line contains <string>, it represents a qualifier for the value of wrapper.java.additional.<n> given in the previous line.

To add a new system property, you extend this list with a new entry, using the syntax without the <string> qualifier. Ensure that the value you assign to <n> is one higher than the highest value so far. The <value> that you specify is described in the following paragraphs.

Example

Assume that the wrapper.conf file already contains various entries of the form wrapper.java.additional.<n>=<value>, and the highest value of <n> so far is 5, and you want to add a property with the value -Dhttp.proxyPort=12345. In this case, you would increment the value of <n> to 6, and the line would look like this:

wrapper.java.additional.6=-Dhttp.proxyPort=12345

HTTP Proxy Configuration

If an HTTP proxy is being used to access the Internet, add the following Java system properties:

-Dhttp.proxyHost=httpprox.<3rd-level-domain>.<2nd-level-domain>
-Dhttp.proxyPort=<proxy_port_number>
-Dhttp.nonProxyHosts="*.<3rd-level-domain>.<2nd-level-domain>|*.<domain_1>.<extension>|*.<domain_2>.<extension>"

The <non_proxy_host_list> should contain at least the name of the host on which the CentraSite Application Server Tier is running. If there is more than one entry in the <non_proxy_host_list>, the entries are separated by the vertical bar character "|".

The following are cases of particular interest in which you may need to set the proxy settings:

HTTPS (SSL) Proxy Configuration

If an HTTPS proxy is being used to access the Internet, add the following Java system properties:

-Dhttps.proxyHost=<sslproxy> 
-Dhttps.proxyPort=<port>

Without this setting, any operation requiring HTTPS, such as importing a WSDL/BPEL/XSD file via HTTPS, may fail with messages like: "The WSDL file is unreachable. Make sure the input information is correct".

Memory Settings

If you want to change the amount of available memory, modify the value for -XX:MaxPermSize, for example:

-XX:MaxPermSize=256M

Print Feature on UNIX and Linux Platforms

Using the print feature on UNIX and Linux platforms requires Java AWT to be set to headless mode.

Examples would be for instance printing or previewing BIRT reports with the CentraSite Application Server Tier running on a Linux platform.

The parameter setting is as follows:

java.awt.headless=true

Troubleshooting

If a web application shows unexpected behavior such as "hanging" or refuses to proceed, you should first check the Software AG Runtime log file. The location of the current Software AG Runtime log file is given in the logging property "wrapper.logfile" of the wrapper.conf file.

Top of page

Securing Communication Between CentraSite Application Server Tier and CentraSite Registry Repository

You can configure a secure communication between the CentraSite Application Server Tier and the CentraSite Registry Repository by executing the following commands in the command line interface CentraSiteCommand.cmd (Windows) or CentraSiteCommand.sh (UNIX) of Command Central. The tool is located in <CentraSiteInstallDir>/utilities.

If you start this command line tool with no parameters, you receive a help text summarizing the required input parameters.

The parameters of the command are case-sensitive, so for example the parameter "-file" must be specified as shown and not as "-FILE".

Securing the CentraSite Application Server Tier

To secure the CentraSite Application Server Tier, use a command of the following form:

CentraSiteCommand set AST security -file <CONFIG-FILE>

The following table describes the complete set of input parameters that you can use with the set AST security utility:

Parameter Description
-file
The URI (file: or http:) of the configuration file.

For example:

CentraSiteCommand set AST security -file "config.xml"

Securing the CentraSite Registry Repository

To secure the CentraSite Registry Repository, use a command of the following form:

CentraSiteCommand set RR security -file <CONFIG-FILE>

The following table describes the complete set of input parameters that you can use with the set RR security utility:

Parameter Description
-file
The URI (file: or http:) of the configuration file.

For example:

CentraSiteCommand set RR security -file "config.xml"

Top of page

Using Terracotta BigMemory

Terracotta BigMemory is a separately-licensed add-on product that allows you to use vast amounts of off-heap cache memory for the storage of application data. By significantly reducing the dependency on disk-based processing, applications that use BigMemory can run with huge speed increases.

For general information about Terracotta BigMemory usage within the webMethods Suite, refer to the System Requirements, Installation, and Upgrade section of the webMethods Suite on the Software AG documentation web site.

To activate BigMemory processing for CentraSite, you need to carry out the following steps:

Setting up the license to use Terracotta BigMemory

In CentraSite, Terracotta BigMemory can be used in 3 places:

Web applications in Software AG Runtime use internal mechanisms to locate the license file, so you do not need to modify anything here.

For Eclipse/Software AG Designer and client applications, you need to specify the location of the license file explicitly. The license file can be placed in any directory, but Eclipse/Software AG Designer or the client application must be started with the following Java property:

-Dcom.tc.productkey.path=<path to license file>

For example:

-Dcom.tc.productkey.path=C:\SoftwareAG\common\conf\terracotta-license.key

Configuring CentraSite to use Terracotta BigMemory

You need to perform some steps in order to configure CentraSite to use BigMemory.

Start of instruction setTo configure CentraSite to use BigMemory

  1. On the CentraSite Registry Repository node, open a command line and go to the CentraSite bin directory (<SAGInstallDir>/CentraSite/bin).

  2. Execute the script centrasite_setenv.

  3. Execute the command:

    java -jar CentraSiteCacheConfiguration.jar <CentraSite_URL> <AdministratorID> <Password> 
         SET maxMemoryOffHeap <Size><Unit>

    where Unit can be any of : k, K, m, M, g, G, t, T (for kilobytes, megabytes, gigabytes, terabytes)

For example, the command for setting a BigMemory cache of 20 gigabytes with an administrator account "INTERNAL\Admin" and password "AdminPW" would be:

java -jar CentraSiteCacheConfiguration.jar "http://localhost:53307/CentraSite/CentraSite" "INTERNAL\Admin" "AdminPW" 
     SET maxMemoryOffHeap 20G 

Top of page

Configuring HTTP Proxy Settings for Importing WSDLs

In order to have access to or to import WSDL files from the internet, the following Java system properties should be set for the Java Service Wrapper:

Syntax Example:

-Dhttp.proxyHost=httpprox.<3rd-level-domain>.<2nd-level-domain>
-Dhttp.proxyPort=8080
-Dhttp.nonProxyHosts="*.<3rd-level-domain>.<2nd-level-domain>|*.<domain_1>.<extension>|*.<domain_2>.<extension>"

There are two occurrences in which you may need to set the proxy settings:

Top of page

Configuring UDDI

The default behavior of the UDDI processing in CentraSite can be configured using global and local properties. These properties are set on the CentraSite Application Tier Server (CAST) where the UDDI Registry web application runs that handles UDDI client requests to CentraSite. If your environment contains more than one CAST, you can modify the properties on each CAST.

For information about setting up these properties, refer to the section Configuring the UDDI Environment in the document Access via UDDI.

Top of page

Setting Up the Eclipse Plug-Ins

The CentraSite distribution kit includes Eclipse plug-ins that allow you to use Eclipse as an alternative to CentraSite Control. You can either use the plug-ins with the Eclipse kit that is included in the CentraSite kit, or, if you already have an installed Eclipse environment, you can add the plug-ins to that environment.

The plug-ins follow the paradigms of the Eclipse Workbench: Views, editors, and a perspective are provided for displaying the contents of a CentraSite registry and repository. Actions can be carried out from context menus and toolbars. The working environment can be customized using standard Eclipse Workbench functions. For detailed information on the Eclipse Workbench, refer to the Workbench User Guide which comes with Eclipse.

The CentraSite Eclipse plug-ins include report design features which make use of the Business Intelligence and Reporting Tools (BIRT) provided by the Eclipse Foundation. You can find examples in the tutorials, which are in the Software AG documentation web site: http://documentation.softwareag.com/.

For general information about Eclipse, see http://www.eclipse.org/.

Installing the CentraSite Eclipse Plug-Ins

The CentraSite installation procedure includes an option to install the Software AG Designer component, which is an Eclipse installation tailored for CentraSite. If you did not select this option during the CentraSite installation, you can run the CentraSite installation procedure again, selecting just this option.

If the Software AG Designer has not yet been installed, run the Software AG Installer and select the Software AG Designer plus the CentraSite specific plug-ins as shown in the following screenshot. If you wish to perform CentraSite reporting using BIRT, select "SOA Governance" also.

graphics/ss2_2a.png

Installing the Software AG Designer will, among other actions, add a suitable entry to the Windows Start menu.

Using your Existing Eclipse Environment

If you already have an Eclipse working environment, you can install the CentraSite plug-ins in the existing environment rather than installing a new Eclipse from the CentraSite kit.

The distribution of CentraSite includes a set of Eclipse plug-ins for development purposes. The CentraSite Eclipse plug-ins provide a graphical user interface that you can use to create and manage the information in a CentraSite registry and repository.

The CentraSite Eclipse plug-ins can be used with Eclipse on any of the supported platforms.

Note:
Software AG recommends using the same version of Eclipse as Software AG Designer uses.

Installing Eclipse

The first prerequisite for Eclipse is a Java runtime environment (JRE), which can be downloaded from http://www.oracle.com/technetwork/java/index.html.

Eclipse (with the BIRT Report Designer plug-in) can be downloaded from eclipse project downloads (http://www.eclipse.org/downloads/). If you wish to use the CentraSite reporting feature (based on BIRT), you require the Eclipse IDE for Java and Report Developers. The Eclipse download page offers integrated packages that contain both BIRT and the required Eclipse software. If you do not wish to use the CentraSite reporting feature, you can use the Eclipse IDE for Java Developers.

Installing Eclipse simply copies a folder called eclipse into the file system. Consequently, uninstalling Eclipse simply means deleting this folder including all its subfolders.

Workspaces

The files that are created when working with Eclipse are contained in projects, which in turn are bundled in workspaces. An Eclipse workspace is a folder at an arbitrary location in the user's file system, though Eclipse suggests placing the workspace in a folder imaginatively called workspace under Documents and Settings/<userid> on the drive where Eclipse was installed. When you create an Eclipse project, the corresponding folder is created in the current workspace.

Installing CentraSite Eclipse Plug-ins

This software package includes plug-ins for the Eclipse environment (supported on Windows platforms only). These are unpacked to the installation directory and from there can be installed into your Eclipse platform. In order to use these plug-ins, the Eclipse SDK must be available as a prerequisite. Check the webMethodsSystem Requirements for the supported version of Java (http://documentation.softwareag.com/).

Start of instruction setTo install the CentraSite plug-ins in the Eclipse environment

  1. Start the Eclipse in which the plug-ins are to be installed.

  2. From the menu entry Help, select the item to install new software. This can be for example Install New Software or Software Updates, depending on the Eclipse version you are using.

    This takes you to the Available Software dialog. On some Eclipse versions, you might instead see the Software Updates and Add-ons dialog; if so, select the tab Available Software.

  3. Choose Add or Add Site. This takes you to the Add Repository dialog, where you specify the location of the plug-ins.

    Choose Archive and navigate to the following location: <SuiteInstallDir>/eclipse/updates. There you will find the zip file CentraSiteUpdateSite.zip. Select this file, and click Open to return to the Add Repository dialog, then click OK.

    The archive location can also contain optional language packs. If you need a language pack, install it using the same method as described here.

  4. Back in the Available Software dialog, you now see the SOA Governance category under which the plug-ins are listed.

    Click Select All, then click Next.

  5. You may be asked to confirm that you want to perform the installation, and that you agree to license conditions. Select the appropriate option to confirm. When the Finish button is enabled, click it to start the installation.

    In some cases you might need to restart Eclipse after the installation has completed, in order to activate the plug-in.

  6. You can now test that the installation was successful.

    To do this, first create a report project using File > New > Project > Business Intelligence and Reporting Tools > Report Project, then open the Report Design perspective.

    Now create a BIRT report using File > New > Report.

  7. Open the view Report Design > Data Explorer.

  8. Right-click Data Sources, then choose New Data Source from the context menu. The New Data Source dialog now displays the CentraSite data sources that you can use to create the XQuery for generating CentraSite reports.

  9. Select CentraSite XQuery from the list of data source types. Use the default data source name, then choose Next.

    Connection information about the CentraSite data source appears.

Important:
Before running the plug-ins, you must restart the Eclipse environment.

Connecting from Eclipse to CentraSite

Connection Configuration

To be able to connect the CentraSite data storage, it is necessary to establish a connection configuration. This is achieved in the Eclipse Preferences Dialog (reachable from the Window menu entry). This dialog automatically pops up when connection to the data storage is first requested.

In the Preferences dialog, expand the CentraSite node and click Connections. Then click Add to create a new connection. In the next popup, enter the following information:

graphics/ss2_2i.png

When you have entered these 3 fields, click OK. You will be asked to provide the password for the given user.

Choosing "Save password" avoids having to enter your password for future Eclipse sessions, but is not recommended in a security-sensitive environment.

You can check that a connection to CentraSite is possible by clicking the Test button.

Proxy Settings

In most scenarios the Eclipse environment's "Native" settings should provide for a flawless connection.

However, should you experience connection problems check the network connection settings (Window > Preferences > General > Network Connections).

The proxy settings should be the same as for the Application Server Tier. In this respect pay particular attention to the non-proxy host settings (see previous chapters of this section).

Starting to Work with the CentraSite Plug-ins for Eclipse

We recommend starting to work with the CentraSite Eclipse plug-ins by opening the CentraSite perspective. You can do this, for example, in the following way:

You can work with the CentraSite perspective just as you would work with any other perspective in the Eclipse Workbench. The Workbench remembers which views and perspectives you have opened, and how you have customized your working environment. The next time you open the Workbench, it appears as you have left it. For detailed information, refer to the Eclipse Workbench User Guide.

Getting Help

In the same way as the CentraSite Eclipse plug-ins are integrated in the Eclipse Workbench, their documentation is integrated in the help system of the Eclipse Workbench. The documentation is provided in a separate plug-in which is installed along with the software.

You can get help in the following ways:

Top of page

Installing the Adobe Flash Player

The graphical Impact Analysis feature of CentraSite requires the Adobe Flash Player, which is a third party web browser plug-in. If you do not already have the Flash Player version 8 or later installed, please install it from the Adobe web site at http://www.adobe.com/.

Top of page

Prerequisites for Reading the Online Documentation

Top of page

Problems with Blocked Content

Software AG documentation uses active content (JavaScript and Java applets). With Service Pack 2 (SP2) for Windows XP, Microsoft introduced a range of powerful new security features. One effect of these security features is that warning messages appear whenever you try to display HTML pages that use active content, for example Software AG documentation, in the Internet Explorer. A typical warning message that appears in the Internet Explorer information bar is:

Warning:
To help protect your security, Internet Explorer has restricted this webpage from running scripts or ActiveX controls that could access your computer. Click here for options...

To continue using the documentation, you can do one of the following:

Start of instruction setTo unblock active content

In the Microsoft Internet Explorer:

  1. Choose Tools> Internet Options.

  2. Choose the tab Advanced.

  3. Scroll down to the section Security.

  4. Check (tick) the box Allow active content to run in files on My Computer.

  5. Choose OK.

  6. Restart the Internet Explorer.

The warning messages should now no longer appear.

Top of page