Versions Compared

Old Version 8

changes.mady.by.user Jack Reynebeau

Saved on

compared with

New Version Current

changes.mady.by.user Tristan Butzine (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Provides the ability to start a composite(s) on the SOA server.

...

  This operation will handle all revisions for a given composite to ensure that the default revision doesn't change as revisions are started.  The default revision is always started and other revisions can be controlled by an "Start All Revisions" input.

Target Properties

Property Name

Property Code

Required

Description

SOA Server Host

FDSOA_SERVER_HOST

Yes

Host name of the SOA managed server.

SOA Server Port

FDSOA_SERVER_PORT

Yes

Port number of the SOA managed server, which will be the SSL Listen Port or Listen Port based on whether you desire to connect using SSL.

SOA Use SSL

FDSOA_USE_SSL

No

Whether or not to use SSL when connecting to the SOA Server. Is unchecked by default. If checked, SOA Server Port must be set to the SSL Listen Port and Weblogic Domain Directory must be set.

Weblogic Admin User

FDWLS_ADMIN_USER

Yes

Admin

user name

username for WebLogic server.

Weblogic Admin Password

FDWLS_ADMIN_PASSWORD

Yes

Weblogic Admin User

password for WebLogic server

 password for WebLogic server.

Weblogic Domain Directory

FDWLS_DOMAIN_DIRECTORY

Yes*

Weblogic Domain Directory for the WebLogic server. *Only required if SOA Use SSL option is checked.

Oracle SOA Home

FD_ORACLE_SOA_HOME

Yes

Oracle SOA Home

,

indicates where SOA Suite is installed.

Project Properties

Property Name

Property Code

Required

Description

SOA Composite Name

FDSOA_COMPOSITE_NAME

Yes

Name of composite that is being deployed.

SOA Partition

FDSOA_PARTITION

Yes

Name of the partition to hold the composite on the server.

Inputs

Input Name

Input Code

Required

Description

Deploy Config Plan

Composites File

FDSOA_INP_

DEPLOY

COMPOSITES_

CFG_PLAN

FILE

No

Deployment config plan that is to be used for the composite. Takes a Wildcard expression or filename. Can be a relative or absolute path (see special considerations

File name (anywhere in temp directory) or absolute path to file with comma separated composite names.  See Special Considerations section below for additional details.

Composite Name List

FDSOA_INP_COMPOSITE_NAME_LIST

No

Comma separated composite names, overrides Composite File Name input.  Optionally, can prefix a partition on the composite name if there are more than one composite with the same name, (<partition:>composite1, composite2).  See Special Considerations section below for additional details.

Start All Revisions

FDSOA_INP_START_ALL_REVISIONS

No

Check to start all composite revisions.  If false, then only default revision will be started (default value is false).

Composite Revision

FDSOA_INP_REVISION

No

Provide

the composite revision (see special considerations).

Outputs

Output Name

Required

Description

specific revision to start.  If set, then Start All Revisions input will be ignored.  See Special Considerations section below for additional details.

Make Default Revision

FDSOA_MAKE_DEFAULT_REVISION

No

If Composite Revision input is provided, that specific revision will be set as default.

Continue on Not Found

FDSOA_INP_CONTINUE_ON_NOT_FOUND

No

If checked, error will not be thrown if composite is not found. Defaults to false.

Artifacts

This operation doesn't consume or produce any artifacts.

...

This operation will select all available endpoints associated to the environment/instanceTarget.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

Special Considerations

The latest revision will be started if Composite Revision is not filled incomposite names that are used will be determined by first looking at the Composite Names input, then the Composite File Name input and lastly the SOA Composite project property (the first two inputs can provide multiple composite names).  The Revision input should generally not be utilized with the Composite Names or Composite File Name inputs.  The single revision input will be checked against each composite from the composite list and the specific revision may not be available on all composites, which will cause the operation to fail. :

  • starting a single revision (this is the backwards compatibility capability)

    • utilizes "Composite Revision" and "Make Default Revision" inputs to control what revision to start and whether it should be the default revision

  • starting multiple composites/revisions

    • utilizes "Composites File" or "Composite Name List" and "Start All Revisions" inputs

      • if utilizing "Composite File", there can be several variations of file name.

        1. just a file name, will look in the temp directory for the given file name

        2. relative path, will only look for the relative path within the temp directory for the given file name

        3. absolute path, will only look at the absolute path for the given file

    • either input (Composite File or Composite Name List) provides a list of composite names to start that must use the following format: <partition:>composite1,composite2 (partition is optional)

    • the default revision is started first and then all non-default revisions will be started, if the "Start All Revisions" input is checked.  This will maintain the default revision and not allow SOA Suite to move the default revision to another revision.  If a composite is in two partitions, then specify the partition in the above format to direct the operation to the correct composite.