Once the reference configuration files have been deleted, a new pipeline configuration project can be created.
When creating a new project using the Oracle Endeca Developer Studio, the user will be prompted with the following dialog box:
To create a new project:
-
In order for a new pipeline to be run properly within the
deployment template, the following must be properly specified:
- The Project Name field must be the same as the data prefix specified for the "app" element in [appdir]/config/script/AppConfig.xml. By default, this data prefix will have been set to the name of the application that was specified when running deploy.bat or deploy.sh.
- Recall that the [appname] specified was also used to create the base [appdir] directory. For example, if "myapp" was supplied as the [appname], and "c:\Endeca\apps" was supplied as the Deployment Directory, then [appdir] would be c:\Endeca\apps\myapp. In this example, the Project Name should also be specified as "myapp".
-
The
Save Project As field should be
[appdir]\config\pipeline\[appname].esp
In the example above, the Save Project As field would be c:\Endeca\apps\myapp\config\pipeline\myapp.esp.
After clicking the "OK" button, a number of
files will be created in the
[appdir]/config/pipeline/ directory. The primary
files to be concerned with are listed below:
| File name | Description |
|---|---|
| pipeline.epx | This is the main pipeline file that the deployment template will reference when running forge. |
| [appname].esp |
This is the Developer Studio project file that will be used whenever reopening the project. Although this file does not actually require the [appname] prefix, it is good practice to keep it consistent with other project files. |
| [appname].*.xml | These are the various configuration files that will be used later by the indexer and MDEX Engine processes. It is important that they have the same prefix as the deployment template Application Name. |
| dimensions.xml | This is the dimension file referenced by the default Dimension Adapter. |
