Converting from Deployed to Development Mode

9

In Deployed mode, you can run your Redcell application, but in Development mode, you can customize it for your particular circumstances. You must have a development license to change a Deployed application to one for Development.

Follow these steps to convert Redcell from Deployed mode to Development mode:

1. Ensure you are in mixed mode (the property is in oware/lib/owmisc.properties)

2. Put the Redcell source JAR (rcdev.jar) file in the following directory:

$OWARE_USER_ROOT\owareapps\redcell\

3. In Windows, open a command shell and type oware to enter the bash environment. For Solaris, open a terminal window and type . /etc/.dsienv ([dot][space]/etc/.dsienv) to prepare your environment.

4. Run rcsetupdev

5. Run rcmake imports. This import Redcell classes into the OCC, where you can edit them.

rcinit no longer exists in Redcell. Use rcmake help to display all the general make targets, some of which may be useful to you as you re-build. This replaces rcinit. A printout of rcmake help appears below.

Component: RC.3.1.x.xx

Buildfile: d:\work\owareapps\redcell\src\rcbuild.xml

 

Command Line Options

--------------------

-help help on underlying ant system

-projecthelp comprehensive help on targets

-noocc skip building temp jar; assume a valid temp jar already exists

-nover skip generating version information class; assume one already exists

 

Basic Target Overview

---------------------

help ................ displays this overview

clean ............... removes class files and jars from disk

imports ............. imports OCC export files into meta and classes databases

core ................ creates occ.jar, generates IRCVersion.class and calls core.compile

dbseed .............. seeds application data

dbrefresh ........... DATA WILL BE LOST - calls dbreset.data and then dbseed to restore default data

dbreset ............. DATA WILL BE LOST - resets all databases (loaddb)

dbreset.data ........ DATA WILL BE LOST - resets busdb and cntl databases; then calls dbseed.prime

cleanbuild .......... DATA WILL BE LOST - resets all databases then calls imports, clean and core

cleanbuild.seed ..... DATA WILL BE LOST - convenience target; calls cleanbuild, dbseed.prime and dbseed

alljars ............. builds jar targets for deployed execution

dbschema............. generates SQL files under d:/work/owareapps/redcell/db/<dbms> directory

javadocs ............ generates javadocs under d:/work/owareapps/redcell/docs/javadocs

metadocs ............ generates metadocs under d:/work/owareapps/redcell/docs/metadocs

release ............. stages files for release under d:/work/owareapps-release/RC

cleanbuild.release .. DATA WILL BE LOST - convenience target for SCM (no seeding)

test.deploy ......... DATA WILL BE LOST - calls alljars, dbreset, core.clean, dbseed.prime and dbseed

test.classpath ...... for debugging compile issues; displays content of classpath variables

 

Redcell Custom Targets

----------------------

rco.jar ............... builds RCOApplet.jar in owareapps dir; called by base 'alljars' target

rc.meta.imports ....... imports classes, calls rc.core.precompile and then imports remaining meta

rc.clean.extras ....... removes RCOApplet.jar file; called by base 'clean' target

rc.release.installer .. releases installer; called by base 'release' target