Installation Guide

Two Steps – Environment and CaptainCasa itself

CaptainCasa is a J2EE-Servlet based framework. Applications require some Java runtime environment and some servlet container into which they are deployed.

As consequence CaptainCasa comes with two types of installation files:

When installing CaptainCasa Enterprise Client the first time then you need to execute both installation steps – one after the other. When later on installing updates of CaptainCasa you do not need to re-install the environment components a second time – you just need to install the CaptanCasa part.

Windows Installation

If you already have installed CaptainCasa then stop the corresponding Tomcat instances before installation.

Install Environment Components

Execute the setup of the environment components:

During the installation you are prompted for a directory into which CaptainCasa will be installed (default “C:\EnterpriseClientRISC”). When selecting some own directory: do NOT use a directory location within the Windows “Program Files” of “Program Files (x86)” folder.

Install CaptainCasa Enterprise Client itself

Execute the setup of CaptaiNCasa Enterprise Client:

During the installation you are prompted for a directory. Use the same directory that you used for the environment installation. It is automatically proposed by the installation wizard.

Run Enterprise Client RISC - Demo Workplace

The Demo Workplace shows the features of CaptainCasa Enterprise Client CC. It contains a lot of useful information and code snippets how to use components and how to develop concrete scenarios.


Start the Tomcat instance that provides the demo workplace (and that by default will include the web applications that you develop on your own).

Now start the browser showing the demo application:

The page will present a list of links to the demos, select one of them and you will see the corresponding demos.

For best performance: minimize the Tomcat instance (DOS-Box). The log output that is shown for demo purpose takes a quite significant amount of resources.

Run Enterprise Client RISC - Toolset

The CaptainCasa Enterprise Client Toolset is the environment for creating dialogs and binding them to your application processing.



Start the Tomcat instance that provides the toolset.

Now start the browser showing the toolset application:

Linux / Mac OS Installation

If you already have installed CaptainCasa then stop the corresponding Tomcat instances before installation.

Install Environment Components

Create a directory in which you want to place the CaptainCasa installation.

Example (assuming the installation directory is “/opt/EnterpriseClientRISC” and assuming the downloaded field is in the “/home/xyz” directory):

cd /opt

mkdir EnterpriseClientRISC

cd EnterpriseClientRISC

tar -xvf /home/xyz/EnterpriseClientRISC_JRE11Tomcat9.tar.gz

 

Of course you can use any other directory – both for placing the CaptainCasa installation and for keeping the download file.

Install CaptainCasa Enterprise Client itself

Execute the setup of CaptainCasa Enterprise Client:

Example (assuming the installation directory is “/opt/EnterpriseClientRISC” and assuming the downloaded field is in the “/home/xyz” directory):

cd /opt/EnterpriseClientRISC

tar -xvf /home/xyz/EnterpriseClientRISC_6_0_20190812.tar.gz

 

Run Enterprise Client RISC - Demo Workplace

Start the Tomcat instance that provides the demo workplace (and that by default will include the web applications that you develop on your own).

cd /opt/EnterpriseClientRISC

./A_startserver.sh

 

Now start the browser and open URL:

http://localhost:50000/demos/indexRISC.html

Run Enterprise Client RISC - Toolset

Start the Tomcat instance that provides the toolset.

cd /opt/EnterpriseClientRISC

./C1_starttoolsserver.sh

 

Now start the browser and open URL:

http://localhost:51000/editor/indexRISC.html

Details on installation

Installed directories and files

Maybe you want to take a look into the installation directory:

<installdirectory>

  /documentation

  /resources

    ...

    /eclipseplugin

  /server

    /jre

    /tomcat

    /tomcattools

  A_startserver.bat

  …

 

Default Tomcat configuration

The Tomcat instance for running the applications occupies ports in the 5000* area. The default HTTP-port is “50000”.

The Tomcat instance for running the toolset occupies ports in the 5100* area. The default HTTP-port is “51000”.

In general we recommend to keep the ports as defined when testing / developing with CaptainCasa Enterprise Client RISC. In case of conflicts within your environment you may update the ports by updating the file <tomcat>/conf/server.xml.

Eclipse Plugin

CaptainCasa comes with a little plugin to simplify the development with Eclipse.

What does the plugin do?

The tools of CaptainCasa are operating on the same directory that also used by the corresponding Eclipse project. Whenever a change (e.g. to a layout definition) is done within the CaptainCasa tools, a “signal file” is written into the project folder. The pluging scans this “signal file” and automatically refreshes the project.

Result: changes due to CaptainCasa tools are automatically scanned and lead to an updated of the Eclipse project – you do not have to manually refresh the project against the file system.

Why is there no plugin for NetBeans and IDEA?

...the scanning of the project files is done automatically by both of the tools in a fast way – there is no need for plugin to trigger this.

Installation

The plugin is part of the “/resources” folder, the name is “org.eclnt.eclipseplugin.zip”.

Eclipse <= 4.4 (Luna)

If using Eclipse <= 4.4 (Luna): Unzip the file into your eclipse installation directory.

Eclipse >= 4.5 (Mars)

Copy the .jar file contained in the zip-file into the /dropins-folder of your Eclipse installation directory.

Running the plugin

After coying the file and restarting Eclipse, you need to start the plugin. Then open the menu...



...and select the CaptainCasa plugin:

After opening, press the “Start” button within the plugin:

You will see the tool scanning for changes regularly.