Chapter 4 Defining Components

Defining components

You can define components in Jaguar Manager, Sybase PowerJ, or PowerBuilder.

PowerBuilder components are installed into EAServer using the PowerBuilder user interface. After a PowerBuilder component is installed in EAServer, you can view the settings in Jaguar Manager. Sybase recommends that you edit all PowerBuilder component settings from PowerBuilder so that the EAServer component definition remains in sync with the PowerBuilder object definition and project settings. See your PowerBuilder documentation for more information.

If you have PowerJ installed, you can define, develop and deploy Java components from within PowerJ. See your PowerJ documentation for more information.

Defining components in Jaguar Manager

Decide how you will define the component interface. Your options are:

Option	Description
Importing a compiled Java file	Jaguar Manager reads method definitions from a compiled Java class or interface. "Importing interfaces from compiled Java files " describes this feature in detail.
Importing an ActiveX file	Jaguar Manager reads the interface definition from your ActiveX DLL or a separate ActiveX type library file. "Importing ActiveX components" describes this feature in detail.
Defining the interface manually	You can define methods manually using Jaguar Manager graphical controls or by creating the interface in an IDL file.

If you import from an ActiveX or Java file, skip to step 3. (The import process installs the component and sets the properties on the General tab in the Component Properties window.)

Install the component in an EAServer package. See "Installing components" for more information.
Configure the settings in the Component Properties window, as described in "Configuring component properties".

Component names are not case-sensitive Components in a package must have unique names that differ in ways other than letter case. For example, you cannot install two components named MyComp and mycomp in the same package.