Question
EY
GB
Last activity: 21 Mar 2019 12:40 EDT
Pega BIX OOTB Operation Mechanis,
Hi All,
I was wondering if I can get some reference material / helps regarding the below questions (as I couldn’t find anything relevant in PDN or BIX Documentation so far) would be really great.
Context:
- Pega GOA and ROD (Ratingen Oracle Database) Integration via Pega BIX
Current Scenario:
- BIX Extract rules is set up with a case data model consisted with 4 different tables (for different page lists)
- Target DB has 1 main table and 3 sub tables at ROD side. (Sub tables are for Page Lists)
- An agent is set up to invoke OOTB pxExtractDataWithArgs to generate and write information to target tables.
- For each trigger – there will be only one case data that BIX is going to send out.
Questions:
- How does BIX insert case data into all 4 different tables - Does it happen sequentially, i.e. records are inserted in one table after another, or does it happen in parallel , i.e., case data is inserted into all four tables at once/in parallel?
- Does Pega commit as a whole at Transaction Level , or does it commit for each insert statement independently.
We tried to DB trace but still unable to decode the details. This questions we are asking as the downstream database system i.e. ROD is trying to find a way to conclude the Pega DB transaction for their design purpose.
Hi All,
I was wondering if I can get some reference material / helps regarding the below questions (as I couldn’t find anything relevant in PDN or BIX Documentation so far) would be really great.
Context:
- Pega GOA and ROD (Ratingen Oracle Database) Integration via Pega BIX
Current Scenario:
- BIX Extract rules is set up with a case data model consisted with 4 different tables (for different page lists)
- Target DB has 1 main table and 3 sub tables at ROD side. (Sub tables are for Page Lists)
- An agent is set up to invoke OOTB pxExtractDataWithArgs to generate and write information to target tables.
- For each trigger – there will be only one case data that BIX is going to send out.
Questions:
- How does BIX insert case data into all 4 different tables - Does it happen sequentially, i.e. records are inserted in one table after another, or does it happen in parallel , i.e., case data is inserted into all four tables at once/in parallel?
- Does Pega commit as a whole at Transaction Level , or does it commit for each insert statement independently.
We tried to DB trace but still unable to decode the details. This questions we are asking as the downstream database system i.e. ROD is trying to find a way to conclude the Pega DB transaction for their design purpose.
I really appreciate your help, please let me know if you need any more details.
***Moderator Edit-Vidyaranjan: Updated SR details***
Pegasystems Inc.
US
The extract is going to generate a series of inserts statements to the 4 tables. For each instance it will insert into top level table and then each of the pagelist tables if those properties have values. The inserts are batched together based upon the size of the batch (-b) argument. The default batch size is 30. These inserts are happening sequentially. Commit happens based upon batch size - ie, pass in batch of 30 inserts to the database and commit happens at that point. Repeat until completed.
Pegasystems Inc.
US
Here is the link to the BIX User's Guide. You can find information about the -b argument there as well as the batch identifier for each run, etc.
https://community.pega.com/knowledgebase/documents/bix-81-user-guide
Here is the link to the BIX User's Guide. You can find information about the -b argument there as well as the batch identifier for each run, etc.
https://community.pega.com/knowledgebase/documents/bix-81-user-guide