If you are using RDOp, so the RDOUSR is a topic you could not get rid of. Before installing RDO, manually create the RDOUSR user profile, supplying a password that meets your security Requirements is necessary.
The RDOUSR user profile, which owns the Rocket DevOps product, including RDOp, RDOe-api, RDOi-api, and
RDOt. RDOUSR is used as a "back-end" user to perform these actions:
◦ schedule deployment
◦ schedule reports
◦ synchronize users from the RDOi/RDOe servers (for the Portal security feature)
To enable the RDOUSR user profile to run the deployment or reports scheduler, authorize RDOUSR as a registered RDOe/ RDOi user. Registering RDOUSR does not consume an extra seat of the RDOe/ RDOi license. That means you could use RDOUSR to login RDOe GUI, run aldcs command, login RDOp and RDOi, and this user is free of charge.
To authorize RDOUSR to view RDOe information in Rocket DevOps, register it as a named or concurrent RDOe user in Security Server. For RDOi, you have to grant Perform deployment authority to RDOUSR.
When you authorize RDOUSR on Rocket DevOps with the RDOe server and the RDOi server, the name and password of RDOUSR must be the same on both servers if: RDOe on Linux is associated with RDOi on IBM i; or RDOe on IBM i is on a separate host from RDOi.
If you changed the RDOUSR password from the Linux platform (using ssh) or the IBM i platform (using the green screen), you do not need to choose the RDOi and RDOe options on the Function ID page. Simply choose the RDOp option to register the password to PostgreSQL for later usage.
RDOUSR have to obtain the read-write permissions of the RDOe-api/ RDOi-api log file path, or else the api installation will fail.
For more details, refer to the latest Rocket DevOps portal Installation Guide.
------------------------------
Jiqing Fan
Rocket Internal - All Brands
------------------------------