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

 Arijit Bose (ArijitBose)
Mphasis
Project Lead - Systems
Mphasis
US
ArijitBose Member since 2010 13 posts
Mphasis
Posted: Jul 1, 2015
Last activity: Jul 18, 2017
Posted: 1 Jul 2015 16:20 EDT
Last activity: 18 Jul 2017 10:55 EDT
Closed
Solved

Script or Executable file for automating import function in PRPC

Hi,

We have a unique requirement in our project where we want to automate the code migration process. There will be a separate tool (Not PRPC) which will upload the jar file (Jar file will be exported from DEV environment manually) into the QA application server. Now, we need to create a script or executable file which will automatically extract that jar file for QA environment (The standard feature of PRPC import, but we won't use the manual feature ).

Does anybody know how an external script can connect to PRPC and complete rule import from the application server? How can we configure it? I don't think the command line utility program for code migration does this as that one is for automatically migrating product from source to target, our requirement is a bit different.

Thanks.

***Updated by moderator: Lochan to close 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.

To see attachments, please log in.

Accepted Solution

Posted: 9 years ago
Posted: 7 Jul 2015 7:03 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

At somepoint in the 6.x series prpcUtils was enhanced so that you just need to use the parameter import and the tool figures out what kind of archive it is for you.

In your prpcUtils.properties file it looks like your database connection is not populated correctly.  This is what you have set.

pega.jdbc.username=S060206

pega.user.username=N767480

rules.schema.name=pega_data

 

data.schema.name is not populated

If this is a split schema then both rules.schema.name and data.schema.name need to be populated correctly.  For a import operation you do not need a Pega operator so pega.user.username does not need to be populated.  The pega.jdbc.username should be the database user that has all of the privileges needed to start the engine.  Basically this should be the same database user (or equivalent) to what is used in the datasource in your app server to start the regular system.

To see attachments, please log in.
Posted: 9 years ago
Posted: 2 Jul 2015 2:39 EDT
Phani Sahukaru (sahup1)
Pegasystems Inc.
Phani Sahukaru
Pegasystems Inc.
IN

Would taking a DB snapshot applicable?

  • not really sure or no idea - why we won't consider DB snapshot for migrations other than having the DB platform dependency and other installation supports like Split schema or MT like (please share your thoughts...)

though you're not looking at the following items - just wanted to have notes here...

  • through PRPC, DesignerStudio --> Application --> Distribution --> Migrate Product (will place the jar file at target system's static content folder. we will need to install accessing the system)

No idea on any (ant like) script base auto bundling & import process

To see attachments, please log in.
Posted: 9 years ago
Posted: 6 Jul 2015 17:33 EDT
Arijit Bose (ArijitBose)
Mphasis
Project Lead - Systems
Mphasis
US

I tried this and was almost able to configure it, but it throws this error:

** The mode "importPegaArchive" has been replaced by the mode "import".

** Continuing using import mode...

Buildfile: /wasdumps/Pega_software/scripts/utils/prpcUtils.xml

-init:

[pega:propertyparser] Reading Properties from : /wasdumps/Pega_software/scripts/utils/prpcUtils.properties

[pega:propertyparser] pega.jdbc.driver.jar=/home/db2cae01/sqllib/java/db2jcc.jar

[pega:propertyparser] pega.jdbc.driver.class=com.ibm.db2.jcc.DB2Driver

[pega:propertyparser] pega.database.type=udb

[pega:propertyparser] pega.jdbc.url=jdbc:db2://AASDDBW1D:60016/dprct000:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;

[pega:propertyparser] pega.jdbc.username=S060206

[pega:propertyparser] pega.jdbc.password=******

[pega:propertyparser] pega.user.username=N767480

[pega:propertyparser] pega.user.password=Green123

[pega:propertyparser] rules.schema.name=pega_data

[pega:propertyparser] pega.agents.enable=true

[pega:propertyparser] column.population.job.mode=COMMANDLINE_JOB

Show More

I tried this and was almost able to configure it, but it throws this error:

** The mode "importPegaArchive" has been replaced by the mode "import".

** Continuing using import mode...

Buildfile: /wasdumps/Pega_software/scripts/utils/prpcUtils.xml

-init:

[pega:propertyparser] Reading Properties from : /wasdumps/Pega_software/scripts/utils/prpcUtils.properties

[pega:propertyparser] pega.jdbc.driver.jar=/home/db2cae01/sqllib/java/db2jcc.jar

[pega:propertyparser] pega.jdbc.driver.class=com.ibm.db2.jcc.DB2Driver

[pega:propertyparser] pega.database.type=udb

[pega:propertyparser] pega.jdbc.url=jdbc:db2://AASDDBW1D:60016/dprct000:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;

[pega:propertyparser] pega.jdbc.username=S060206

[pega:propertyparser] pega.jdbc.password=******

[pega:propertyparser] pega.user.username=N767480

[pega:propertyparser] pega.user.password=Green123

[pega:propertyparser] rules.schema.name=pega_data

[pega:propertyparser] pega.agents.enable=true

[pega:propertyparser] column.population.job.mode=COMMANDLINE_JOB

[pega:propertyparser] user.temp.dir=C:/pega_temp

[pega:propertyparser] import.archive.path=SampleCodeMigFile.jar

[pega:propertyparser] import.mode=import

[pega:propertyparser] import.existing.instances=skip

[pega:propertyparser] import.nofailonerror=false

[pega:propertyparser] import.commit.count=100

[pega:propertyparser] import.compile.libraries=true

[pega:propertyparser] import.codeset.name=Customer

[pega:propertyparser] import.codeset.version=06-01-01

[pega:propertyparser] export.archive.full.path=C:/path/to/export/file/exported-Jan-5.zip

[pega:propertyparser] export.archive.productkey=

[pega:propertyparser] export.classes.included=

[pega:propertyparser] export.included.descendent=true

[pega:propertyparser] export.classes.excluded=

[pega:propertyparser] export.excluded.descendent=true

[pega:propertyparser] export.startVersion=

[pega:propertyparser] export.endVersion=

[pega:propertyparser] export.keys.file=

[pega:propertyparser] export.ruleset.name=

[pega:propertyparser] export.application.context=

[pega:propertyparser] export.preserve.locks=false

[pega:propertyparser] export.migration.xml=

[pega:propertyparser] export.migration.date=

[pega:propertyparser] expose.classes.included=

[pega:propertyparser] expose.included.descendent=true

[pega:propertyparser] expose.classes.excluded=

[pega:propertyparser] expose.excluded.descendent=true

[pega:propertyparser] expose.declareIndex.accessgroup=

[pega:propertyparser] expose.startKey=

[pega:propertyparser] expose.endKey=

[pega:propertyparser] expose.startDate=

[pega:propertyparser] expose.endDate=

[pega:propertyparser] expose.reindex=true

[pega:propertyparser] expose.reindexType=nonpega

[pega:propertyparser] expose.commitRate=100

[pega:propertyparser] expose.numOfThreads=

[pega:propertyparser] resave.classes.included=true

[pega:propertyparser] resave.included.descendent=true

[pega:propertyparser] resave.classes.excluded=false

[pega:propertyparser] resave.excluded.descendent=true

[pega:propertyparser] resave.startKey=

[pega:propertyparser] resave.endKey=

[pega:propertyparser] resave.startDate=

[pega:propertyparser] resave.endDate=

[pega:propertyparser] runagent.agentruleset=Pega-RulesEngine

[pega:propertyparser] runagent.agentname=PropertyOptimization

[pega:propertyparser] scan.applicationName=PegaRULES

[pega:propertyparser] scan.applicationVersion=

[pega:propertyparser] scan.lib.external.jars=

[pega:propertyparser] scan.result.file=E:/Results.csv

[pega:propertyparser] scan.ruletypes.file=E:/RuleTypes.txt

[pega:propertyparser] manage.hotfix=

[pega:propertyparser] syntax.rules.excludeCore=false

[pega:propertyparser] syntax.rules.allVersions=true

[pega:hasenoughspace] Found 7121816KB of free space on '/tmp'

    [mkdir] Created dir: /tmp/PegaInstallTemp-06-July-2015-17.28.18/load

    [mkdir] Created dir: /tmp/PegaInstallTemp-06-July-2015-17.28.18/pr_temp

     [echo] Using /tmp/PegaInstallTemp-06-July-2015-17.28.18 for install scratch space...

    [unzip] Expanding: /wasdumps/Pega_software/archives/prweb.war into /tmp/PegaInstallTemp-06-July-2015-17.28.18/load

    [unzip] Expanding: /wasdumps/Pega_software/archives/pegadbinstall-classes.zip into /tmp/PegaInstallTemp-06-July-2015-17.28.18/load

     [copy] Copying 1 file to /tmp/PegaInstallTemp-06-July-2015-17.28.18/load/lib

     [copy] Copying 1 file to /tmp/PegaInstallTemp-06-July-2015-17.28.18/load/WEB-INF/classes

     [copy] Copying 1 file to /tmp/PegaInstallTemp-06-July-2015-17.28.18

Checking Configuration Files:

_findSystemName:

     [echo] select max(s.pySystemName) from PEGA_DATA.pr_data_admin s inner join PEGA_DATA.pr_data_admin r    on s.pySystemName = r.pySystemName    where s.pxobjclass = 'Data-Admin-System' and r.pxObjClass = 'Data-Admin-Requestor'

Processing Configuration Files:

[propertyfile] Creating new property file: /tmp/PegaInstallTemp-06-July-2015-17.28.18/prbootstrap.properties

[propertyfile] Updating property file: /tmp/PegaInstallTemp-06-July-2015-17.28.18/udb.conf

Configuration:

     [echo] Database Type: udb

     [echo] JDBC Driver JAR: /home/db2cae01/sqllib/java/db2jcc.jar

     [echo] Bootstrap Config: /tmp/PegaInstallTemp-06-July-2015-17.28.18/prbootstrap.properties

     [echo] PegaRULES Config: /tmp/PegaInstallTemp-06-July-2015-17.28.18/prconfig.xml

     [echo] PegaRULES Logging Config: /tmp/PegaInstallTemp-06-July-2015-17.28.18/prlogging.xml

-import:

     [echo] about to Import from : /wasdumps/Pega_software/scripts/utils/SampleCodeMigFile.jar archive ...

     [echo] arg line :       -y   -c "100"  load -j "Customer" -k "06-01-01"      -M -U "N767480" -P "Green123"

     [java] Jul 6, 2015 5:28:23 PM com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource

     [java] 19830421: Loading bootstrap properties from file:////tmp/PegaInstallTemp-06-July-2015-17.28.18/prbootstrap.properties

     [java] Jul 6, 2015 5:28:23 PM com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

     [java] Jul 6, 2015 5:28:23 PM com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup

     [java] Jul 6, 2015 5:28:23 PM com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource

     [java] 19830421: Bootstrap datatables schema: PEGA_DATA

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Engine schema defined in allclasses: null

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting lookup

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.SettingReaderJNDI

     [java] 19830421: Could not find prconfig in the local JNDI context, skipping prconfig setting lookup

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Engine classes schema: null

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: Assembled classes schema: null

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421: prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRMiniLoader

     [java] 19830421: Will load phase 2 bootstrap from Pega-EngineCode:07-10-15

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRMiniLoader

     [java] 19830421: PRMiniLoader - unable to load classes from the database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=PEGA_DATA.PR_ENGINECLASSES, DRIVER=3.69.24

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] 19830421:

     [java] ============ PegaRULES Bootstrap Configuration ============

     [java]            Date: Mon Jul 06 17:28:24 EDT 2015

     [java]    Java Version: IBM Corporation 1.6.0

     [java]   Configuration: file:////tmp/PegaInstallTemp-06-July-2015-17.28.18/prbootstrap.properties

     [java] Pega-EngineCode: 07-10-15

     [java]        Database: DB2/AIX64 SQL10055

     [java]          Driver: IBM Data Server Driver for JDBC and SQLJ 3.69.24

     [java]

     [java] Unable to use given database configuration

     [java] Unable to locate classes on filesystem

     [java] =============== End Bootstrap Configuration ===============

     [java]

     [java] Unable to load phase 2 bootstrap class: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.internal.bootstrap.PRBootstrap

     [java] SEVERE: Error initializing PRAppLoader

     [java] Throwable occurred: java.lang.ClassNotFoundException: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

     [java]     at com.pega.pegarules.internal.bootstrap.PRMiniLoader.loadClass(PRMiniLoader.java:388)

     [java]     at java.lang.ClassLoader.loadClass(ClassLoader.java:665)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.loadPhase2BootstrapClass(PRBootstrap.java:685)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.checkForStartup(PRBootstrap.java:629)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:376)

     [java]     at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)

     [java]     at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:265)

     [java]     at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] Jul 6, 2015 5:28:24 PM com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega

     [java] SEVERE: Problem during method invocation (main)

     [java] Throwable occurred: java.lang.RuntimeException: PRAppLoader was not properly initialized, unable to load class com.pega.pegarules.deploy.external.util.ImportUtility

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.getImplementationOf(PRBootstrap.java:199)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.getEntry(PRBootstrap.java:292)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.getMethod(PRBootstrap.java:272)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:377)

     [java]     at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)

     [java]     at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:265)

     [java]     at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] Exception in thread "main" java.lang.RuntimeException: Problem during method invocation (main)

     [java]     at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:271)

     [java]     at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

     [java] Caused by: java.lang.RuntimeException: PRAppLoader was not properly initialized, unable to load class com.pega.pegarules.deploy.external.util.ImportUtility

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.getImplementationOf(PRBootstrap.java:199)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.getEntry(PRBootstrap.java:292)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.getMethod(PRBootstrap.java:272)

     [java]     at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:377)

     [java]     at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)

     [java]     at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:265)

     [java]     ... 1 more

BUILD FAILED

/wasdumps/Pega_software/scripts/utils/prpcUtils.xml:598: Java returned: 1

Total time: 7 seconds

Ant Process returned a non 0 value

I could not really understand how to fix this, so will need further help. I can confirm that the DB settings are fine, those are taken right from the setupDatabase.propertes file present in the scripts folder.


Show Less
To see attachments, please log in.

Accepted Solution

Posted: 9 years ago
Posted: 7 Jul 2015 7:03 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

At somepoint in the 6.x series prpcUtils was enhanced so that you just need to use the parameter import and the tool figures out what kind of archive it is for you.

In your prpcUtils.properties file it looks like your database connection is not populated correctly.  This is what you have set.

pega.jdbc.username=S060206

pega.user.username=N767480

rules.schema.name=pega_data

 

data.schema.name is not populated

If this is a split schema then both rules.schema.name and data.schema.name need to be populated correctly.  For a import operation you do not need a Pega operator so pega.user.username does not need to be populated.  The pega.jdbc.username should be the database user that has all of the privileges needed to start the engine.  Basically this should be the same database user (or equivalent) to what is used in the datasource in your app server to start the regular system.

To see attachments, please log in.
Posted: 9 years ago
Posted: 6 Jul 2015 17:58 EDT
Eric Osman (ericosman_GCS) Senior Software Solutions Engineer
Pegasystems
US

It looks like some params changed names.  I see this in my prpcutils.bat file for 6.3sp1:

if "%PEGA_TOOL%"=="importPegaArchive" goto :importMessage

if "%PEGA_TOOL%"=="importCodeArchive" goto :importMessage

if "%PEGA_TOOL%"=="importAppBundle" goto :importMessage

. . .

rem If the tool is one of the old import methods, inform the user

rem that they should use 'import'

:importMessage

echo ** The mode "%PEGA_TOOL%" has been replaced by the mode "import".

echo ** Continuing using "import" mode...

set "PEGA_TOOL=import"

goto :pegaToolOK

/Eric

To see attachments, please log in.
Posted: 9 years ago
Updated: 9 years ago
Posted: 7 Jul 2015 9:13 EDT
Updated: 7 Jul 2015 9:20 EDT
Bernard Matutat (matub) Senior Principal Demo Engineer - Field Support
Pegasystems Inc.
CA

[java] 19830421: PRMiniLoader - unable to load classes from the database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=PEGA_DATA.PR_ENGINECLASSES, DRIVER=3.69.24

Check your database configuration set in prpcUtils.properties as the embedded engine is not able to access the PR_ENGINECLASSES table using that configuration.

To see attachments, please log in.
Posted: 9 years ago
Posted: 7 Jul 2015 11:04 EDT
Arijit Bose (ArijitBose)
Mphasis
Project Lead - Systems
Mphasis
US

Hi Bernard,

I used exactly the same configuration as mentioned over there in the setupDatabase.propertes file, so it shouldn't be the wrong one I guess.

To see attachments, please log in.
Posted: 9 years ago
Posted: 7 Jul 2015 12:16 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

Please look at the properties that I asked about previously.   It is connecting to the DB but it cannot find the pr_engineclasses table in the PEGA_DATA schema.  By the name that would seem to be the data schema and not the rules schema where the pr_engineclasses table is located. 

To see attachments, please log in.
Posted: 9 years ago
Posted: 9 Jul 2015 12:05 EDT
Arijit Bose (ArijitBose)
Mphasis
Project Lead - Systems
Mphasis
US

It works now, thanks for pointing me to the correct direction. I was mistaking between rule and data schema. However, there is one problem still present though. I want to parameterize the zip file name, not able to do that though and I am hardcoding stuff at this point of time. I am still exploring options, but still thought if I can get some help.

To see attachments, please log in.
Posted: 9 years ago
Posted: 9 Jul 2015 12:15 EDT
Bernard Matutat (matub) Senior Principal Demo Engineer - Field Support
Pegasystems Inc.
CA

Parameterization of your scripts depends on your scripting environment.

If you are just using ant (and not calling ant from another environment) you can force a parameter value using the Java -D parameter:

ant import -Dimport.archive.path=/pega/myArchive.jar

You can also create another ant script that calls the import target in the prpcUtils.xml build. When you do that you can create your own property files to manage parameterization.

To see attachments, please log in.
Posted: 9 years ago
Posted: 9 Jul 2015 12:26 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

There is already an option to externalize the archive path available with the prpcUtils script.  If you look at the usage there is a archivePath parameter that can be used instead of filling in the propety within the properties file.

usage() {

echo "prpcUtils.sh export | exportRAP | import | expose | runagent | resave | runUpdateWizard | scanInvalidRules | manageHotfixes | javaSyntaxUpgrade | indexing | help [options...]"

echo ""

echo "Options:"

echo "  --driverClass  Your JDBC driver class (example: oracle.jdbc.OracleDriver)"

echo "  --driverJAR    Location of your JDBC JAR file"

echo "  --dbType       Database vendor type (\"mssql\" for SQL Server, \"udb\" for DB/2 UDB, \"oracledate\" for Oracle)"

echo "  --dbURL        JDBC URL to db to be loaded"

echo "  --dbUser       Database username"

echo "  --dbPassword   Database password"

echo "  --udbSchema    Sets the schema for UDB"

echo "  --archivePath  Full path to the archive to be imported or exported"

echo "  --hfixAction   If manageHotfixes is selected, sets the hotfix operation. Valid values are commit, rollback, generateDDL, install, and scan."

echo "  --U            PRPC User Name (Optional. But if provided, will be used only by exportRAP, resave, expose)"

echo "  --P            PRPC User Password (Optional. But if provided, will be used only by exportRAP, resave, expose)"

Show More

There is already an option to externalize the archive path available with the prpcUtils script.  If you look at the usage there is a archivePath parameter that can be used instead of filling in the propety within the properties file.

usage() {

echo "prpcUtils.sh export | exportRAP | import | expose | runagent | resave | runUpdateWizard | scanInvalidRules | manageHotfixes | javaSyntaxUpgrade | indexing | help [options...]"

echo ""

echo "Options:"

echo "  --driverClass  Your JDBC driver class (example: oracle.jdbc.OracleDriver)"

echo "  --driverJAR    Location of your JDBC JAR file"

echo "  --dbType       Database vendor type (\"mssql\" for SQL Server, \"udb\" for DB/2 UDB, \"oracledate\" for Oracle)"

echo "  --dbURL        JDBC URL to db to be loaded"

echo "  --dbUser       Database username"

echo "  --dbPassword   Database password"

echo "  --udbSchema    Sets the schema for UDB"

echo "  --archivePath  Full path to the archive to be imported or exported"

echo "  --hfixAction   If manageHotfixes is selected, sets the hotfix operation. Valid values are commit, rollback, generateDDL, install, and scan."

echo "  --U            PRPC User Name (Optional. But if provided, will be used only by exportRAP, resave, expose)"

echo "  --P            PRPC User Password (Optional. But if provided, will be used only by exportRAP, resave, expose)"

echo "  --accessGroup  AccessGroup in which the Rule-Declare-Index of the classes being exposed exists.(applicable for expose utility if --U or --P are not provided)"

echo "  --noFailOnError  Set to true or false. When enabled, instances that fail to import are skipped and import continues instead of failing"

echo "All \"--\" options are optional and will override options in the properties file"

        exit 1

}


Show Less
To see attachments, please log in.

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