I was trying the beta version of React-based UI feature on Pega 8.5.1 but did not succeed.
Instructions I followed are:
Preparing your local Windows 10 system – 45 minutes
==========================================================================
To deploy Pega Platform using a local Windows 10 system on which you can run commands with administrator privileges, prepare your system with required applications and configuration files that you need for your deployment. By preparing your system, you can complete the deployment without having to pause to install a Windows application or prepare a configuration file.
Before you begin
----------------
To prepare a Wndows 10 system, it is assumed:
- You have a basic familiarity with running commands from a Windows 10 PowerShell with administrator privileges.
- You have appropriate administrative privileges to install programs on your local computer.
- You use the open source packaging tool Chocolatey to install applications onto your Windows laptop. For more information, see [How Chocolatey Works](https://chocolatey.org/how-chocolatey-works).
- You have basic familiarity with a GitHub account with which you download a Pega-managed GitHub repository that contains configuration files and scripts that support installing Pega Platform and deploying it in the Kubernetes cluster.
Creating a local folder to access all of the configuration files
----------------------------------------------------------------
show original
High level steps I performed:
Get image access key from Pega
Pull required images
Deploy pega, pega search, constellation to my locally running docker + kubernetes
Create a demo application
Enable React-Based UI in application rule and set appropriate costmos DSS
Create a Portal
Launch the poral - a blank page is displayed and and in browser tracer I see 400 error when pega is retrieving portal:
https://pega.local.com/prweb/app/my-cosmos-demo/api/application/v2/portals/MyTestPortal
Any suggestions will be appriciated.
PSOBO
December 31, 2020, 12:54pm
2
I have same issue.
Open HTML @baseclass.pxBootstrapShell in private edit and change restServer variable to Pega address with basic auth credentials, example: ‘https://operatorLogin:opertorPassword@localhost:8443/prweb ’ (this should be done around line 114)
Open “application” service package and change authentication type to Basic
Of course it is not target solution, but is good enough to see how React frontend app is working
@PSOBO Thaks for replying. My issue is slightly different. See the reply above.
@jasper.zhao After working with Pega Support/UI Team, it turns out to be a defect in the system. The issue is with the app url Pega generates - https://pega.local.com/prweb/app/my-cosmos-demo/api/application/v2/portals/MyTestPortal
The app alias “my-cosmos-demo” has dashes in it. Updating the application alias to “mycosmosdemo” resolved the issue.
Pega will fix the issue in next version. In the meanwhile, removing the special chars in the app alias will work around the issue.