Target types
This section describes each of the PowerScript application
and component targets and Web targets you can build.
PowerScript application targets
There are three wizards for creating PowerScript application
targets:
Application Target wizard
You use the Application Target wizard to create a new PowerScript-based Application
object and the library containing it. You need to create any other objects
you need from scratch.
Template Application Target
wizard
You use the Template Application Target wizard to create a
PowerScript-based application, the library containing it, and a
set of basic objects and scripts. If the application requires a
connection to EAServer or a SQL database, the wizard automatically
creates a Connection object.
In the Template Application wizard, you can choose one of
three application types: MDI Application, SDI Application, and PFC-based
Application.
MDI Application The wizard automatically generates the shell and scripts for a
basic Multiple Document Interface (MDI) application that includes
these objects:
- Application
object - Frame window
- Frame menu
- Base sheet window
- Sheet menu
- Sheet menu service object
- Sheet windows
- About window
- Toolbar window
- Connection service object (if database connection
is needed) - Project object (optional; can build later using
a Project wizard)
You can run the MDI application immediately by clicking the
Run button on the PowerBar. You can open sheets, display an About
box, and select items from menus. The To-Do List can help you use
the application as a starting point for continuing development of
an MDI application.
SDI Application In the Template Application wizard, you can also choose to create
an SDI application. An SDI application has only one main window
with a menu and an about window. If the application requires a connection
to EAServer or a SQL database, the wizard automatically creates
a Connection object.
PFC-based Application In the Template Application wizard, you can also create a
PFC-based application that uses objects in the PowerBuilder Foundation
Class Library that you have customized for developing your own class
libraries. When you use PFC, you can provide services to your applications
and provide more corporate, departmental, and application consistency
to your users.
For information about building MDI and SDI
applications, see Application Techniques
. For
information about PFC applications, see the PowerBuilder Foundation
Class Library User’s Guide
.
Existing Application Target
wizard
You use the Existing Application Target wizard to add a target
to your workspace that uses an application you built in an earlier
version of PowerBuilder. After
you complete the wizard, the Migrate Application dialog box opens
so you can migrate the application to this version.
Before you migrate Always make a backup copy of all the PBLs used in an application
before you migrate it to a new version of PowerBuilder.
You can use the Migration Assistant to check for obsolete
syntax in your application before you migrate; then you can make
changes in the earlier version of PowerBuilder and avoid some migration
errors. The Migration Assistant is particularly useful if you are
migrating from PowerBuilder 6 or earlier. Open the Migration Assistant
from the Tool tab of the New dialog box, and press F1 if you need
Help in the wizard.
You should also check the release notes for the version of
PowerBuilder that you are using to find out if there are any migration
issues that might affect you.
For information about building PowerScript
applications, see the rest of this book and Application
Techniques
.
PowerScript component targets
EAServer Component Target wizard
You use the EAServer Component Target wizard to create a new
target containing a custom class user object (to which you later
add methods and properties) with the characteristics needed to be
an EAServer component object that you can deploy to EAServer. If you want to
create an EAServer component in an existing target, use the wizard
on the PB Object page.
Access to the EAServer component from a PowerBuilder client
application is gained through a Proxy object. You create a Proxy
object using the EAServer Proxy wizard on the Project tab page.
COM/MTS/COM+ Component
Target wizard
The COM/MTS/COM+ Component Target
wizard creates a new target containing a custom class user object
(to which you later add methods and properties) with the characteristics
needed to be a component object that you can deploy to a Microsoft
MTS or COM+ server. If
you want to create a COM/MTS or COM+ component
in an existing target, use the wizard on the PB Object page.
Automation Server Target wizard
The Automation Server Target wizard creates a new custom class
user object (to which you later add methods and properties) with
the characteristics needed to be an automation server. You can access
methods in the user object from clients built with OLE-enabled applications
such as PowerBuilder, Visual Basic, and Visual C++.
For information about building components, see Application
Techniques
.
Web and JSP targets
JSP Target wizard
The JSP Target wizard creates a target in which you can
build a Web application and helps you set deployment and configuration
options for deploying the target to an application server.
Dynamo Web Site Target wizard
The Dynamo Web Site Target wizard creates a target to organize your
files and a PowerDynamo Web site that uses Adaptive Server Anywhere
(ASA) and ODBC. It also helps you set deployment and configuration
options.
Web Site Target wizard
The Web Site Target wizard creates a target for organizing
the files for a Web site that can be deployed to ASP, to the file
system, or to PowerDynamo for any of its site type configurations,
not only ODBC.
Migrate PowerSite 7.1 Project wizard
The Migrate PowerSite 7.1 Project wizard brings a PowerSite
project into PowerBuilder as a Web target. You must maintain an
accessible copy of your Component Manager database in order to migrate
your PowerSite projects.
Source Controlled Web Target wizard
The Source Controlled Web Target wizard opens a Web target
that has been checked into a source control system.
For more information about creating Web applications,
see Working with Web and JSP Targets
.