MUD Administrator Test Migration Activities

To prepare the repository for the test environment, the MUD administrator, Adam Straight, must now perform several tasks directly on the master repository.

The MUD administrator, Adam, opens the sales.rpd repository in offline mode. As soon as he does this, other users are locked out, and get Windows permissions errors if they try to check out projects. If Adam needs to open and close the file several times, he needs to remove the Oracle BI repository from the shared directory while modifying it so that other users can't check out repository objects between his changes.

Adam changes the connection pool settings to match the test environment. When Model Administration Tool users check out projects, connection pool parameters aren't included in the checkout. The master repository in the MUD directory contains the test connection pools, but each individual developer might need different settings for connecting to their own test databases. At merge and publish, the connection pools in the master repository aren't overwritten by developer changes, so that they can continue to point at the shared test databases.

Adam must ensure that the new application roles are migrated to the test system. Because there are only two application roles, he decides to reenter them in Fusion Middleware Control on the test system. Adam also provisions some test users or groups to the new application roles so the security filters, permissions, and query limits can be tested.

Adam uploads the repository to the test system and restarts the Oracle BI Server. Using his local Model Administration Tool, he connects to the test Oracle BI Server in online mode and runs the consistency checker. If any application roles referenced by this repository are missing or incorrect, the consistency checker lists the errors.