Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Renaming and Configuring the CDD and Building the EAR

Begin by renaming the CDD from the Cache OM Tutorial, and add a few configuration details for backing store functionality: click a checkbox to enable backing store functionality, and select the JDBC Connection resource you want to use. Of course, more options are available for different needs.

Procedure
1. In TIBCO BusinessEvents Studio Explorer, right-click the `fdcache.cdd` resource and select Refactor > Rename. In the New Name field, type `fdstore` and click Preview. You can preview the effect of this change, then click OK.
2. Open the newly renamed `fdstore` CDD file in the resource editor.
3. Click the Cluster tab and select the General section on the left. Change the cluster name from `fdcache` to `fdstore`.
   Note: Cluster Clashes
   If you have clashes with other clusters running on your machine, use a different cluster name, discovery URL and listen URL from the other cluster or clusters. See Cache OM Tutorial > Adding and Configuring a CDD for details.
4. Select Cluster tab > Object Management > Persistence
   1. Select Persistence Option Store.
   2. Select Store Type Oracle (or as needed for your DBMS).
5. Select Cluster > Object Management > Persistence > Connection on the left and in the URI field, select the JDBC Connection shared resource you configured for the backing store (see Adding a JDBC Connection Shared Resource).

   You can optionally check that the rest of the CDD configuration is correct. Refer to Adding and Configuring a CDD.

6. Select Domain Objects > Default on the left.

   The Domain Objects area is where you configure how objects are managed. You can set defaults, and you can override them for specific entities.

   On the right, ensure that Mode is set to `Cache Only` (the default for the Cache OM CDD template).
   Select the Preload Entities checkbox.

   Preloading is not necessary for the tutorial to function, but it is a commonly used feature. See section introduction for more details.

   For legacy ID lookup implementations, select the Preload Entities and Preload Handles checkboxes. For details about legacy ID and enabling it for a project, see the Primary Key Strategies topic in the TIBCO BusinessEvents Administration Guide.

7. If there are override entries, check each entry in turn, and make sure that the Mode is set to `Cache Only`, and that the Has Backing Store checkbox is selected.
8. Save the CDD file.
9. In TIBCO BusinessEvents Studio Explorer, highlight the project name, then from the top menus select Project > Build Enterprise Archive.

   If you see a message asking you to save all project resources, click Yes. It means an unsaved resource editor is open.

   1. Change the Name to `FraudDetectionStore`
   2. In the File Location setting, specify a location from which you can access the EAR when you run the database setup utility and when you start the engine.
   3. At the end of the location string, change the file name to `fdstore.ear`. The FraudDetectionStore example ships with this value: BE_HOME`/examples/standard/FraudDetectionStore/fdstore.ear`.

      If you need a refresher on building the EAR file, see Building the EAR File.

What to do next

Now you are ready to run the scripts that prepare the backing store’s database schema.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.