Creating Applications

http://<server name>/<scripts directory>/#proj

http://heartofgold/scripts/myproject

Oracle Cartridges

To deploy an Oracle Web Cartridge you will need an Oracle Web Server (available at the time of writing for Solaris and Windows NT systems) to deploy to.

Setting Project Options to create an Oracle Web Cartridge

After the above steps are taken you can now build a Sapphire project to create a Web Cartridge. Check these settings in your Project Options:

Makefile Tag

Makefile.$SA_DEPLOYMENT_TARGET: drop this down and select WRBAPI2x.

Makefile.exeSuffix: remove this setting

Test and Release Tags

Sapphire/Web will generate a .DLL file that you must copy to the directory that your Oracle Web Server expects to see cartridges in. You must then register your cartridge with the server.

Application Servers

This is a schematic of a possible Web Site, showing the relationships between the various types of application that you can use Sapphire/Web to generate.

• The Web Server Extension shown is the Sapphire/Web NSAPI PlugIn.

• App. Srvr. 1 and App. Srvr. 2 are Application Servers being used by the Web Server. The PlugIn checks to see that they exist and then hands off all processing to them. If a required Application Server is not running, the PlugIn contacts the App. Server Manager, which starts the required program. After this the PlugIn can continue as before.

Both the PlugIn and the Application Server Manager use the Config. File to determine how an Application Server should be started and communicated with.

• The Oracle Web Cartridge needs an Oracle Web Server and Web Request Broker (the equivalent of the Server and Plugin shown here).

• The App. Server Manager Console (described later in this chapter) is used by the system administrator to control the use of resources by the system. This program offers a number of useful features:
  • Any number of instances of an Application Server can be prepared for launching.
  • An instance is only launched on demand (when there is a user waiting and not all prepared instances are running).
  • Application Server instances can be configured at their creation to endure a given amount of time after their last use before automatically shutting down
  • Application Servers can be configured at their creation to shut down after a total of a certain number of requests.

• The System Administrator can use the Application Server Manager Console to obtain information on the running instances.