Question

What is the difference between "BIX Extract run from Agent scheduler" and "BIX Extract run from UNIX script (CA7 job)".

Could you please explain in what purpose we use UNIX script to run PEGA BIX Extract.

***Updated by moderator: Lochan to add Categories***

**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.

Correct Answer
December 2, 2015 - 12:49am

BIX, till 7.1.8, was not available with all the options to be run via a Pega platform agent. If things needed to be scheduled to run at regular intervals, command line (batch script or shell script) was the only option.

Note that when run via an agent, it will run in a background thread in the same JVM as the node where it has been scheduled to run. If run via a shell script, it spawns a new JVM (process) to extract the data. So the call is whether to load the current JVM with extra processing or to spawn a new one.

Comments

Keep up to date on this post and subscribe to comments

December 1, 2015 - 5:27pm

we include a shell script to run bix extract from outside of application server. Like our other prpcutils script features, we use xml files to configure database connectivity and specify options. The shell fires up a stand-alone jvm that instantiates engine and runs the exportImpl BIX code.

with proper profile and setup, no reason that the shell script can not run under any standard task scheduler, including crontab or CA7

Pega
December 2, 2015 - 12:49am

BIX, till 7.1.8, was not available with all the options to be run via a Pega platform agent. If things needed to be scheduled to run at regular intervals, command line (batch script or shell script) was the only option.

Note that when run via an agent, it will run in a background thread in the same JVM as the node where it has been scheduled to run. If run via a shell script, it spawns a new JVM (process) to extract the data. So the call is whether to load the current JVM with extra processing or to spawn a new one.

May 5, 2017 - 11:36am
Response to nistr

Hi, please could you point to PDN help on how to run the scheduled command line script fox BIX extracts? 

Mod
May 5, 2017 - 12:01pm
Response to QURESHIH

Hello!

You can find all the BIX related information on the BIX landing page on PDN: https://pdn.pega.com/products/business-intelligence-exchange-bix

This link also contains the BIX User Guide.

Lochana | Community Moderator | Pegasystems Inc.

February 12, 2016 - 6:01am

And to Add to the above conversation, to run BIX from unix script, Pega (application) need not be up and running, BIX will interact with Pega database and perform the extract. No Additional load on Pega application. Please correct my understanding if it is wrong.

Regards,

Burhan.

February 12, 2016 - 8:36am
Response to _MohammedB9117

Yes you are correct.  As Andy stated earlier when running BIX from the command line it fires up a stand-alone jvm that instantiates engine and runs the exportImpl BIX code.  There is no interaction with the app server or Pega application.  It is strictly dealing with the database.  Of course it is the same database that the Pega application is interacting with if it is up and running so you still do not want to be running BIX extractions during peak hours.

February 12, 2016 - 9:44am
Response to CelesteDufresne_GCS

clarification question - does the BIX "engine boot" instantiate hazelcast + elastic and try to temporarily connect to 'running' nodes identified in pr_sys_statusnodes ?

Pega
February 18, 2016 - 10:03am
Response to AndrewWerden

Elastic Search is not started in embedded nodes unless you are using FullTextIndexer utility.

September 21, 2017 - 1:10pm
Response to CelesteDufresne_GCS

can't we make the engine up for all the time? if we would like to run a job every minute rather then going for every hour. is there any possibility?