A. A project, no. The .bpel process file can be opened, yes.
A. There is no easy way to do this because the data model is implemented using dependencies. The process itself can simply be deployed to the new server.
A. Refresh the Imports node in the Outline view. This causes Designer to re-read each of the imported files and accept any changes.
A. We recommend that you create a WSDL for PLTs. If you use Designer's wizard to create the PLTs and save them into a WSDL, the WSDL imports necessary WSDLs and XSDs.
A. Code supporting an extention activity is added to server engine. When the server encounters the extension in the executing process instance, it executes it. If the server does not have the supporting code, it either ignores the extension or throws a fault. This choice depends on how the mustUnderstand attribute is set in the extension. Consider all of these questions before deciding whether or not to use an extension activity in a process.
A. Yes. However, you can start with a Java interface (POJO), a sample XML file, or a schema and use the Interface wizard to generate a WSDL. Additionally, REST-based partners can use a built-in WSDL Interface (in V6). Prior to V6, developers need to import aeREST.wsdl.
A. For a comprehensive answer, consult our white paper on this subject at: Best Practices and Principles for Design
A. Use the WS-Security policy, as per the WS-Security standards.
A. By applying WS-Security policies to the endpoints. WS-Security support needs to be implemented in both the source and the destination application in order for it to work. ActiveVOS server has implemented WS-Security support, including encryption. WS-Security can be added to a process or a group of processes on deployment, not directly by the server. The way to add security, including encryption, is to attach a policy assertion to a My Role and/or Partner Role endpoint during deployment. See the section on User Defined policies for information on adding a Policy Reference, a set of security features, that can be applied to a process.
A. Developer attaches policy to each endpoint when creating the PDD file.
A. If there is security, it was provided in the PDD file when the process was deployed.
A. No. A Wait activity can be cancelled if its enclosing scope terminates.
A. Yes, but we added a scheduler to the V6.0 server, so doing so is unnecessary.
A. Yes, but a dead path is not necessarily seen as an error.
A. Yes, by sharing a workspace.
A. There is no current delete functionality. You must go into the wsdl file that contains them and delete the property reference. Adding a Delete button to the Properties dialogs has been submitted as an enhancement request.
A. To validate their correctness.
A. Yes.
A. Yes, use a schema type or schema derived type. Acceptable variable types are: Schema Type, Schema Element and MessageType.
A. XPath support is required by the specification because it is most widely used and most commonly understood. The spec allows other languages to be supported, but does not require any beyond XPath.
Inbound/Outbound messages using a single part of the element type (only) can use a From (inbound) or a To (outbound) to create a virtual assign and move data into or out of a variable without using an explicit Assign statement.
Q. Can we recommend a Rules Engine?
A. We have worked with JBoss users who were able to use their Drools engine.
A. Depends on the process itself. Each incoming message will be received by the app server using a separate thread from the HTTP thread pool. If the message is intended for the BPEL engine, the app server will dispatch the message to the engine. If the message is for a one-way invoke then the HTTP thread is released at this point. If the message is for a request-response invoke, then the HTTP thread will be blocked until the BPEL engine completes the processing of the message. Once a message is posted to the engine, if it is for creating a new process instance, then the engine will request a thread from the work manager to start a process instance. If it is for a correlated receive/onMessage, then the message will be routed to the thread where the receive/onMessage is running. There is a monitoring thresholds feature in the server so you can perform your own tests on resource usage and tweak the engine settings.
A. Yes, your ESB can intercept the inbound message before it is applied and therefore before the instance is created.
A. Yes.
A. A process can be printed and converted into a pdf or other format. The .bpel code file also retains comments and documentation in-line so that if you print it, they are embedded in the code. If you have an AdobePDF printer set up, you can print to PDF:File>Print>Adobe PDF. Also, each element in a BPEL process contains a Comment and a Documentation element. The Documentation element's contents becomes part of the process. There is also a <documentation> element as a child of <process>. Also, the customer may be interested in V6, since it includes Business Process Modeling Notation (BPMN), with a robust documentation feature.
A. No, except with a screen grab. Copying an activity (or group of activities) in Designer copies the underlying code.
A. Yes, these are available from your instructor.
A. No.
A. A good enhancement request that has been passed on to our development team.
A. The custom Ant tasks used in the BPRD files are defined in a jar called bpr_tasks.jar, which is installed with the Designer. You can look for it in the directory: