Support for Local BOMs in Analysis Projects or BPM Developer Projects
You can still use local BOMs in Analysis projects and BPM Developer projects, but you should only do this when it is necessary. Best practice is to put local BOMs, WSDLs and XSDs in Business Data projects.
When you create a new BPM Developer project, the project does not by default contain a Business Object Model folder or Service Descriptors folder. When you create a new Analysis project, the project does not by default contain a Service Descriptors folder.
You should only add local BOMs, WSDLs or XSDs to a new Analysis project or BPM Developer project if you need to maintain compatibility with existing (pre-version 4.0) projects:
- If you want to add local BOMs to a project, you must first manually add a special folder of type Business Object Model to the project.
- If you want to add WSDLs or XSDs to a project, you must first add a special folder of type Service Descriptors to the project.
You can either select these assets when you create the project using the New Analysis Project or New BPM Developer Project wizard, or manually add them to the project later.
Local BOMs (whether user-created or generated) in existing Analysis or BPM Developer projects created in pre-4.0 versions of Business Studio are still supported. You can either:
- continue to use them as they are, in which case they will be handled by ActiveMatrix BPM exactly the same way as in earlier versions. (A BDS Plug-in corresponding to each BOM in the project is generated when you generate a DAA for or deploy the project.)
- move local BOMs or WSDLs into new or existing Business Data projects. If you do this, you must update any BPM process projects that reference the BOM to reference them from their new location.