You can create a BPM Project (with common resources) in the Eclipse integrated development environment (IDE) of Progress Developer Studio for OpenEdge. These common resources can be accessed from and used in all Progress Developer Studio for OpenEdge projects, and can include folders for:
Business Objects - Java sources available to both EJB and Portal servers. Java files in this folder will be compiled into a hidden classes folder. Business Objects of the BPM Project (with common resources) are copied to the OEBPS_HOME\ebmsapps\common\bo\classes folder for use in Business Processes and to the <App_Server>\WEB-INF\classes folder for use in Web applications.
Note: <App_Server> refers to the path of the OEBPS folder for a specific application server. For the value of this configuration parameter, refer to the oebps.webappdir parameter in the OEBPS_HOME\conf\oebps.conf file.
Adapters - customized adapters for common Business Processes and Web applications. Adapters in Business Processes are copied to the OEBPS_HOME\ebmsapps\common\lib folder and adapters in Web applications are copied to the <App_Server>\WEB-INF\lib folder.
css - Stylesheet files. These stylesheet files are copied to the OEBPS_HOME\ebmsapps\common\css folder and Web applications are copied to the <App_Server>\ebmsapps\common\css folder.
External Business Objects - include compiled Java classes, XML resources, and custom dataslots. These are copied to the same location as Business Objects.
Images - Common image files are copied to the OEBPS_HOME\ebmsapps\common\images folder and images used in Web applications are copied to <App_Server>\ebmsapps\common\images.
Javascripts - include common javascript files. JavaScripts used in Business Process Portal applications are copied to OEBPS_HOME\ebmsapps\common\javascript whereas the ones used in Web applications are copied to <App_Server>\ebmsapps\common\javascript.
lib folder contains JAR files generated by compilation of files in the src folder or pre-existing JAR files. Common JAR files used in Business Process Portal applications are copied to OEBPS_HOME\ebmsapps\common\lib whereas the ones used in Web applications are copied to <App_Server>\WEB-INF\classes.
You can also use a BPM Project (with common resources) to publish common bpmportal resources. However, you must specify the target for the resources in a file that you create called dir.map, which should be included as a part of the project. For example, it is possible to publish some of the bpmportal resources such as css and javascripts, as part of a BPM Project (with common resources).
For example, assume your project contains a folder called bpmportal. It is possible to publish the content of the bpmportal folder in the project to the <App_Server>\bpmportal folder by adding a dir.map file to the project with the following entry:
bpmportal =__sbmweb_archive/bpmportal
(NOTE: a double underscore (__) is used to begin the equation)
Other available mappings that can be used in dir.map are:
“__ebmsapp_archive” to map content of the folder to OEBPS_HOME\ebmsapps.
“__webapps_archive” to map content of the folder to OEBPS_HOME\bpmebflow.
“__sbm_archive” to map content of the folder to OEBPS_HOME.
“__sbmweb_archive” to map content of the folder to <App_Server> folder (example, for JBoss, jboss\webapps\deploy\sbm.war).
Business Objects - Java sources available to both EJB and Portal servers. Java files in this folder will be compiled into a hidden classes folder. Business Objects of the BPM Project (with common resources) are copied to the OEBPS_HOME\ebmsapps\common\bo\classes folder for use in Business Processes and to the <App_Server>\WEB-INF\classes folder for use in Web applications.
