Resource Bundle com.soa.activity.ui / ActivityApplicationResources Information

AuditActivity.type.helpText

The Audit Activity provides a mechanism for auditing a message. The audited message content that is recorded and displayed as audited message content from an Auditing Policy. This information displays on the Monitoring pages of a service (i.e., Services > Monitoring). The input to the activity can be a message variable.In the Capture Details section, if "Capture complete message" is selected, then the entire message will be recorded. A name can be given to the audited content so it can be distinguished in the monitoring page. If "Capture message at the following expressions" is selected, then only portions of the message will be recorded. The results of multiple XPath expressions will be recorded. Each expression has its own label.In the Masked Elements section, content that should be masked, such as password or account number, can be identified by one or more XPath expressions.In the Namespace Prefixes section, all namespace prefixes used in XPath expression used in the activity can be defined. If a namespace is used in an XPath expression without a definition in this table, then there will be an error performing the activity.

AuditActivity.type.helpTitle

Auditing Details Editor

InsertContentActivity.type.helpText

The Insert Content Activity can be used to fill the content of a String or Message variable. The source of the content can be either statically defined content or an existing variable.The From section of the activity editor identifies the source of the content. To specify static content to be inserted select the "Static Content" radio button. Once selected a text area will be displayed where content of any type, XML, JSON, text, etc. can be entered. A text field will also be displayed where you must enter the mime content type of the static content you entered in the text area (i.e., application/xml or application/json).The To section of the activity identifies the target of the content specified in the From section. The target of the inserted content must be a variable. The From content can either initialize/replace the content of the variable in the To section or it can be inserted into the existing content of the target variable. If replacing the entire content of a variable and the variable has not yet been initialized it will be initialized as a result of the activity.A filter is defined using a filter expression written in a selected language. The languages supported are XPath (for XML content), JSONPath (for JSON content), or Regular Expression (for any content). The result of the filter expression applied to the input variable will be inserted. It is possible that the filter expression results in multiple elements or properties being used as input.When defining XPath filter expressions the namespaces of specified elements must be included. That is done by using a namespace prefix in the expression. All namespace prefixes must be mapped to a namespace in the Namespace Prefixes table at the bottom of the activity page.

InsertContentActivity.type.helpTitle

Insert Content Details Editor

ProcessActivity.type.helpText

The Process Activity allows you to call one process from another so that you can create processes with common activities and then call those processes at an appropriate point of another process. These processes with common activities are reusable and are organized in the "Processes" folder of each Organization in the Policy Manager Workbench. Reusable processes can themselves have Process Activities so that they can call other reusable processes.The "Process Selection Editor" is used to configure the Process Activity. The editor presents a tree of reusable processes that are available in the "Processes" folder of each Organization in the Policy Manager Workbench. Click the radio button of the process you would like to add to the current Process Activity and click "Finish."When a process is called from another process, the calling process's context is passed to the called process. All the variables and their values from the calling process are passed through. If the called process defines variables with the same names as ones in the calling process, the calling process's variables will be used.

ProcessActivity.type.helpTitle

Process Selection Editor

ScriptedActivity.type.helpText

The Script Activity provides the ability to execute a script at the point in the process the activity is connected. The script can be written in any of the languages available in the drop-down list.The Script Details Editor is organized into two separate areas, Imports and Source. The Source has a pull-down where you can select the script language. It also has a large source code editor text area.Common functions that you may need to perform in your scripts can be saved in Script objects using the Add Script function in the Scripts section of each Organization in the Policy Manager Workbench. To make use of those common functions from the Script Activity the Script objects defining those functions must be imported. The Imports area is where those scripts are identified for import. The available scripts are listed in the Available Scripts tree. Any number of Scripts in that tree can be moved to the Imported Scripts list box. After the script is imported it can then be referenced in the script source. Note that only scripts that match the language type will be available for selection in the tree. The script does not return a value.You can author "Process" related scripts using the "Policy Manager Scripting API". Here you will find interfaces for adding alert reporting, logging capababilities, and scripted messages, invoking operations, triggering process execution, and classes for holding transport header information (name/values) and holding transport headers for a message. When you are ready to save your script, click "Finish."

ScriptedActivity.type.helpTitle

Script Details Editor

TransformActivity.type.helpText

The Transformation activity provides a mechanism for transforming messages or string content using XSLT or Freemarker. Using XSLT, you are prompted for an Input Variable and all other process variables are available to the XSLT as XSL parameters, i.e., <xsl:param name="var1"/>.Using Freemarker you can address any element in the process context and variables, including headers, parameters, content, and more.A simple template for processing a JSON document might look like:<#assign m = message.contentAsString?eval> <name>$&#123m.pet.name&#125</name> Once transformed, the altered content is saved to the Output Variable with the specified content type.

TransformActivity.type.helpTitle

Transformation Details Editor

com.soa.activity.ui.activity.description.label

Description

com.soa.activity.ui.activity.label

Activity Details

com.soa.activity.ui.activity.name.label

Name

com.soa.activity.ui.activity.type.label

Type

com.soa.activity.ui.add.label

Add

com.soa.activity.ui.audit.activity.button.add

Add

com.soa.activity.ui.audit.activity.button.delete

Delete

com.soa.activity.ui.audit.activity.capture.complete.message.label

Capture complete message

com.soa.activity.ui.audit.activity.capture.details.label

Capture Details

com.soa.activity.ui.audit.activity.capture.xpaths.label

Capture message at the following expressions

com.soa.activity.ui.audit.activity.description

The Audit Activity is used for ...

com.soa.activity.ui.audit.activity.details.label

Auditing Details

com.soa.activity.ui.audit.activity.grid.value.missing

Please enter the values for at least one row

com.soa.activity.ui.audit.activity.icon

/com.soa.activity.ui/resources/images/audit-24px.gif

com.soa.activity.ui.audit.activity.language.column

Language

com.soa.activity.ui.audit.activity.mask.label

Mask:

com.soa.activity.ui.audit.activity.masked.elements.label

Masked Elements

com.soa.activity.ui.audit.activity.menuHoverHelp

Drag and drop to add Audit Activity

com.soa.activity.ui.audit.activity.name

Audit

com.soa.activity.ui.audit.activity.namespace.column

Namespace

com.soa.activity.ui.audit.activity.namespace.prefixes.label

Namespace Prefixes

com.soa.activity.ui.audit.activity.prefix.column

Prefix

com.soa.activity.ui.audit.activity.record.name.column

Record Name

com.soa.activity.ui.audit.activity.record.name.label

Record Name:

com.soa.activity.ui.audit.activity.record.name.value.missing

Record Name is required

com.soa.activity.ui.audit.activity.transformation.label

Transformation:

com.soa.activity.ui.audit.activity.value.missing

Value for one of the rows is missing

com.soa.activity.ui.audit.activity.xpath.column

XPath

com.soa.activity.ui.condition.language.label

Language

com.soa.activity.ui.condition.name.label

Name

com.soa.activity.ui.condition.otherwise.label

Otherwise

com.soa.activity.ui.connector.icon

/com.soa.activity.ui/resources/images/connector.gif

com.soa.activity.ui.delete.icon

/com.soa.activity.ui/resources/images/delete-24px.gif

com.soa.activity.ui.delete.label

Delete

com.soa.activity.ui.delete.menuHoverHelp

Delete selected Objects

com.soa.activity.ui.download.icon

/com.soa.activity.ui/resources/images/download-24px.gif

com.soa.activity.ui.download.menuHoverHelp

Download stored Process in XML format

com.soa.activity.ui.emptyFaults

No faults available

com.soa.activity.ui.emptyVariables

No variables available

com.soa.activity.ui.error.contenttype.required

Content Type required.

com.soa.activity.ui.error.inputvariable.required

Input variable required.

com.soa.activity.ui.error.language.required

Language required.

com.soa.activity.ui.error.outputvariable.required

Output variable required.

com.soa.activity.ui.faultNames.label

Fault Names

com.soa.activity.ui.help.icon

/com.soa.activity.ui/resources/images/help-24px.gif

com.soa.activity.ui.help.menuHoverHelp

Help

com.soa.activity.ui.insertContent.activity.description

Insert Content description here

com.soa.activity.ui.insertContent.activity.icon

/com.soa.activity.ui/resources/images/insertcontent-24px.gif

com.soa.activity.ui.insertContent.activity.menuHoverHelp

Drag and drop to add Insert Content Activity

com.soa.activity.ui.insertContent.activity.name

Insert Content

com.soa.activity.ui.insertContent.detail.label

Insert Content Details

com.soa.activity.ui.insertContent.expression.label

Expression

com.soa.activity.ui.insertContent.filter.label

Filter

com.soa.activity.ui.insertContent.from.label

From

com.soa.activity.ui.insertContent.nsPrefixes.label

Namespace Prefixes

com.soa.activity.ui.insertContent.static.radio.label

Static Content

com.soa.activity.ui.insertContent.to.label

To

com.soa.activity.ui.insertContent.variable.radio.label

Variable

com.soa.activity.ui.insertContent.variableName.label

Variable Name

com.soa.activity.ui.insertcontent.append.radio.label

Append

com.soa.activity.ui.insertcontent.contentType.label

Content Type

com.soa.activity.ui.insertcontent.replace.radio.label

Replace

com.soa.activity.ui.invoke.accesspoint.directly.label

Invoke Access Point Directly

com.soa.activity.ui.invoke.accesspoint.radio.label

Access Point

com.soa.activity.ui.invoke.activity.description

The Invoke is used for ...

com.soa.activity.ui.invoke.activity.icon

/com.soa.activity.ui/resources/images/invoke-24px.gif

com.soa.activity.ui.invoke.activity.menuHoverHelp

Drag and drop to add Invoke Activity

com.soa.activity.ui.invoke.activity.name

Invoke

com.soa.activity.ui.invoke.audit.label

Audit

com.soa.activity.ui.invoke.consumer.radio.label

Consumer

com.soa.activity.ui.invoke.domain.radio.label

Domain:

com.soa.activity.ui.invoke.endUser.radio.label

End-User

com.soa.activity.ui.invoke.identity.label

Identity

com.soa.activity.ui.invoke.inputVariable.label

Input Variable

com.soa.activity.ui.invoke.invocation.details.label

Invocation Details

com.soa.activity.ui.invoke.outboundIdentity.label

Outbound Identity

com.soa.activity.ui.invoke.outputVariable.label

Output Variable

com.soa.activity.ui.invoke.password.radio.label

Confirm Password:

com.soa.activity.ui.invoke.result.label

Result

com.soa.activity.ui.invoke.search.services.label

Search Services

com.soa.activity.ui.invoke.search.text

Enter any part of the "Service QName" including "Namespace" and/or "Localpart" and click "Search." Service QNames that match your search criteria will display in the "Results" section.

com.soa.activity.ui.invoke.select.endpoint.option

----- select access point -----

com.soa.activity.ui.invoke.select.endpoint.title

Check "Invoke Access Point Directly" and select an interface to enable and populate Access Point drop down

com.soa.activity.ui.invoke.select.interface.label

Interface

com.soa.activity.ui.invoke.select.interface.option

----- select interface -----

com.soa.activity.ui.invoke.select.interface.title

Select a service to enable and populate Interface drop down

com.soa.activity.ui.invoke.select.operation.label

Operation

com.soa.activity.ui.invoke.select.operation.option

----- select operation -----

com.soa.activity.ui.invoke.select.operation.title

Select an interface to enable and populate Operation drop down

com.soa.activity.ui.invoke.select.service.label

Service

com.soa.activity.ui.invoke.select.service.option

----- select service -----

com.soa.activity.ui.invoke.select.service.title

Select Search button to enable and populate Service drop down

com.soa.activity.ui.invoke.service.qname.label

Service QName:

com.soa.activity.ui.invoke.service.radio.label

Service

com.soa.activity.ui.invoke.sourceIdentity.label

Source Identity

com.soa.activity.ui.invoke.specifyInbound.label

Use Incoming Identities as Outbound Identities

com.soa.activity.ui.invoke.specifyInbound.text

This option indicates the identities and their categories will be used in outgoing messages.

com.soa.activity.ui.invoke.specifyOutbound.label

Specify Outbound Identities

com.soa.activity.ui.invoke.specifyOutbound.text

This option indicates the supported identities for outbound calls and what the content of those identities should be, such as the virtual service's identity or an identity received in a consumer's message. Click "Add" to launch the "Add Outbound Identity" screen and configure outbound identities. After adding identities you can then manage them on this screen using the "Modify" and "Delete" actions available through the Actions drop-down list box.

com.soa.activity.ui.invoke.staticUser.radio.label

Static User

com.soa.activity.ui.invoke.url.radio.label

URL

com.soa.activity.ui.invoke.useServiceIdentity.checkbox.label

Use Service Identity for Outbound HTTPS

com.soa.activity.ui.invoke.useServiceIdentity.comment.label

This option configures the "identity" to be used when communicating over HTTPS.

com.soa.activity.ui.invoke.useVariable.label

Use Variable

com.soa.activity.ui.invoke.userDefined.radio.label

User Defined Category

com.soa.activity.ui.invoke.username.radio.label

Username:

com.soa.activity.ui.invoke.variableDetails.label

Variable Details

com.soa.activity.ui.join.activity.description

Join desc

com.soa.activity.ui.join.activity.icon

/com.soa.activity.ui/resources/images/join-24px.gif

com.soa.activity.ui.join.activity.menuHoverHelp

Drag and drop to add Join Activity

com.soa.activity.ui.join.activity.name

Join

com.soa.activity.ui.menu.deleteActivity

Delete Activity

com.soa.activity.ui.menu.deleteCondition

Delete Condition

com.soa.activity.ui.menu.deleteConnection

Delete Connection

com.soa.activity.ui.menu.editActivityDetail

Edit Activity Detail

com.soa.activity.ui.menu.editActivityName

Edit Activity Name

com.soa.activity.ui.menu.editCondition

Edit Condition

com.soa.activity.ui.message.activityCannotBeDeleted

Activity connected to a condition cannot be deleted, without also selecting the condition for delete.

com.soa.activity.ui.message.browserNotSupported

Browser is not supported!

com.soa.activity.ui.message.casePostionNotNumeric

Case position is not numeric.

com.soa.activity.ui.message.changeConnection

Activity [{0}], connecting to activity name [{1}] and activity type [{2}] must all have a value.

com.soa.activity.ui.message.confirmCaseDelete

Deleting case connection will delete the switch condition. Do you want to continue?

com.soa.activity.ui.message.confirmParentCaseDelete

Deleting this activity will also delete the case condition that it is connected to. Do you want to continue?

com.soa.activity.ui.message.confirmSwitchDelete

Deleting branch activity will delete all of its associated cases. Do you want to continue?

com.soa.activity.ui.message.connectingToItself

Cannot connect activity to itself.

com.soa.activity.ui.message.deleteConfirm

Are you sure you want to delete the selected process object(s)?

com.soa.activity.ui.message.duplicateConnection

Cannot connect to an activity that already has a connection.

com.soa.activity.ui.message.enterScript

Please enter a script.

com.soa.activity.ui.message.helpMissing

Help is not available.

com.soa.activity.ui.message.invalidInput

Activity [{0}] cannot have any input.

com.soa.activity.ui.message.invalidOutput

Activity [{0}] cannot have any output.

com.soa.activity.ui.message.invalidStartingPoint

Starting point activity [{0}] is not connected to all activities.

com.soa.activity.ui.message.joinMissingSplit

All join activities must be part of a split activity.

com.soa.activity.ui.message.leaveConfirm

Leaving the page will cause changes to be lost. Are you sure you want to exit this page?

com.soa.activity.ui.message.missingActivities

No process activities are defined for this operation.

com.soa.activity.ui.message.missingConditionActivity

Branch [{0}] has a condition that does not connect to an activity.

com.soa.activity.ui.message.missingConnectionActivity

Activity [{0}] has a connection that is not joined to an activity.

com.soa.activity.ui.message.missingFaultActivities

No fault activities are defined. Drag and drop any activity icon from the menu, to start the fault sequence.

com.soa.activity.ui.message.missingGraph

Saved positions were not found for this graph. Layout is automatically generated.

com.soa.activity.ui.message.missingInput

Activity [{0}] must have at least 1 input.

com.soa.activity.ui.message.missingOutput

Activity [{0}] must have at least 1 output.

com.soa.activity.ui.message.missingReply

Process must have at least 1 reply activity.

com.soa.activity.ui.message.missingScriptSelectFromList

Please select at least one script from the List

com.soa.activity.ui.message.missingScriptSelectFromTree

Please select at least one script from the tree

com.soa.activity.ui.message.missingScriptType

Unable to find customized script editor for selected language.

com.soa.activity.ui.message.missingStartingPoint

Process must have at least 1 starting point. There must be at least 1 activity with no input.

com.soa.activity.ui.message.movingCondition

A condition cannot be moved from it's Branch.

com.soa.activity.ui.message.multipleConnections

Activity [{0}] cannot be connected to more than 1 activity.

com.soa.activity.ui.message.multipleInputs

Activity [{0}] cannot have more than 1 input.

com.soa.activity.ui.message.multipleOutputs

Activity [{0}] cannot have more than 1 output.

com.soa.activity.ui.message.multipleReceives

Process cannot have more than 1 receive activity.

com.soa.activity.ui.message.multipleStartingPoints

Process cannot have more than 1 starting point.

com.soa.activity.ui.message.nameAlreadyExists

New name [{0}] already exists.

com.soa.activity.ui.message.noDownload

Process does not exist yet. There is nothing to download.

com.soa.activity.ui.message.noRendererFound

No activity renderers found. Activities cannot be created.

com.soa.activity.ui.message.nothingToSelectFromList

Nothing to select from the list

com.soa.activity.ui.message.nothingToSelectFromTree

Nothing to select from the tree

com.soa.activity.ui.message.operationKeyNull

Operation key is null. Process cannot be retrieved.

com.soa.activity.ui.message.receiveCannotBeDeleted

The Receive Activity is part of the default process and cannot be deleted.

com.soa.activity.ui.message.recursiveConnection

Cannot recursively connect activities to each other.

com.soa.activity.ui.message.reload

Do you want to reload the current process? You will lose all unsaved changes. This cannot be undone.

com.soa.activity.ui.message.saveError

Process not saved. Reconcile the structure of the following activities and try again:

com.soa.activity.ui.message.selectLanguage

Please select language.

com.soa.activity.ui.message.splitConnectingToJoin

Split cannot connect to join activity.

com.soa.activity.ui.message.splitJoinsNotEqual

Split output sequences do not match Join input sequences. Make sure all activities are joined correctly and that Split does not contain a Branch Activity.

com.soa.activity.ui.message.splitMissingJoin

All split activities must have a join activity.

com.soa.activity.ui.message.splitMissingSequence

Split activity [{0}] must have at least 2 sequences.

com.soa.activity.ui.message.splitSequenceMissingActivity

Split activity [{0}] sequences must all contain activities.

com.soa.activity.ui.message.successfulSave

Changes successfully saved. Page will now reload.

com.soa.activity.ui.message.validationError

Process not saved. Correct the following errors and try again:

com.soa.activity.ui.moveDown.label

Move Down

com.soa.activity.ui.moveUp.label

Move Up

com.soa.activity.ui.none.value

-- None --

com.soa.activity.ui.printer.icon

/com.soa.activity.ui/resources/images/printer.png

com.soa.activity.ui.process.description

The Process Activity is used for ...

com.soa.activity.ui.process.fieldset.label

Selected Process Details

com.soa.activity.ui.process.helpId

633

com.soa.activity.ui.process.icon

/com.soa.activity.ui/resources/images/process-24px.gif

com.soa.activity.ui.process.key.label

Process Key

com.soa.activity.ui.process.menuHoverHelp

Drag and drop to add Process Activity

com.soa.activity.ui.process.name

Process

com.soa.activity.ui.process.name.label

Process Name

com.soa.activity.ui.process.noneSelected

none selected

com.soa.activity.ui.process.treeName.label

Process Activity Tree

com.soa.activity.ui.receive.description

The Receive is used for ...

com.soa.activity.ui.receive.details.label

Receive Details

com.soa.activity.ui.receive.icon

/com.soa.activity.ui/resources/images/receive-24px.gif

com.soa.activity.ui.receive.menuHoverHelp

Drag and drop to add Receive Activity

com.soa.activity.ui.receive.name

Receive

com.soa.activity.ui.receive.variable.label

Variable

com.soa.activity.ui.refresh.icon

/com.soa.activity.ui/resources/images/refresh-24px.gif

com.soa.activity.ui.refresh.menuHoverHelp

Reload Process from Database

com.soa.activity.ui.reply.description

The Reply is used for ...

com.soa.activity.ui.reply.details.label

Reply Details

com.soa.activity.ui.reply.fault.label

Fault

com.soa.activity.ui.reply.icon

/com.soa.activity.ui/resources/images/reply-24px.gif

com.soa.activity.ui.reply.menuHoverHelp

Drag and drop to add Reply Activity

com.soa.activity.ui.reply.name

Reply

com.soa.activity.ui.reply.variable.label

Variable

com.soa.activity.ui.save.icon

/com.soa.activity.ui/resources/images/save-24px.gif

com.soa.activity.ui.save.menuHoverHelp

Save Process to Database

com.soa.activity.ui.script.description

The Script Activity is used for ...

com.soa.activity.ui.script.fieldset.label

Script Details

com.soa.activity.ui.script.fieldset.successMessage

Script is error free

com.soa.activity.ui.script.icon

/com.soa.activity.ui/resources/images/script-24px.gif

com.soa.activity.ui.script.language.label

Language

com.soa.activity.ui.script.language.select

-- Select --

com.soa.activity.ui.script.menuHoverHelp

Drag and drop to add Script Activity

com.soa.activity.ui.script.name

Script

com.soa.activity.ui.script.permission.denied

This user lacks permissions to view imported scripts. Saving this activity will wipe out the imported script references

com.soa.activity.ui.script.script.label

Script

com.soa.activity.ui.select.value

-- Select --

com.soa.activity.ui.split.activity.description

Split desc

com.soa.activity.ui.split.activity.icon

/com.soa.activity.ui/resources/images/split-24px.gif

com.soa.activity.ui.split.activity.menuHoverHelp

Drag and drop to add Split Activity

com.soa.activity.ui.split.activity.name

Split

com.soa.activity.ui.switch.condition.label

Branch Condition

com.soa.activity.ui.switch.conditionDetails.label

Branch Details

com.soa.activity.ui.switch.conditionField.label

Condition

com.soa.activity.ui.switch.conditions.changeLanguage

Changing the language will delete the source of current conditions. Do you still want to continue??

com.soa.activity.ui.switch.conditions.label

Branch Details

com.soa.activity.ui.switch.description

The Branch is used for ...

com.soa.activity.ui.switch.expressions.label

Expressions

com.soa.activity.ui.switch.icon

/com.soa.activity.ui/resources/images/branch-24px.gif

com.soa.activity.ui.switch.labels.label

Case Conditions

com.soa.activity.ui.switch.language.simple.display

Simple

com.soa.activity.ui.switch.language.simple.value

urn:soa:language:simple

com.soa.activity.ui.switch.language.xpath.display

XPath

com.soa.activity.ui.switch.language.xpath.value

http://www.w3.org/TR/1999/REC-xpath-19991116

com.soa.activity.ui.switch.menuHoverHelp

Drag and drop to add Branch Activity

com.soa.activity.ui.switch.name

Branch

com.soa.activity.ui.switch.namespaces.label

Namespaces

com.soa.activity.ui.switch.prefixes.label

Prefixes

com.soa.activity.ui.switch.scriptExpression.label

Script Expression

com.soa.activity.ui.switch.simpleExpression.label

Simple Expression

com.soa.activity.ui.switch.xpathExpression.label

XPath Expression

com.soa.activity.ui.throw.description

The Throw is used for ...

com.soa.activity.ui.throw.details.label

Throw Details

com.soa.activity.ui.throw.faultname.label

Fault Name

com.soa.activity.ui.throw.icon

/com.soa.activity.ui/resources/images/throw-24px.gif

com.soa.activity.ui.throw.menuHoverHelp

Drag and drop to add Throw Activity

com.soa.activity.ui.throw.name

Throw

com.soa.activity.ui.throw.variable.label

Variable

com.soa.activity.ui.transform.activity.description

The Data Transformation Component performs an XSLT transformation on the message being processed. This provides many valuable services including facilitating compatibility between Web services and Web service clients of different versions.

com.soa.activity.ui.transform.activity.icon

/com.soa.activity.ui/resources/images/transform-24px.gif

com.soa.activity.ui.transform.activity.menuHoverHelp

Drag and drop to add Transformation Activity

com.soa.activity.ui.transform.activity.name

Transformation

com.soa.activity.ui.transform.contentType

Content Type

com.soa.activity.ui.transform.detail.label

Transformation Details

com.soa.activity.ui.transform.invar

In Variable

com.soa.activity.ui.transform.language

Language

com.soa.activity.ui.transform.outvar

Out Variable

com.soa.activity.ui.transform.template.label

Template

com.soa.activity.ui.variable.default.label

Default Value

com.soa.activity.ui.variable.description

com.soa.activity.ui.variable.icon

/com.soa.activity.ui/resources/images/variable-24px.gif

com.soa.activity.ui.variable.label

Variables and Faults

com.soa.activity.ui.variable.menuHoverHelp

Add or View Activity Variables

com.soa.activity.ui.variable.name

Variable

com.soa.activity.ui.variable.name.label

Name

com.soa.activity.ui.variable.type.label

Type

com.soa.activity.ui.variableDetail.label

Variable Details

com.soa.activity.ui.view11.icon

/com.soa.activity.ui/resources/images/view_1_1.png

com.soa.activity.ui.zoomIn.icon

/com.soa.activity.ui/resources/images/zoom_in.png

com.soa.activity.ui.zoomOut.icon

/com.soa.activity.ui/resources/images/zoom_out.png

condition.type.helpText

The language for each case condition is set in the Branch Details Editor and can only be changed there. Each condition must have a unique name.If "Otherwise" checkbox is selected, then the case becomes the default and no condition is entered. The condition name automatically becomes "Otherwise" and cannot be changed. The "Otherwise" checkbox will be disabled if there is already an "Otherwise" condition.The "Otherwise" checkbox can also be unselected, to change from the default condition to a regular condition.The result of the condition created here must be either true or false.

condition.type.helpTitle

Condition Details Editor

detail.type.helpText

The activity details editor provides the ability to change the activity name. Each activity name within a process must be unique.

detail.type.helpTitle

Activity Details Editor

external.type.fault.handling.helpText

An Invocation Activity may result in a fault being thrown. A fault will be remediated, or "handled", by executing a fault flow, either a flow designated for a particular fault identified by name or a default catch all flow.The current sequence of activities will be stopped when a fault is thrown and the fault flow will be executed immmediately. A fault flow is executed within a scope of control, either within the process scope or the Invocation Activity scope. If the fault flow is executed within the process scope, at the conclusion of the fault flow the process will terminate. If the falut flow is executed within the activity scope, at the conclusion of the fault flow the process will resume executing the sequence of activities after the Invocation Activity. The fault flow executing within the activity scope can itself throw a fault, in which case another fault flow within the process scope will be executed and then terminate the process.To designate the remediation of a fault to be executed within the activity's scope instead of the process's scope select the Handled checkbox next to it in the Handled Fault table.Some faults that are generated as the result of an invocation activity are unnamed. They are faults that do not appear in the invoked service's WSDL document. Without a name these faults will be handled within the process scope using the default Unnamed fault flow. By selecting the Map Unnamed Faults check box and entering a new fault name in the Fault Name text field the fault will be thrown with the given name and can therefore be handled by a named fault flow.

external.type.fault.handling.helpTitle

Manage Faults

external.type.helpText

The Invoke Activity invokes the operation of a service registered in the system. The operation is invoked by sending it a message that is specified using a single input variable or multiple input parameters. The response from the operation invocation is stored in an output variable. These variables can be configured on the Manage Input/Output Parameters screen.The operation that will get invoked can be specified either statically or dynamically through the use of variables. To statically identify the operation to invoke, first start by searching for the service with the operation.The search is performed using QNames. When the Search button is clicked the system searches for any service with a QName that contains what is typed in the Service QName field. If nothing is entered all services will be returned.Variables can be used for specifying the service, interface, and/or operation. The variable must be a string typed variable.By default the access point (endpoint) that is called when invoking the operation is selected by the runtime container using its selection strategy.Auditing the message as it is sent over the wire to the access point can be achieved by simply selecting the Audit checkbox. The virtual service operation invocation that is executing the process must be currently being audited by use of an auditing policy for the downstream message to be audited.

external.type.helpText2

The "Manage Outbound Identities" screen is used to configure whether you want to use incoming identities as outbound identities (the default), or specify custom identities to be used for all outbound messages to the down-stream service.When securing outbound calls from a virtual service, identities will typically be required to be specified in request messages. Those identities can be categorized as different actors in a message exchange.The "Use Incoming Identities as Outbound Identities" option is selected by default. This means identities used when invoking the operation are dictated by the outbound identity configuration of the virtual service.The "Specify Outbound Identities" section allows you to define identities for outgoing messages. Added identities are stored in an Identity Table where they can be modified or deleted. Perform the configuration tasks as needed (i.e., Add, Modify, or Delete). Select the "User Service Identity for Outbound HTTP" option if applicable.After completing your entries, click "Finish."

external.type.helpText3

The "Add Outbound Identity" screen allows you to configure an outbound identity to be used for outbound calls. The identity may be relayed from one of the identities provided in the incoming messages. The "Source Identity" option allows you to specify the outbound identity that should be taken from an identity received in the inbound message. Predefined categories include Consumer, End-User, and Service. The "User-Defined Category" option allows you to specify a custom category name. The "Static User" option allows you to specify a Policy Manager or external user name and password. The "Outbound Identity" option allows you to specify the subject category of the inbound identity that will be used for the outbound identity. Predefined categories include Consumer and End-User. The "User-Defined" option allows you to specify a custom category name. Click the radio button for each identity and configure as required. After completing your entries, click "Finish." The "Manage Outbound Identities" screen displays and the "Specify Outbound Identities" table is populated with the new category entries.

external.type.helpText4

An invocation activity must define where inputs to the invocation will come from and where the output to the invocation will be held within the process.An operation may have 0 or more parameters, or message parts that must be provided input values. Depending on the protocol used these parameters can be encoded differently.By default a single message can be used as input using the Single Input Message option. The runtime engine will construct protocol messages using a default mapping of parameters from the single input message according to protocol specific rules. In cases where there are multiple input parameters that cannot be constructed using the default mapping one can directly specify values for each parameter with the Multiple Input Parameters option.When choosing the Multiple Input Parameters option, variables in the process can be identified as the inputs to the parameters/parts defined for the operation. Each parameter of the operation will be listed in the Parameters table. A variable can be selected from the drop down in the same row to populate the parameter. If a variable is not assigned to a parameter the runtime engine will attempt to perform its own mapping for that parameter.A single output message will be returned from an invocation. A variable can be selected to hold that output for later use within the process.Click "Next" to continue or "Finish" to save your configuration and exit the wizard.

external.type.helpTitle

Invocation Details Editor

external.type.helpTitle2

Manage Outbound Identities

external.type.helpTitle3

Add Outbound Identities

external.type.helpTitle4

Manage Input/Output Parameters

receive.type.helpText

The Receive activity provides the entry point into the process. The caller will invoke the process by providing it with a message. That message will be stored in the variable selected in the activity's configuration screen. Only variables of type message can be used. There can only be one Receive activity in a process.

receive.type.helpTitle

Receive Details Editor

reply.type.helpText

The Reply Activity provides the exit point from a process. Every flow through the process must have one and only one Reply Activity. This means if there are multiple branches created from a Branch Activity, each branch must be terminated with a Reply Activity. The Reply activity can return a message to the caller. It is not required for one-way operation processes. Only variables of type message can be used.In addition to specifying the variable holding the message to return you can also indicate that the message is a fault by providing a Fault Name. Faults fall into two main categories, application faults and binding faults.An application fault is caused by a problem in the business process of the operation. For example if the operation was to withdraw funds an application fault may be for identifying there were insufficient funds.A binding fault is not specific to the business function of the operation. It a problem at the protocol layer itself. Binding faults are general to all operations. Examples would be security failures, communication failures, message parsing errors, etc.An application fault will be defined in the WSDL document for the operation. Policies can be attached to them. A binding fault is typically not referenced anywhere. In the Reply Activity Editor a Fault Name pull-down is provided that will contain the application faults found in the WSDL document for the operation as well as a reserved fault name of "BindingFault." You can choose what the message being returned represents. One other option is provided that is called "CurrentFault." That option is available only in the Fault Sequence Editor. It requires the reserved fault variable to be filled with a message and its fault name to be already known and used here.

reply.type.helpTitle

Reply Details Editor

switch.type.helpText

A Branch Activity is similar to a Java switch statement. It can support multiple branches. Only one branch will be followed. The branches have boolean conditions defined either by an XPath expression or a script. Each branch is evaluated in order. The first to evaluate to true is selected and the sequence of activities associated with the branch are performed.Branch Conditions are defined separately from the main Branch Activity in the Condition Details Editor. You add a Branch Condition by adding a new activity to the sequence (e.g., Script Activity, Invoke Activity, etc. ) and dragging a connector from the main Branch Activity to the target activity. There must always be a default branch that can be selected if no other branch conditions evaluate to true. This default Branch Condition is named "Otherwise" and must be added and set for each Branch Activity configuration.A Branch Condition can be written in any of the languages in the drop-down, is set in the Branch Details Editor and can only be changed there. The language selected will apply to all conditions within the branch.Note that if you have branch conditions defined and you choose to change the language all source will be deleted. It is recommended that you make a copy of your source content prior to changing the language.After you select the language for case conditions, you then save and exit your Branch Activity and add your connections.The result of the condition must be either true or false. If there are multiple conditions for a branch, the order in which they are executed can be changed by moving each condition up or down in the Case Conditions table. Note that the "Otherwise" condition does not display in the Case Conditions table but must still be defined.

switch.type.helpTitle

Branch Details Editor

throw.type.helpText

The Throw Activity exits the current flow of activities and enters the fault flow. A message variable can be identified as the fault message.

throw.type.helpTitle

Throw Details Editor

variable.type.helpText

The Variables and Faults Editor allows you to define variables that can be used in the process and faults that are handled within the process.Variables can be used in different activities to dictate behavior, such as using a variable to identify the endpoint of a service to invoke. Variables can also be used to store the output from web service invocations or provide input to web service invocations.A variable is identified by a name and defined by a type, or syntax. The type recognized by the system are message (used for input or output of a web service invocation, request, or Reply Activity), string, int, long, boolean, float, or any (can hold any content). Activities that support the use of variables in their configurations will often restrict the use of variables based on type. Optionally a default value can be given to a variable. If there is a default, at the beginning of process execution the variable will be given that value.To add a new variable, click "Add", select the variable type, and add a Default Value (if applicable). The variable will be added to the Insert Content, Invoke, Reply, and Transformation Activities. Note that added variables are available to activities in the current process only.Faults can be thrown as the result of an activity. If unhandled the default fault flow is invoked. Optionally fault flows can be defined for each named fault thrown within the process if they are identified here.To add a new fault, click "Add" and type the fault name. To remove a fault, select the fault and click "Delete". Note that any fault flow that has been defined for the fault will be deleted as well. To change the fault name, select the fault and edit the text.

variable.type.helpTitle

Variables and Faults Editor