Overview of GP Content Delivery Framework
GP Content Delivery is a delivery process based on RCD (Rapid Content Delivery) Framework. It allows the customer to import/apply the GP content, a Support Package or a Release.
For details about RCD (Rapid Content Delivery Framework), refer to the wiki: Rapid Content Delivery
How new GP content is installed in customer systems
The RCD framework downloads the GP content package to customer system's RCD Staging Area, automatically.
Once the GP content package is in the RCD Staging Area, the package is "Ready to install".
The customer is notified in two places that GP content is ready to be installed:
- When he executes a guided procedure, he will see a message informing him that new GP content is ready.
- When he opens GP browser, a message in the Content Delivery area shows the current status of GP content.
Installation of new content
New content must only be installed from the Guided Procedure Browser. (not from the RCD UI, which should not be possible, the Import button on the RCD UI should be inactive).
When new content is ready to be installed, the "Install new content" button will be enabled. (If you have authorization. See Troubleshooting for more details).
To install the content, click on it. The installation will start. The information message will change to:
NOTE: The message will vary, depending of the kind of package being installed.
User do not have to specify the kind of package, the GP content routines detect the kind of content available, and installation those required.
The installation is asynchronous, so even if you close the GP browser, the installation of new content will continue in the background.
When the Installation is complete, "install new content" will be disabled in GP browser, and the message "Guided Procedure Content is up-to-date" will be displayed.
The 'import content' button is disabled although you can see that new content is available:
This is probably because you do not have authorization. To import content, you have to be GPA "Administrator”, with the rights to: create, change, delete, display and execute a guided procedure.
The authorization object is: SM_GPACUST.
Where to find Logs:
Extraction and Importation process logs some information in SLG1 on object: GPADLOG .
The log information is voluntary and not very detailed due to performance constraints, but it can still be helpful.
The log gives information about GPs skipped at extraction and import. A GP is skipped if a check fails.
At extraction time, you can find the ID and version of the GP in the log, and use Guided Procedure Maintenance to check the GP for the problem.
At import time, there is not yet an easy way to check the cause of the skip, but it will usually be a validity check.
At import time, you will also see which version of an existing GP has been set to inactive. (The import process, when importing a new GP, sets it to active, and deactivates the previous one).
If, at import time, you see something like the following in the log:
the GP content import process did not start, because the content package validity checks failed.