|
Node
|
Node Name
|
Field 1
|
Field 2
|
Example
|
Comment
|
|---|---|---|---|---|---|
|
Read File
|
ReadFile
|
File Name without path or targetID information, if applicable.
|
None, as the node contains the information provided in the file and does no other manipulation of it.
|
ReadFile_ESIDefa ult_BAPI_MATERIAL_SAVEDATA
|
|
|
Write File
|
WriteFile
|
File Name without path or targetID information, if applicable.
|
None, as the node contains the information provided in the file and does no other manipulation of it.
|
WriteFile_ESIDeb ugLog
|
|
|
JDBC Update
|
JDBCUpdate
|
None, as this is a one-way communication.
|
The Service it references. Log or CrossReference.
|
JDBCUpdate_ESI Log_CommitBOM
|
A few words strung together to give a brief description of what was logged. No underscores.
|
|
JDBC Query
|
JDBCQuery
|
None, as this is a one-way communication.
|
The Service it references. Log or CrossReference.
|
JDBCQuery_Error HandlingCode_Ha ndlingCode
|
A few words strung together to give a brief description of what is being queried. No underscores.
|
|
EMS Queue Sender
|
EMSSender
|
The schema (if no schema is characterized, then use the business object name) from Process Data column of the Input tab that is being mapped to the EMS Body (no underscores). for example, CBOPart or ESIPostResult.
|
Everything after the last dot in the queue name (after com.ptc.windchill.esi.). For example, Response.
|
EMSSender_ESIPostResult_Result
|
|
|
EMS Queue Receiver
|
EMSReceiver
|
Everything after the last dot in the queue name (after com.ptc.windchill.esi.). For example, Response.
|
The schema (if no schema is characterized, then use the business object name) from Process Data column of the Input tab that is being mapped to the EMS Body (no underscores). for example, CBOPart or ESIPostResult.
|
EMSReceiver_Response_ESIResponse
|
Assumes that there is only one EMS receiver on each queue.
|
|
RV Subscriber
|
RV Subscriber
|
The Subject Name after com.ptc.windchill.esi: For example, Error.
|
The schema (if no schema is characterized, then use the business object name) from Process Data column of the Input tab that is being mapped to the RV Message (no underscores). For example, CBOPart or ESIPostResult.
|
RVSubscriber_Error_ESIError
|
|
|
Publish RV Message
|
RVPublisher
|
The schema (if no schema is characterized, then use the business object name) from Process Data column of the Input tab that is being mapped to the RV Message (no underscores). For example, CBOPart or ESIPostResult.
|
The Subject Name after com.ptc.windchill.esi: For example, Error.
|
RVPublisher_ESIError_Error
|
|
|
Parse XML
|
XMLParser
|
Input Schema into Parser only if the input schema is different than the schema that you are parsing against.
|
Schema Parsing against: ESIEvent.
|
XMLParser_ESIEvent
|
|
|
Render XML
|
XMLRenderer
|
Input Schema into Renderer only if the input schema is different than the schema that you are rendering against. Typically, a map and render are combined, and thus this is the schema of the Process Data column of the Input tab.
|
Schema Rendering into: ESIRequest.
|
XMLRenderer_ESI Event_ESIRequest_GetPart
|
|
|
Checkpoint
|
Checkpoint
|
WC or Oracle Applications interaction schema that was last executed. For example, ESIResponse.
|
None.
|
CheckPoint_ESIRe sponse
|
|
|
Mapper
|
Mapper
|
Input Schema Name - on the input tab, the Schema of the Process Data being used. See XML schemas for a list of the schemas used in Windchill ESI and use the schema name - without the underscores - except when using API's.
|
Output Schema Name - the schema that is selected on the Output Schema tab, and used to map to the Activity Input column of the Input tab.
|
Mapper_ESIRespo nse_CBOMaster
|
In the case where the same schemas are being mapped from input to output, a description field should be included: The description should not have spaces or underscores - only two or three words strung together to describe the activity: Mapper_CB OMaster_C BOMaster_ FilterNoOrgs.
|
|
Java Code
|
Java
|
Description of what the class does using Windchill ESI Capitalization Notation.
|
Java_GarbageColl ection
|
||
|
Generate Error
|
Error
|
Process Definition Name without the "PD."
|
Error_LoggingSer vice
|
Error_LoggingSer vice Unsure as to the functionality of this activity.
|
|
|
Call Process
|
CallProcess
|
Process Definition Name without the "PD."
|
(optional) The inputs to the process.
|
CallProcess_Loggi ng_Service
|
|
|
Label
|
A sentence
|
Label name is what displays as the label on the process definition workspace.
|
|||
|
Start
|
Start
|
Process Definition Name, without "PD."
|
None
|
Start_Logging_Ser vice
|
|
|
End
|
End
|
Process Definition Name, without "PD."
|
None
|
End_Logging_Serv ice
|
|
|
Null
|
Null
|
None
|
(Optional) Description
|
Null_SimplifyLogB ranching
|
|
|
Invoke an Adapter Request- Response Sequence
|
Invoke
|
The name of the BAPI being invoked
|
(Optional) The BAPI previously invoked.
|
Invoke_BAPI_TRA NSACTION_COM MIT_BAPI_DOCU MENT_CREATE2
|
|
|
Write to Log
|
Write to Log
|
Description of what information is being written to the log using Windchill ESI Capitalization Notation.
|
None
|
WriteLog_Invoked BAPI_MATERIAL_SAVEDATA
|