We've made some strides in the Installation/Upgrade of our newer Rocket DevOps portal (RDOp). From the inclusion of more requisite packages to better message handling, the process has made it much easier to install or upgrade the portal on the IBM i or Linux.
After the installation, there are a few 'admin' items that need to be addressed prior to getting the users in the pool. While our guide calls them out here, I'm including a brief summary below with some screenshots to ease the process and get you on your feet.
Best,
d
~~
After you've installed and started the RDOp subsystem jobs, you should be able to access the portal via a browser (e.g. Chrome, Edge...). The default URL would be using your development LPAR (or Linux server for RDOe on Linux) with http://<dev_server>:8890/page/login.
This section in the RDOp Installation Guide contains the default credentials (you'll be prompted to update on login) to access the portal for initial setup steps.
After login, you'll have access to the 'admin' profile options for RDOp configuration. The items below mirror our guide recommended steps and include a few screenshots for reference.
First, enable your RDOi|e|t applications for access via the RDO portal (this enables the APIs to access RDOi|e|t).
- Global Settings > Instance Settings, select RDOi - Edit - then toggle to 'Enabled' and save.
- Next, update the Global Settings > Global Configurations > Function ID. Edit and save the RDOUSR password... for 'RDOp' (only). This will allow RDOp to pull the RDOi users for additional setup.
Next, review 'Security' options and ensure we can pull/sync the RDOi|e list of Users... The following 'sync' message may be seen if RDOUSR creds are not known/saved in RDOp or the RDOUSR user profile is not defined in RDOi or Security Server.
Now that the RDOUSR credentials are saved, should be able to 'sync' and load list of defined RDOi|e users into RDOp for review. Will be able select for 'Edit' and update Role assignment (including the RDOUSR - defined to RDOi as-needed for deployment scheduling).
Find and update all users that should have 'Admin' RDOp role and enable those role options via this RDOp 'Security' option and save the updates.
Log out and then log in with one of the 'Admin' RDOi users...and should be ready to work with the RDOi instance AND have access to additional admin/setup options...
Please let us know if you have questions.
Can open a support case via our Rocket Customer Community support portal and we'll be happy to help.
------------------------------
Dale
L3 Support for the enterprise bits, portals and plugins...
Rocket DevOps (formerly Aldon)
Somewhere on the Oregon coast...
------------------------------