WebSphere Adapter for JD Edwards EnterpriseOne

Metadata of business functions

The metadata generated by enterprise service discovery provides the adapter with instructions on how to process business functions. Metadata is generated at the business-object level, the operation level, and the property level.

You can view (and modify) the metadata values listed associated with the business object. Use Business Object Editor to modify the values. For more information about Business Object Editor, see Related product information.
Note: Do not change the metadata element name.

Business-object-level metadata

Business-object-level metadata for business functions defines the top-level container.

The following table describes the business-object metadata elements of a business function container objects.

Table 1. Metadata for business function containers
Metadata element Description
Type The business object type value is set to BSFN.
Operation
The specified operation metadata is defined in the JDEBFNOperationTypeMetadata tag and contains the following:
  • Name: Name of the operation.
  • BSFN: List of Business Functions associated with the operation.

The following table describes the business-object metadata elements of a business function.

Table 2. Metadata for business functions
Metadata element Description
BSFNName Name of the Business Function as it exists in JD Edwards EnterpriseOne

Property-level metadata

Property-level metadata can represent child objects or an array of child objects.

The following table describes the metadata elements of a property.

Table 3. Property-level metadata
Metadata element Description
Name The business function parameter name as represented in JD Edwards EnterpriseOne.
Type The type of the business function parameter as it exists in JD Edwards EnterpriseOne.
IOType

The type of the business function parameter as it exists in JD Edwards EnterpriseOne.

Possible values are:
  • IN: the parameter is mapped from the business object to the business function.
  • OUT: the parameter is mapped from the business function to the business object.
  • INOUT: the parameter is mapped both ways.
  • DEFAULT: the parameter is mapped using the default JD Edwards EnterpriseOne value. For adapter purposes, it is processed as INOUT.
RequiredType

Identifies if the parameter is required.

Possible values are:

  • YES: the parameter is required.
  • NO: the parameter is not required.
  • DEFAULT: the parameter is using the JD Edwards EnterpriseOne value. For adapter purposes, it is processed as NO.
Length The maximum possible length for the parameter value.
Reference

The xpath of the business object property that is used to obtain the value of this attribute. The xpath expression starts at the business function level. For example:

BusinessFunctionContainer
	BusinessFunction1
		Prop1
	BusinessFunction2
		Prop2
If BusinessFunction2/Prop2 property needs to be set with the value of BusinessFunction1/Prop1, the value of Reference for BusinessFunction2/Prop2 needs to be set to BusinessFunction1/Prop1.

Operation-level metadata

The metadata for an operation specifies the list of business function names of the business functions in the JD Edwards EnterpriseOne system. This name is used by the adapter to execute the business functions.

The following table describes the operation-level metadata elements of a business function container

Table 4. Operation-level metadata
Metadata element Description
Name The name of the business object operation.
BSFN
List of business functions associated with the operation.
  • Name: Name of the business function
  • RollbackOnWarnings: A boolean that indicates if the adapter needs to rollback the current transaction when the business function returns with execution warnings. The default setting is false.

Terms of use |

Last updated: Mon 30 Oct 2006 03:42:09

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)