I was wondering if there is a way to install Bedrock 5.x on PA 3.15 (V12) on‑prem. The installation instructions refer to an API Key, which is not available in the on‑prem version.
Thanks.
If you have access to Arc, it has a comprehensive Bedrock installation tool. It is included in the free tier of the software.
If it detects a v12 instance it will automatically offer v5 versions:
It allows you to upgrade and downgrade to different release versions too:
Hi @harvey, Does Arc work with PA Local 3.1 (v12)?
I don’t think we’ve tested that scenario yet. We are constantly working on v12 support, but it takes a fair effort to upgrade our testing servers, and we can’t cover every scenario.
TLDR; It’s worth a try, but no guarantees. If it doesn’t work, submit a support ticket and we’ll work with you to get it resolved.
Hi @harvey, I did try it the other day. I used a similar a similar connection URL to what is used for PAaaS (v12) and it prompts for an API key like it does for PAaaS (v12). I wasn’t able to log in as I have a user name and password (OIDC). I’ll wait until it is tested and supported before I raise a ticket as I’m not in a position to work with you to resolve it.
EDIT: Arc didn’t prompt me for an API key. It cam up with a Bad Request.
In Workspace under your user name there should be a “Manage API Keys” option where you can generate a API key for your user. You can then use this to authenticate with Arc or any other 3P tool to PAaaS.
We are still living in a world where IBM hasn’t provided any mechanism to authenticate 3P tools to PAaaS except for API key. So it’s still this or nothing.
Hi @cw-ch-scott, That’s for IBM PAaaS (v12). This question is about PAL 3.1 (v12). The on-prem non-containerized version of version of v12. The “Manage API Keys” is not a feature of the local version.
It appears that the Bedrock code is consolidated in bedrock.json file. Could someone advise on the most effective method to extract the information and manually build each Bedrock process? V12 introduces a new TI data source called “JSON file,” though I’m not yet sure if it can be used to recreate the bedrock process. Thanks
Sorry I missed that.
I wasn’t aware that anyone had (sucessfully) gotten 3.1 locall running yet.
We do and currently testing it. We are interesting to see how the }bedrock.process.multithread work on v12 on-prem. It would be nice if somebody provide the TI code for it. Thanks
