Login
Register
Actian.comNavigation
Learn About
Developing With
Ingres Talk
Information
Toolbox
Views
Workbench Express 1.0 Setup
From Ingres Community Wiki
Press here to return to Workbench Express Home Page
Workbench Express 1.0 Overview
Workbench Express is designed to provide previews of in-progress development of new OpenROAD features. It is a standalone package that can be installed side-by-side with an existing OpenROAD installation. Workbench Express contains an embedded version of the Ingres Client and does not rely on the presence of an existing Ingres instance.
Workbench Express 1.0 Summary
There are several versions of Workbench Express that are being made available. Each of these can be installed at the same time. The versions of Workbench Express are as follows:
- Workbench Express for Sprint - This version is built from the code line that is used during the OpenROAD Development sprints. It contains a number of features developed by partners that are unreleased or not integrated into the production code lines.
- Workbench Express for Special - This version is used for special internal projects.
- Workbench Express for Community - This version represents the stable Community version of OpenROAD.
- Workbench Express for Unicode - This version is based on the Unicode version of OpenROAD. It can support Unicode, Multibyte and Singlebyte datatypes. The other code lines can only support Singlebyte datatypes.
- Workbench Express for Main - This is the main code line that is used to cross integrate features that have been developed in other code lines.
- Workbench Express for Builder - This code line contains enhancements designed to enhance the application development capabilities of OpenROAD.
- Workbench Express for XML - This code line was used to develop the XML capability. This feature has been cross integrated into the previously listed code lines.
Each of these versions of Workbench Express will be available for download.
In the following examples, the Workbench Express for Unicode will be referred. Change the references to the other versions if they are being installed and used.
Workbench Express 1.0 Features
- Microsoft Installer Support
- Fused Runtime
- Query Tool Runtime for Windows
- Embedded Ingres 10.0 Client
- Query Tool Administration Command Window
- Workbench Application Development
- Rundbapp Support
- Documentapp Support
- Compileapp Support
- Backupapp Support
- Optional Packaging of PDF Documentation
- ODBC Driver
- ODBC Driver Administrator shortcut
- Network Utility for Batch operations
- Terminal Monitor for Batch Operations
- Can be configured for WIN1252 or UTF8 character set support
- Links to Ingres Product Documentation and various Wiki pages
Workbench Express 1.0 Supported Environments
- Windows XP (32-bit and 64-bit)
- Windows Server 2003 (32-bit and 64-bit)
- Windows Vista (32-bit and 64-bit with UAC turned off)
- Windows Vista (32-bit and 64-bit with UAC turned on and installation into a non-default location)
- Windows Server 2008 (32-bit and 64-bit with UAC turned off)
- Windows Server 2008 (32-bit and 64-bit with UAC turned on and installation into a non-default location)
- Windows 7 (32-bit and 64-bit with UAC turned off)
- Windows 7 (32-bit and 64-bit with UAC turned on and installation into a non-default location)
Workbench Express 1.0 does not require a previously installed copy of Ingres. Workbench Express does not have any dependencies on the default II_SYSTEM.
Note: An enhancement is under development that will provide full UAC support.
HOW TO: Install Workbench Express
Workbench Express has been packaged as a Microsoft Installer-based package. There are serveral versions of Workbench Express. Each version is based on a different codeline that is used by the OpenROAD Development group to develop new features.
The following table lists the Name of each version of Workbench Express, the value of the Ingres Installation Code for the embedded Ingres Net Client and the Name of the ODBC Driver associated with the embedded Ingres Net Cleint.
| Workbench Express Version | Installation Code | Ingres Service Name | ODBC Driver Name |
|---|---|---|---|
| Workbench Express for Sprint | WD | Ingres_Net_WD | Ingres WD |
| Workbench Express for Special | WS | Ingres_Net_WS | Ingres WS |
| Workbench Express for Commuinity | WM | Ingres_Net_WM | Ingres WM |
| Workbench Express for Unicode | WC | Ingres_Net_WC | Ingres WC |
| Workbench Express for Main | WF | Ingres_Net_WF | Ingres WF |
| Workbench Express for Builder | WT | Ingres_Net_WT | Ingres WT |
| Workbench Express for XML | WX | Ingres_Net_WX | Ingres WX |
The following section describes how to install this package.
Begin the Installation
Download the zip file that contains the version of Workbench Express that you desire to install. Unzip this file into a directory. Locate the setup.exe file and double-click this to begin the installation process. You will see the following when the installer begins.
Accept End User License
You will need to read and accept the Enter User License to continue with the installation of Workbench Express.
Choose Setup Type
There are three setup types that you will need to choose. These setup types are as follows:
- Typical - Choose this option if you want to install the default features and place Workbench Express in the default location.
- Custom - Chose this option if you want to modify any features and/or the installation location.
- Complete - Choose this option if you wnat all features and installation into the default location.
Choose Custom in this example.
Custom Setup
Make any modifications that you want using this option.
Ready to install Workbench Express
Press the Install button to begin the installation of Workbench Express.
Installing Workbench Express
The following frame will provide the status of the installation progress of Workbench Express.
Configuration of the the Ingres Net Client
The following popup will appear when the Ingres Net Client is being configured. Each version of Workbench Express has a hard coded Ingres Installatino Code.
Installation is Complete
HOW TO: Create a Vnode to Access Your Database
After the installation of Workbench Express has completed, the embedded Ingres Net Client will have been installed as a service, Configured and started automatically. The first thing that must be done is to use Query Tool to ensure that the Ingres Net Client is running and create an Ingres Vnode to access the Ingres or Enterprise Access Server that will be used.
Start Query Tool
Use the following shortcut to start Query Tool,
Start-->Programs-->Ingres-->Workbench Express for Unicode-->Query Tool Unicode
The following will appear
Launch the Query Tool Virtual Node Assistant
Welcome to the Virtual Node Assistant
Enter the Name of the Virtual Node
Enter an arbitrary string that will be the name of the virtual node. In this example the value localhostCP will be used.
Enter the Virtual Node Type
A Global vndoe can be seen by any authenticated user on the local system. A Private vnode can only be seen by the user who created it. In this example we will create a Global vndoe.
Enter the Virtual Ndoe Authorization
Enter the username and password that will be passed to the Ingres or Enteprise Access that will be used to authenticate access by the client.
Enter the Machine Name
This is the name, or IP address of the machine where the Ingres or Enterprise Access server resides. In this example the value localhoist is used.
Enter the Virtual Node Protocol
This is the protocol that the Ingres Net Client will use to access the Ingres or Enteprise Access server. The value tcp_ip is recommended.
Enter Virtual Node Listen Address
Enter the address that the Ingres or Enterprise Access Server Net is listening for inbound connections. In this example the value CP is used.
Virtual Node Completed
The information needed to create the Virtual Node has now been gathered. Press the Ok button to complete the creation of the virtual node.
Use Test Button to See if the Vnode works
Use the Test button to see fi the vnode works.
If the connection is successful then the following will appear
If the connection is *not* successful then the following will appear
Use Query Tool to Open the Vnode
Open the tree next to the newly created vnode. Query Tool will connect to the server and provide a list of running servers and any databases that may be available. If the vnode was created successfully you will see some that appears similar to the following.
HOW TO: Load the Sample Applications
Once the access to the Ingres or Enterprise Access server has been confirmed by using Query Tool, we are ready to proceed to loading the selected database with the sample applications. In the the following examples we will use the locallhostCP::qtdemo/ingres database. This database was created an an Ingres Server independent of Workbench Express.
Launch Workbench Express Command Window
The Workbench Express command window will be used for the steps in this section. To launch this window use the following shortcut,
Start-->Programs-->Ingres-->Workbench Express for Unicode-->Workbench Express Unicode Command Window
The following will appear in a command window,
USAGE: workbenchexpress
workbench -Tmin -L"%II_LOG%\workbenchexpress_%RANDOM%.log"
workbenchexpress /dev
workbenchexpress /dev "%II_SYSTEM%"
w4glapp.exe rundbapp -Tmin -L"%II_LOG%\rundbapp_%RANDOM%.log" {DBNAME} {DBAPP}
workbenchexpress /run {DBNAME} {DBAPP}
workbenchexpress /run {DBNAME} {DBAPP} "%II_SYSTEM%"
backupapps
backupapps /?
backupapps /h
qt -Tmin -L"%II_LOG%\qt_%RANDOM%.log"
workbenchexpress /qt
workbenchexpress /qt "%II_SYSTEM%"
workbenchexpress /qtadmin
workbenchexpress /qtadmin "%II_SYSTEM%"
qtadmin /start
qtadmin
irunnerc -/appflags {scriptname} [script appflags]
sql DATABASE
sql DATABASE < INPUTFILE
sql DATABASE < INPUTFILE >OUTPUTFILE
netutil
iinamu
iinamu -v vnodename
iinamu show servers
iinamu show servers -v vnodename
Use workbenchexpress /? for a more detailed usage.
Run the qtadmin command Script
The qtadmin.bat script will be used to help determine some the of characteristics of the local Net Client and the remote server. When the following command is entered,
qtadmin
The following will appear,
qtadmin
USAGE: qtadmin
qtadmin /servers
qtadmin /vnodes
qtadmin /databases DATABASE
qtadmin /applications DATABASE
qtadmin /check
qtadmin /check DATABASE
qtadmin /qtdemo DATABASE
qtadmin /qtdemo /cmdemo DATABASE
qtadmin /qtdemo /cmdemo /all DATABASE
qtadmin /start
qtadmin /verbose
qtadmin /help
qtadmin /usage
qtadmin /?
irunnerc -/appflags SCRIPTNAME
irunnerc -/appflags SCRIPTNAME -dDATABASE
sql DATABASE
sql DATABASE < INPUTFILE
sql DATABASE < INPUTFILE >OUTPUTFILE
iinamu show servers
iinamu show servers -v VNODENAME
The qtadmin.bat script is a script that will assist in the following actions
1. Verifies that Query Tool is installed.
2. Load demo data that can be used by Query Tool.
3. Can optionally create a demo database if it is running in a full Ingres installation.
4. Checks and reports on the Client and Server enviornments.
It is designed to be a script that can be run from the Workbench Express or Query Tool
Command Prompt.
The parameters can be specified in any order. If no parameters are specified then a short usage
is displayed.
Use (qtadmin /help) to display a more detailed usage.
Run qtadmin /servers
Run the command,
qtadmin /servers
to get a list of the running local servers
qtadmin /servers ====================================================================================== qtadmin: The following options were selected by qtadmin -------------------------------------------------------------------------------------- OPTION_DBNAME = qtdemodb OPTION_QTDEMO = TRUE OPTION_SERVERS = TRUE -------------------------------------------------------------------------------------- Local Server Status ----------------------------------------------------------------------------- Server Port Address ------ --------------------------------------------------- COMSVR * WC\COMSVR\6d4 IINMSVR * WC\NMSVR\78 -----------------------------------------------------------------------------
Run qtadmin /vnodes
Run the command,
qtadmin /vnodes
To get the list of Global and Private vnodes defined. (A vnode should have been created in the previous section by using Query Tool.)
qtadmin /vnodes ====================================================================================== qtadmin: The following options were selected by qtadmin -------------------------------------------------------------------------------------- OPTION_DBNAME = qtdemodb OPTION_QTDEMO = TRUE OPTION_VNODES = TRUE -------------------------------------------------------------------------------------- Locally Defined Global and Private Vnode(s) for ingres ----------------------------------------------------------------------------- Type Vnode ---- -------------------------------------------------------------------- Global localhostCP -----------------------------------------------------------------------------
Run qtadmin /databases against iidbdb
Use the vnode value returned from the qtadmin /vnodes and run the following command
qtadmin /databases localhostCP::iidbdb
This will connect the the remote server and obtain a list of databases. (If the remote server is not an Ingres DBMS, you may need to appear the Enterprise Access Server class.)
qtadmin /databases localhostCP::iidbdb ====================================================================================== qtadmin: The following options were selected by qtadmin -------------------------------------------------------------------------------------- OPTION_DBNAME = localhostCP::iidbdb OPTION_QTDEMO = TRUE OPTION_DATABASES = TRUE -------------------------------------------------------------------------------------- Derived IIDBDB = localhostCP::iidbdb/ingres ----------------------------------------------------------------------------- iidatabase.name = localhostCP::demodb/ingres iidatabase.name = localhostCP::iidbdb/ingres iidatabase.name = localhostCP::imadb/ingres iidatabase.name = localhostCP::qtdemo/ingres -----------------------------------------------------------------------------
Run qtadmin /databases against the selected database
Run the following command,
qtadmin /databases localhostCP::qtdemo/ingres /verbose
This command will return detailed information about the target database.
qtadmin /databases localhostCP::qtdemo/ingres /verbose ====================================================================================== qtadmin: The following options were selected by qtadmin -------------------------------------------------------------------------------------- OPTION_DBNAME = localhostCP::qtdemo/ingres OPTION_QTDEMO = TRUE OPTION_VERBOSE = TRUE OPTION_DATABASES = TRUE -------------------------------------------------------------------------------------- qtadmin: Capabilities of Local Ingres Client ----------------------------------------------------------------------------- II_SYSTEM = C:\PROGRA~1\Ingres\WORKBE~1 CLIENT_CHARSET = WIN1252 CLIENT_TYPE = II CLIENT_VERSION = 10.0.0 CLIENT_NMSVR_PORT = WC\NMSVR\78 CLIENT_COMSVR_PORT = WC\COMSVR\6d4 ----------------------------------------------------------------------------- qtadmin: Capabilities of Target Server localhostCP::qtdemo/ingres ----------------------------------------------------------------------------- DEFAULT_VNODE = localhostCP DEFAULT_DBNAME = qtdemo DEFAULT_SERVER = ingres SERVER_VERSION = 10.0.0 DBMS_CHARSET = WIN1252 DBMS_NORMALIZATION = NFC DBMS_VERSION = II 10.0.0 int.w32/125 COMMON/SQL_LEVEL = 01000 DBMS_TYPE = INGRES DB_DELIMITED_CASE = LOWER DB_NAME_CASE = LOWER DB_REAL_USER_CASE = LOWER DISTRIBUTED = N ESCAPE = Y INGRES = Y INGRES_AUTH_GROUP = Y INGRES_AUTH_ROLE = Y INGRES_LOGICAL_KEY = Y INGRES/QUEL_LEVEL = 01000 INGRES_RULES = Y INGRES/SQL_LEVEL = 01000 INGRES_UDT = Y MAX_COLUMNS = 1024 MIXEDCASE_NAMES = N NATIONAL_CHARACTER_SET = Y OPEN/SQL_LEVEL = 00904 OWNER_NAME = QUOTED PHYSICAL_SOURCE = T QUEL_LEVEL = II10.0.0 SAVEPOINTS = Y SQL_LEVEL = II10.0.0 SQL_MAX_BYTE_COLUMN_LEN = 32000 SQL_MAX_BYTE_LITERAL_LEN = 32000 SQL_MAX_CHAR_COLUMN_LEN = 32000 SQL_MAX_CHAR_LITERAL_LEN = 32000 SQL_MAX_COLUMN_NAME_LEN = 256 SQL_MAX_DECIMAL_PRECISION = 39 SQL_MAX_NCHR_COLUMN_LEN = 16000 SQL_MAX_NVCHR_COLUMN_LEN = 16000 SQL_MAX_ROW_LEN = 262144 SQL_MAX_SCHEMA_NAME_LEN = 32 SQL_MAX_STATEMENTS = 0 SQL_MAX_TABLE_NAME_LEN = 256 SQL_MAX_USER_NAME_LEN = 32 SQL_MAX_VBYT_COLUMN_LEN = 32000 SQL_MAX_VCHR_COLUMN_LEN = 32000 STANDARD_CATALOG_LEVEL = 01000 UNIQUE_KEY_REQ = N ----------------------------------------------------------------------------- Derived IIDBDB = localhostCP::iidbdb/ingres ----------------------------------------------------------------------------- iidatabase.name = localhostCP::demodb/ingres iidatabase.name = localhostCP::iidbdb/ingres iidatabase.name = localhostCP::imadb/ingres iidatabase.name = localhostCP::qtdemo/ingres -----------------------------------------------------------------------------
Run qtadmin /applications
See if there are OpenROAD applications present in the target database by running the following command,
qtadmin localhostCP::qtdemo/ingres /applications
(Notice that there are no 4GL applications present in this database at this point.)
qtadmin localhostCP::qtdemo/ingres /applications ====================================================================================== qtadmin: The following options were selected by qtadmin -------------------------------------------------------------------------------------- OPTION_DBNAME = localhostCP::qtdemo/ingres OPTION_QTDEMO = TRUE OPTION_APPLICATIONS = TRUE -------------------------------------------------------------------------------------- 4GL Applications(s) in database localhostCP::qtdemo/ingres ----------------------------------------------------------------------------- -----------------------------------------------------------------------------
Run backupapps
The backupapps.bat script can be used to import, export, document and compile 4GL applications. Enter the follwoing command
backupapps
This will display a summary usage for this script.
backupapps
USAGE:
backupapps
backupapps [ parm1 { parm2 } ] ... [ parmN { parmN+1 } ]
backupapps /unload /dbname databasename
backupapps /reload /dbname databasename
backupapps /compile /dbname databasename
backupapps {MANDATORY SWITCHES} /backupdir <backup directory name>
backupapps {MANDATORY SWITCHES} /format <export format>
backupapps {MANDATORY SWITCHES} /document <documentapp control>
backupapps {MANDATORY SWITCHES} /listappls <application list file name>
backupapps {ALL PREVIOUS SWITCHES} /simulate
backupapps /?
backupapps /h
Example of reloading 4gl and qtsrc sample applications would be as follows:
backupapps /reload /backupdir "%OR_SYSTEM%\openroad\w4glsamp\4gl" /dbname DATABASENAME
Provide a valid value for DATABASENAME to run this command.
Example of compielapp all applications in a database:
backupapps /compile /dbname DATABASENAME
Provide a valid value for DATABASENAME to run this command.
This script can be used to unload, reload or compileappp a 4GL database using the w4glapp.exe utility.
Issue backupapps /h for a detailed usage.
Reload the Sample 4GL Applications
Several sample applications were installed by default by the Workbench Express installer. The sample applications that are provided are as follows,
- complib
- Connect1
- Connect2
- DemoXml
- Finance
- GolfCard
- Intertask1
- Intertask2
- Jigfall
- MastDetl
- Minesweeper
- Misc
- qt
- SimpleBrowser
- Stat
- Utility
Use the following command to reload these applications into the previously selected database,
backupapps /reload /backupdir "%OR_SYSTEM%\openroad\w4glsamp\4gl" /dbname localhostCP::qtdemo/ingres
This command will load the sample 4GL applications. (Note: These applications are supplied in XML export format. The backupapps.bat script can load or unload in either XML or EXP format.)
backupapps /reload /backupdir "%OR_SYSTEM%\openroad\w4glsamp\4gl" /dbname localhostCP::qtdemo/ingres backupapps Sat 08/28/2010 2:09:58.51: /RELOAD4GL switch has been set... backupapps Sat 08/28/2010 2:09:58.53: /BACKUPDIR switch has been set... backupapps Sat 08/28/2010 2:09:58.53: /DBNAME switch has been set... backupapps Sat 08/28/2010 2:09:58.54: BACKUPDIR = C:\PROGRA~1\Ingres\WORKBE~1\openroad\w4glsamp\4gl backupapps Sat 08/28/2010 2:09:58.54: DBNAME = localhostCP::qtdemo/ingres backupapps Sat 08/28/2010 2:09:58.54: GENLISTAPPLS = TRUE ======================================================================================================= backupapps Sat 08/28/2010 2:09:58.56: Reload the 4GL database using the generated application list ------------------------------------------------------------------------------------------------------- w4glapp backupapp in localhostCP::qtdemo/ingres complib complib.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Connect1 Connect1.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Connect2 Connect2.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres DemoXml DemoXml.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Finance Finance.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres GolfCard GolfCard.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Intertask1 Intertask1.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Intertask2 Intertask2.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Jigfall Jigfall.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres MastDetl MastDetl.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Minesweeper Minesweeper.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Misc Misc.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres qt qt.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres SimpleBrowser SimpleBrowser.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Stat Stat.xml -xml ... w4glapp backupapp in localhostCP::qtdemo/ingres Utility Utility.xml -xml ... ------------------------------------------------------------------------------------------------------- backupapps Sat 08/28/2010 2:10:20.21: All applications are reloaded =======================================================================================================
Compile the loaded 4GL applications in the database
After the 4GL applications have been loaded, it is recommended that they be compiled. This will improve the startup performance if the applications are run from the database using the rundbapp functionality provided by the w4glapp.exe utility.
Use the following command to compile all of the applications in the target database,
backupapps /compile /dbname localhostCP::qtdemo/ingres
(Note: backupapps.bat will connect to the target database, obtain a list of 4GL applications and use that list to compile the applications.)
backupapps /compile /dbname localhostCP::qtdemo/ingres backupapps Sat 08/28/2010 2:13:37.89: /COMPILE4GL switch has been set... backupapps Sat 08/28/2010 2:13:37.89: /DBNAME switch has been set... backupapps Sat 08/28/2010 2:13:37.90: BACKUPDIR = C:\DOCUME~1\ingres\backupapps backupapps Sat 08/28/2010 2:13:37.92: DBNAME = localhostCP::qtdemo/ingres backupapps Sat 08/28/2010 2:13:37.92: GENLISTAPPLS = TRUE ======================================================================================================= backupapps Sat 08/28/2010 2:13:37.92: Connect to localhostCP::qtdemo/ingres and generate application list backupapps Sat 08/28/2010 2:13:38.53: Compileapp the 4GL database using the generated application list ------------------------------------------------------------------------------------------------------- w4glapp compileapp localhostCP::qtdemo/ingres Connect1 -f ... w4glapp compileapp localhostCP::qtdemo/ingres Connect2 -f ... w4glapp compileapp localhostCP::qtdemo/ingres DemoXml -f ... w4glapp compileapp localhostCP::qtdemo/ingres Finance -f ... w4glapp compileapp localhostCP::qtdemo/ingres GolfCard -f ... w4glapp compileapp localhostCP::qtdemo/ingres Intertask1 -f ... w4glapp compileapp localhostCP::qtdemo/ingres Intertask2 -f ... w4glapp compileapp localhostCP::qtdemo/ingres Jigfall -f ... w4glapp compileapp localhostCP::qtdemo/ingres MastDetl -f ... w4glapp compileapp localhostCP::qtdemo/ingres Minesweeper -f ... w4glapp compileapp localhostCP::qtdemo/ingres Misc -f ... w4glapp compileapp localhostCP::qtdemo/ingres SimpleBrowser -f ... w4glapp compileapp localhostCP::qtdemo/ingres Stat -f ... w4glapp compileapp localhostCP::qtdemo/ingres Utility -f ... w4glapp compileapp localhostCP::qtdemo/ingres complib -f ... w4glapp compileapp localhostCP::qtdemo/ingres qt -f ... ------------------------------------------------------------------------------------------------------- backupapps Sat 08/28/2010 2:15:53.43: All applications have been compiled =======================================================================================================
Run qtadmin /applications
We can now use the qtadmin.bat script to obtain a list fo applications present in the target database. Use the following command,
qt'dmin localhostCP::qtdemo/ingres /applications'
qtadmin localhostCP::qtdemo/ingres /applications ====================================================================================== qtadmin: The following options were selected by qtadmin -------------------------------------------------------------------------------------- OPTION_DBNAME = localhostCP::qtdemo/ingres OPTION_QTDEMO = TRUE OPTION_APPLICATIONS = TRUE -------------------------------------------------------------------------------------- 4GL Applications(s) in database localhostCP::qtdemo/ingres ----------------------------------------------------------------------------- complib Connect1 Connect2 DemoXml Finance GolfCard Intertask1 Intertask2 Jigfall MastDetl Minesweeper Misc qt SimpleBrowser Stat Utility -----------------------------------------------------------------------------
HOW TO: Run the Sample Applications from the Database
We are now ready to run some of the loaded applications directly from the database using the workbenchexpress.bat script. THe following sections will show how to do this.
Run workbenchexpress to obtain the usage
Run the followng command to get the workbenchexpress usage summary,
workbenchexpress
workbenchexpress
USAGE: workbenchexpress
workbench -Tmin -L"%II_LOG%\workbenchexpress_%RANDOM%.log"
workbenchexpress /dev
workbenchexpress /dev "%II_SYSTEM%"
w4glapp.exe rundbapp -Tmin -L"%II_LOG%\rundbapp_%RANDOM%.log" {DBNAME} {DBAPP}
workbenchexpress /run {DBNAME} {DBAPP}
workbenchexpress /run {DBNAME} {DBAPP} "%II_SYSTEM%"
backupapps
backupapps /?
backupapps /h
qt -Tmin -L"%II_LOG%\qt_%RANDOM%.log"
workbenchexpress /qt
workbenchexpress /qt "%II_SYSTEM%"
workbenchexpress /qtadmin
workbenchexpress /qtadmin "%II_SYSTEM%"
qtadmin /start
qtadmin
irunnerc -/appflags {scriptname} [script appflags]
sql DATABASE
sql DATABASE < INPUTFILE
sql DATABASE < INPUTFILE >OUTPUTFILE
netutil
iinamu
iinamu -v vnodename
iinamu show servers
iinamu show servers -v vnodename
Use workbenchexpress /? for a more detailed usage.
Run workbenchexpress /run to launch the Jigfall application
Use the following command to run the Jigfall application from the database,
workbenchexpress /run localhostCP::qtdemo/ingres Jigfall
workbenchexpress /run localhostCP::qtdemo/ingres Jigfall workbenchexpress: II_SYSTEM = C:\PROGRA~1\Ingres\WORKBE~1 workbenchexpress: OR_SYSTEM = C:\PROGRA~1\Ingres\WORKBE~1 workbenchexpress: II_LOG = C:\Documents and Settings\ingres workbenchexpress: II_W4GLAPPS_DIR = C:\PROGRA~1\Ingres\WORKBE~1\openroad\bin workbenchexpress: II_W4GLAPPS_SYS = C:\PROGRA~1\Ingres\WORKBE~1\openroad\bin workbenchexpress: DBNAME = localhostCP::qtdemo/ingres workbenchexpress: DBAPP = Jigfall Start w4glapp.exe rundbapp -Tmin -L"C:\Documents and Settings\ingres\rundbapp_31945.log"
Jigfall Application Launched
The Jigfall application should launch within a few seconds. The application components are being fetched from the application database.
Run workbenchexpress /run to launch the Query Tool application
Use the following command to launch the qt (Query Tool) application directly from the database,
workbenchexpress /run localhostCP::qtdemo/ingres qt
workbenchexpress /run localhostCP::qtdemo/ingres qt workbenchexpress: II_SYSTEM = C:\PROGRA~1\Ingres\WORKBE~1 workbenchexpress: OR_SYSTEM = C:\PROGRA~1\Ingres\WORKBE~1 workbenchexpress: II_LOG = C:\Documents and Settings\ingres workbenchexpress: II_W4GLAPPS_DIR = C:\PROGRA~1\Ingres\WORKBE~1\openroad\bin workbenchexpress: II_W4GLAPPS_SYS = C:\PROGRA~1\Ingres\WORKBE~1\openroad\bin workbenchexpress: DBNAME = localhostCP::qtdemo/ingres workbenchexpress: DBAPP = qt Start w4glapp.exe rundbapp -Tmin -L"C:\Documents and Settings\ingres\rundbapp_21817.log"
qt application (Query Tool) Launched
This instance of Query Tool should behave the same as the version launched by qt.exe.
HOW TO: Setup the Use of Workbench Express Application Development
We are now ready to start Workbench Express Application Development. This functionality is supplied by the workbench.exe application.
The workbench.exe differs from the OpenROAD Workbench Development environment is several key aspects:
- You cannot create OpenROAD image files using workbench.exe
- You cannot create OpenROAD eClient applications using workbench.exe
- You cannot use the batch builder capability using workbench.exe
- You cannot manage the OpenROAD Application Server from workbench.exe
- The workbench.exe utility uses the orrun.dll library instead of the or4glnt.dll library
Other than these differences the Workbench Express Application Development environment is very similar to the equivalent OpenROAD Application Development environment.
There is a utility called w4glapp.exe that is bound against the orrun.dll. It provides similar functionality to w4gldev.exe'. The w4glapp.exe does not support the runimage and makeimage modules.
This means that w4glapp.exe does support the following modules;
- backupapp
- compileapp
- createapp
- destroyapp
- documentapp
- purgeapp
- queryimage
- rundbapp
- versionapp
The w4glapp.exe utility is used by the backupapps.bat script.
Start the Workbench Express Application Development Environment
Use the following shortcut to launch workbench.exe
Start-->Programs-->Ingres-->Workbench Express for Unicode-->Workbench Express Application Development
If no profile exists then the Startup Assistant will be launched automatically.
Select the Database Management System
Select an Existing Database
Select the Ingres Net Virtual Node
Select the Database
Supply an Connection Options
Supply the Connection Profile Name
The Workbench Express Application Development Environment is now launched
Select the Jigfall Application
Click the Develop tab and select the Jigfall application. Press the Go icon to start the application.
Jigfall is now launched from the Application Development Environment
Select the qt application
Click the Develop tab and select the qt application. Press the Go icon to start the application.
qt is now launched from the Application Development Environment
Press here to return to Workbench Express Home Page
