Where do we set the deployment tier while deploying PRPC application
Where do we set the deployment tier option for deploying the prpc application. When I see the deployment tier of our application in lower environments like Dev/Test/Acc, it shows as in the attachment and in production it shows webandEnterprise. Our EJBs are not getting loaded in dev, test and acceptance.
***Edited by Moderator: Lochan to tag SR to post***
Thanks for your reply. I went through the installation guide and dont see any option saying webOnly or WebandEnterprise. The only thing I find is if we install prpc ear then its webandEnterprise else webonly for prpc war. For our application, we always deploy ear but the tier shows different in lower environments.
How can that be possible, Is there any other setting am I missing here.
[10-9-19 15:35:53:261 CEST] 00000108 SystemOut O 2019-09-10 15:35:53,261 [ Default : 6] [ ] [ ] [ ] ( external.timers.CpuTimer) INFO - CPU timers set to TOTALSONLY. Use prconfig setting 'initialization/CpuTimerLevel' with one of [FULL, TOTALSONLY, NONE] to modify.
[10-9-19 15:35:53:263 CEST] 00000108 SystemOut O 2019-09-10 15:35:53,263 [ Default : 6] [ ] [ ] [ ] (.timers.EnvironmentDiagnostics) INFO - Using Java 1.5 Thread.getAllStackTraces() for thread dumps
[10-9-19 15:35:53:268 CEST] 000000e4 SystemOut O Using sun.misc.Perf high-resolution timer for elapsed timings
[10-9-19 15:35:53:270 CEST] 000000e4 SystemOut O Using Java 5 Management beans for thread CPU timings.
[10-9-19 15:35:53:270 CEST] 000000e4 SystemOut O Using Java 5 Management beans for process CPU timings: 167598520000
[10-9-19 15:35:53:359 CEST] 00000108 SystemOut O 2019-09-10 15:35:53,359 [ Default : 6] [ ] [ ] [ ] (.access.PageDatabaseMapperImpl) INFO - DeflateStreams is turned ON.
[10-9-19 15:35:53:764 CEST] 00000108 SystemOut O 2019-09-10 15:35:53,764 [ Default : 6] [ ] [ ] [ ] (ernal.basic.SystemSettingsImpl) INFO - Failed to get setting with key: "database/databases/sample/customInfoDataPage" and owning ruleset: "Pega-Engine". PegaRULES database context is not available.
something is not right in your deployment/environment. go ahead and create a SR with GCS, we can take a look at your deployment. I assume you are already deploying the prpc_j2ee14_ws.ear and follow the installation guide, right?
We are deploying the ear from beginning but there was change at deploying things in websphere which made it to deploy the ear as web tier, already raised an SR for the same. Hoping PEGA team to help me in identifying the root cause. Thanks for your instant replies.
I have few MDBs in the ear file and also attached the ear file in the SR. I will need to see whether i can try the OOTB ear. I will let you after trying it. I dont think i can try that step right away.