Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Kohei Yoshiwara (KoheiYoshi)
Tokio Marine Holdings

Tokio Marine Holdings
JP
KoheiYoshi Member since 2014 7 posts
Tokio Marine Holdings
Posted: Jan 18, 2016
Last activity: Jan 20, 2016
Posted: 18 Jan 2016 19:49 EST
Last activity: 20 Jan 2016 9:57 EST
Closed
Solved

Dedicated Data tables change to "pr_other" when "Export"

I develop and test my pega app at 2 environments, the development environment and the test environment.

I created a Data Table as a dedicated table (not "pr_other") in the development environment.

And I "export"(not "package") the ruleset from the development environment and import it into the test envorinment.

At that time, Data table change from dedicated table to "pr_other".

If I need to deploy Data Tables to other environments, Do I have to "package" my apss instead of "export"?

To see attachments, please log in.
Data Integration

Accepted Solution

Posted: 8 years ago
Posted: 19 Jan 2016 20:01 EST
Joel McLeish (JoelMcLeish)
PEGA
Senior Director, Service Assurance
Pegasystems Inc.
AU

You will still need the Data-Admin-DB-Table instances to tell the pega instance to use them.

Using a product rule should allow you to package without the operators, what occurs when you tick to exclude Operators from within the product rule?

To see attachments, please log in.
Posted: 8 years ago
Posted: 19 Jan 2016 9:56 EST
Carissa Wenhardt (CarissaW_GCS)
PEGA
Senior Principal Engineer, Technical Support, Industry Apps
Pegasystems Inc.
US

Hi Kouhei,

I think you would need to package up your application to ensure you get the Data-Admin-DB-Table instance at the very least.  This will map the class to the database table.  Depending on the version used, packaging will also give you options to create the table if you have that access, or you would need to have the SQL applied manually.


Regards,

Carissa

To see attachments, please log in.
Posted: 8 years ago
Posted: 19 Jan 2016 19:26 EST
Kohei Yoshiwara (KoheiYoshi)
Tokio Marine Holdings

Tokio Marine Holdings
JP

Hi Carissa,

Thank you for your advice.

But I have another problem with packaging.

I want to exclude Data-Admin-Operator-ID instances in packaged jar file, but I can't do it if I unchecked them at Application Packaging Wizard.

So I want to "export" rules.

I think a better resolution is to have the SQL applied manually.

Could you let me know how to create internal-table by the SQL?

Sincerely,

Kohei

To see attachments, please log in.

Accepted Solution

Posted: 8 years ago
Posted: 19 Jan 2016 20:01 EST
Joel McLeish (JoelMcLeish)
PEGA
Senior Director, Service Assurance
Pegasystems Inc.
AU

You will still need the Data-Admin-DB-Table instances to tell the pega instance to use them.

Using a product rule should allow you to package without the operators, what occurs when you tick to exclude Operators from within the product rule?

To see attachments, please log in.
Posted: 8 years ago
Posted: 20 Jan 2016 9:57 EST
Kohei Yoshiwara (KoheiYoshi)
Tokio Marine Holdings

Tokio Marine Holdings
JP

Hi Joel

Thank you very much!

All my problems are solved.

I can include the Data-Admin-DB-Table instances and exclude Data-Admin-Operator-ID instances from exported jar file by using "Product" rules.

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice