9 173 PACKAGE_CREATE

LANSA Technical

9.173 PACKAGE_CREATE

Þ Note: Built-In Function Rules.. Deleteif applicable.

This Built-In Function creates a Package based on the supplied Deployment Tool Template. Objects can be added to the package.

Note: For WAMs and Weblets, the required Languages and Technology Services must be provided.

For use with

LANSA for i

NO

 

Visual LANSA for Windows

YES

Only available for RDMLX.

Visual LANSA for Linux

NO

 

 

Arguments

No

Type

Req/ Opt

Description

Min Len

Max Len

Min Dec

Max Dec

1

A

Req

Deployment Template

Must have associated .ptf template file in <System Directory>\X_Apps\X_Tmplt

1

10

 

 

2

A

Req

Application Name

1

8

 

 

3

A

Req

Version or Patch

Version must be in the format <major version number>.<minor version number>.<build number>

Patch must be in the format <major version number>.<minor version number>.<build number>.<patch number>

1

23

 

 

4

List

Req

Objects to include in Package

List can be empty but must be supplied.

From - To   Description

  1     50     Object Type

Supported object types are listed in Package Objects.

 51     70     Object Name

 71     80    Object Qualifier

 81     81    Include Data (Files & Web Components only)

For files:
  Y - Include data
  N - Do not include data
For web components:
  I - Input
  O - Output
  N - Not applicable

 82     82    Data processing option (files only)

For files:
  I - Reload data ignoring any duplicates
  D - Drop existing data
  R - Reload data replacing duplicates (only available if file data included).

 83    99    Reserved for future use.

81

99

 

 

5

List

Req

Web Designs

If including WAMs or weblets in the package indicate the languages and technology services required.

List can be empty but must be supplied.

From - To   Description

  1     50     Object Type

WEBLANGUAGE
TECHNOLOGYSERVICE

 51     60     Language / Provider

WEBLANGUAGE : Language Code (e.g. ENG)
TECHNOLOGYSERVICE: Technology Service Provider (e.g. LANSA)

 61     70     Technology Service

WEBLANGUAGE: blank

TECHNOLOGYSERVICE: Technology Service (e.g. XHTML)

70

70

 

 

6

A

Opt

Package Path

Indicate where the package should be created.

If blank package will be created at <System Directory>\X_Apps.

If you intend to edit the package using the Deployment Tool, the package must be created at <System Directory>\X_Apps

Default: blank

1

256

 

 

7

A

Opt

Replace Package

Y or N

Default: N

1

1

 

 

8

A

Opt

Build Package

Y or N

Default: Y

1

1

 

 

9

A

Opt

Package Description

If the package already exists, the description will only be replaced if a non-blank description is supplied.

Default: blank

1

200

 

 

10

A

Opt

Application Description

If application already exists, the description will only be replaced if non-blank description is supplied.

Default: blank

1

200

 

 

 

Return Values

No

Type

Req/ Opt

Description

Min Len

Max Len

Min Dec

Max Dec

1

 A

Req

Return Code

OK = Package created without error

ER = An Error occurred during the package creation or build.  Check log files associated with package.

2

2

 

 

2

A

Req

Reason

Explanation accompanying error

1

100

 

 

 

 

Package Objects

When formatting entries for Argument 4, the Objects to include in Package, use the following table to determine appropriate data for each object type.

 

Object Type

Object Name
Required

Object Qualifier
Required

Include Data
Required

ACTIVEX

Y

N

N

BITMAP

Y

N

N

BUSINESS OBJECT

Y

N

N

CURSOR

Y

N

N

DOTNETCOMPONENT

Y

N

N

EXTERNALRESOURCE

Y

N

N

FIELD

Y

N

N

FILE

Y

Y - Library name

Y

FORM

Y

N

N

FUNCTION

Y

Y - Process

N

ICON

Y

N

N

LANGUAGE

Y – Package Language Code

Special value used to include Package Languages

N

N

MESSAGE

Y - Message ID (1-7), Language Code (8-11)

Language is optional. If not supplied, all languages are included.

Y - Message File

 

MESSAGEFILE

Y – Message File

Y - Language Code

N

MULTILINGUALVARIABLE

Y

N

N

PROCESS

Y

N

N

REUSABLEPART

Y

N

N

SYSTEMVARIABLE

Y

N

N

TECHNOLOGYSERVICE

Y – Provider

Y – Technology Service

N

VISUALSTYLE

Y

N

N

WEBAPPLICATIONMODULE

Y

N

N

WEBCOMPONENT

Y

N

Y

WEBLET

Y

N

N

WEB SERVICE

Y

N

N

 

What you cannot include with this BIF

  • Editor List or Task related objects.
  • Application Template objects.