We have PRPC 5.5 and BIX 2.3 (Extract jobs runs from standalone application ANT scripts using Extract rule XML's).
We are planning to upgrade to 7.1.9 and BIX 7.1 (which comes with distribution package). What are the steps involved for BIX upgrade ... Can anyone help please ...?
I read BIX user guide and though it says about new installation, for upgrade i comeup with following steps ... Is it make sense ? i mean any steps missing or any step is unnecessary ..? please suggest.
A. Import BIX Package and Validate Extract rules
Unzip the BIXDistributionImage.zip file to a directory.
Log in to Pega 7 Platform using an operator ID with Administrator privileges, Import pxBIX_ 07.10.01.zip. Package.
Add the BIX ruleset to your base ruleset version in the Application rulesets list
Verify application Extract rule for correctness
Recreate an XML representation of an Extract rule
B. Reset up stand-alone command-line Environment
Download the BIX distribution archive to and expand the archive into a directory.
Configure a JVM environment with access to Pega 7 Platform JAR files and the appropriate database driver files.
Configure prconfig.xml, prbootstrap.properties, and prlogging.xml provided in the configuration directory of BIX distribution to specify source Pega 7 Platform database and target database, Split schema variables setup. (We can refer existing BIX config file for this).
Regenerate pegarules.keyring file if required
Copy Extract rule xml to appropriate path
Validate ANT build file with that of sample build file provided in distribution package
Is steps A.4 , A.5 , B.4, B.5, B.6 really required or i can skip and use existing ..? please suggest ..
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
If your passing Extract rule insname or pzinskyes as inputs then these steps are not required.
These are required only if you are using the Extract rule xml as input for extracting the rules. From Pega 5.x to Pega 7.x XML structure could have been changed and that is the reason they suggest to take the latest extract rule xml and pass as input.
Step B4 is required if you don't want to metion the direct password name in configuration files. this will allow you to encrypt the password.
Another important thing is there ar new columns pxCommitDateTime and pxSaveDateTime added to work tables and all the incrementel extracts are done through pxCommitDateTime instead of pxUpdateDateTime. Upgrade process will not alter you custom work tables and you need to manuall alter all you custom work tables and populate these columns by running resave utility.
This info is alredy mentioned in the BIX user guide, please refere to page 42 (Optimizing BIX performance) section.
Thanks for your reply... It helps me lot to plan for upgrade activities.
Few things to clairify here is, we already have standalone BIX Envt set up (BIX 2.3) which uses Extract rule xml and pegarules.keyring file concept for Password encryption. So considering we will follow similar approach after upgrade, my doubts wree,
A4, A5, B5 required --> From your reply i read like yes we have to do
B4 --> Can we use old pegarules.keyring file or we need to generate new file ?
B6 --> ANT build file, we have existing build file, i am expecting it dont need any major chage, just crosscheck with latest example from v7 UserGuide and if any new paramaters added we need to update my old build file and add those additional changes.... Can you confirm please ?
Regarding your comment on pxCommitDateTime, thanks for mentioning this, somehowwhen i read userguide i didnt come across on this, will check again.
Appriciate your time to read this and respond back. Thanks.
I am not sure whether BIX 2.3 generated encrypt password will work for Pega 7. I suggest you to re-generate the new encrypted password in Pega 7. Regarding ANT build file(bix.xml) please compare with BIX 7.1.9 ANT build file make sure that you have all the parameters from BIX 7.1.9.