Question of applying generated ddls and production level value
Hello,
We are using Pega 7.2 on Tomcat Application server. Can you please suggest on below questions:
1) What is the significance of production level value in setupDatabase.properties file.
2) If we use same schema names on all environments, can we use generated ddls from Dev for UAT and PROD or do we need to generate ddls for each environment?
Pegasystems Inc.
US
# During installs, the above system name is generated with the following production level.
# The system production level can be set to one of the below integer values (1-5):
# 5 = production;
# 4 = preproduction;
# 3 = test;
# 2 = development;
# 1 = experimental
production.level=2
For installation the value of this property indicates what production level the environment should be set to.
If you are doing new installations in the different environments then you can reuse the ddl generated. If you are upgrading environments you should rerun for each environment to allow the tool to compare what is currently in that schema to what it should be and genenerate the DDL specific for that environment.
UBS
US
Thanks Celeste.
While doing the rules import for first time it is taking more than half hour and it is extracting pegadbinstall-classes.zip file into tmp directory. Import zip file size is 7 MB.
Can you advise if it would take time to import rules for first time or should it be quick?
Pegasystems Inc.
US
I am not sure that I understand the question. For a new installation on 7.2.1 for example there are like 100 different RAP files to import into the database. That is going to take time. Any install or upgrade is very database intensive so the closer the node you are running the install is to the database server the faster it will be. You want to be in the same datacenter if at all possible to avoid multiple hops across the network. When the install/upgrade completes there should be a summary of the time each step took and then a further breakdown of the time the import of each RAP file took.
Pegasystems Inc.
US
You really should have posted this in a new discussion. The importing of a RAP file via prpcUtils really has the same answer as with the importing of RAP files during the install. You want to be as close to the DB as possible. How long it takes depends on what you are importing. There will be some time needed to start the engine as well.
UBS
US
It took 5 mins for UI to import and 30 mins for importing same Zip file via prpcutil.sh . We see lot of files extracetd while doing import from command line . It created 3 folders and files as shown below. Not sure about these files and folders being created while running the script. ????
drwxr-x--- 7 crddev crddev 4096 Aug 11 19:32 load
-rw-r----- 1 crddev crddev 1974 Aug 11 19:33 prconfig.xml
-rw-r----- 1 crddev crddev 957 Aug 11 19:33 prbootstrap.properties
-rw-r----- 1 crddev crddev 121 Aug 11 19:33 oracledate.conf
drwxr-x--- 4 crddev crddev 4096 Aug 11 19:35 extractedFiles
drwxr-x--- 8 crddev crddev 4096 Aug 11 19:42 pr_temp
It took 5 mins for UI to import and 30 mins for importing same Zip file via prpcutil.sh . We see lot of files extracetd while doing import from command line . It created 3 folders and files as shown below. Not sure about these files and folders being created while running the script. ????
drwxr-x--- 7 crddev crddev 4096 Aug 11 19:32 load
-rw-r----- 1 crddev crddev 1974 Aug 11 19:33 prconfig.xml
-rw-r----- 1 crddev crddev 957 Aug 11 19:33 prbootstrap.properties
-rw-r----- 1 crddev crddev 121 Aug 11 19:33 oracledate.conf
drwxr-x--- 4 crddev crddev 4096 Aug 11 19:35 extractedFiles
drwxr-x--- 8 crddev crddev 4096 Aug 11 19:42 pr_temp
-bash-4.1$ cd extractedFiles
-bash-4.1$ ls -trl
total 8
drwxr-x--- 3 crddev crddev 4096 Aug 11 19:35 baseloader
drwxr-x--- 2 crddev crddev 4096 Aug 11 19:36 apploader
-bash-4.1$ cd apploader
-bash-4.1$ ls -trl
total 23684
-rw-r----- 1 crddev crddev 1519908 Aug 11 19:35 fop-0.20.5-dsm.jar
-rw-r----- 1 crddev crddev 652331 Aug 11 19:35 chemistry-opencmis-commons-impl-0.12.0.jar
-rw-r----- 1 crddev crddev 2111746 Aug 11 19:35 batik-1.5-fop-0.20-5-dsm.jar
-rw-r----- 1 crddev crddev 784290 Aug 11 19:35 praxiom-1.2.13.jar
-rw-r----- 1 crddev crddev 63934 Aug 11 19:35 prneethi-3.0.2.jar
-rw-r----- 1 crddev crddev 4126298 Aug 11 19:36 prhazelcast-3.4.1.jar
-rw-r----- 1 crddev crddev 409736 Aug 11 19:36 prhttpcomponents-core-4.1.3.jar
-rw-r----- 1 crddev crddev 361435 Aug 11 19:36 prhazelcast-client-3.4.1.jar
-rw-r----- 1 crddev crddev 10290217 Aug 11 19:36 saxon9he.jar
-rw-r----- 1 crddev crddev 379973 Aug 11 19:36 prhttpcomponents-client-4.1.2.jar
-rw-r----- 1 crddev crddev 1085 Aug 11 19:36 prrampart-module-1.6.2.jar
-rw-r----- 1 crddev crddev 1427 Aug 11 19:36 prrahas-module-1.6.2.jar
-rw-r----- 1 crddev crddev 2134205 Aug 11 19:36 praxis2-1.6.2.jar
-rw-r----- 1 crddev crddev 24589 Aug 11 19:36 praddressing-1.5.4.jar
-rw-r----- 1 crddev crddev 831966 Aug 11 19:36 pad-reporting-7.2.0.jar
-rw-r----- 1 crddev crddev 59653 Aug 11 19:36 avalon-framework-4.0-dsm.jar
-rw-r----- 1 crddev crddev 452994 Aug 11 19:36 prrampart-core-1.6.2.jar
-bash-4.1$ cd ..
-bash-4.1$ cd baseloader/
-bash-4.1$ ls trl
ls: cannot access trl: No such file or directory
-bash-4.1$ ls -trl
total 60
-rw-r----- 1 crddev crddev 56290 Aug 11 19:35 activation-1.1.1.jar
drwxr-x--- 2 crddev crddev 4096 Aug 11 19:36 java6
-bash-4.1$ cd ../../load/
-bash-4.1$ ls -trl
total 24
-rw-r----- 1 crddev crddev 19 Feb 3 2016 archive.info
drwxr-x--- 2 crddev crddev 4096 Aug 11 19:32 META-INF
drwxr-x--- 2 crddev crddev 4096 Aug 11 19:32 diagnostic
drwxr-x--- 2 crddev crddev 4096 Aug 11 19:32 images
drwxr-x--- 5 crddev crddev 4096 Aug 11 19:32 WEB-INF
drwxr-x--- 6 crddev crddev 4096 Aug 11 19:32 lib
-bash-4.1$ cd lib
-bash-4.1$ ls -trl
total 412
drwxr-x--- 3 crddev crddev 4096 Aug 11 19:15 base
drwxr-x--- 2 crddev crddev 4096 Aug 11 19:15 boot
drwxr-x--- 2 crddev crddev 4096 Aug 11 19:15 java7
drwxr-x--- 2 crddev crddev 20480 Aug 11 19:32 pega
-rw-r----- 1 crddev crddev 388822 Aug 11 19:32 prdeploy.jar
Pegasystems Inc.
US
It is created all of those in temp as part of starting the engine. There will be some time needed to start the engine. In the logs from the import we should be able to see if all of the time is being spent on the startup or the import. Like when you start the web application the first time the command line tool is going to take longer. On subsequent uses, when it is using the same temp area, it should be faster.