Configuring Recommendation Settings

Use the Recommendation Settings page (ECL_ENVRECM_SET_FL) to configure or update recommendation settings.

Recommendation settings can be configured on this page only after it is enabled in Cloud Manager Settings. See Recommendation Settings Page.

The recommendations feature works only for environments with tags.

The recommendation is indicated as a badge counter against each environment. The badge is not displayed if there are no recommendations associated with an environment.

This example illustrates the badge counter for recommendations on the Environments page.

Clicking the badge displays all recommendations available for the environment. You can then take appropriate action based on the type of recommendation generated.

There are two types of policy recommendations:

• Infrastructure CPU

• Midtier Scaling

By default, Recommendations will be enabled for all recommendation type for the environment. If you want to update recommendation settings for the environment, navigate to Environments> Details > Related Actions > Recommendation Settings.

This example illustrates the fields and controls on the Environments > Recommendation Settings page. Definitions for the fields and controls appear following the example.

For Infrastructure CPU Recommendation, you can choose to either apply the update immediately or create policy.

This example illustrates the action available for Infrastructure CPU Recommendation.

When a recommendation is available for the Infrastructure CPU, you can apply the updates immediately, or create a policy to apply it later. If you choose to apply the Infrastructure CPU immediately, you can click on Apply Updates. It will take you to Infrastructure CPU page in Environment Details. See Applying Infrastructure CPU Patches.

If there is no existing policy, selecting Create Policy option displays the Policy Editor page. You can review the prefilled policy and click Save to create the policy. You can create a policy with a policy action schedule, which will apply the Infrastructure CPUs at a specific date and time. If you do not set up a policy action schedule, the policy applies the Infrastructure CPUs immediately upon download. An Infrastructure CPU policy is created for a specific PeopleTools release such as PeopleTools 8.59 or 8.61. If the new policy is created for Infrastructure CPU, Cloud Manager prompts you to apply the Infrastructure CPU, because this newly created policy will be applicable for the next Infrastructure CPU Download.

If the policy already exists, the Environment Name is added to the existing policy and a message is displayed about this addition.

This example illustrates the details of Infrastructure CPU recommendation regarding patches displayed for the selected environment.

This example illustrates the action available for Midtier Scaling Recommendation.

If you choose to accept the recommendation to create a new policy, clicking the corresponding action on Actions field redirects you to Policy Editor page. See Using Policy Editor. The mid-tier scaling recommendation applies to environments that have monitoring enabled and forecasting data present. Cloud Manager provides a weekly recommendation for middle tier resources. A mid-tier scaling policy is created for a specific environment. If a policy already exists, Cloud Manager auto updates the existing forecast data with new forecast data. This policy needs to be recurring, so you must select the recurrence (Environment Midtier Scaling) or choose their custom recurrence under “Schedule”.

On selecting the Details field, Cloud Manager displays recommendation details for the respective environment. The x-axis denotes weekly node forecasting and the y-axis denotes forecasted nodes. The values for each day in the week match the values for parameters Day 01 (Monday) to Day 07 (Sunday) in Policy Action Parameters. See Using Policy Editor.

This example illustrates the details of Midtier Scaling recommendation displayed for the selected environment.

You can also discard any recommendation by selecting Discard corresponding to the recommendation.

There is a recurring job ( ECL_GEN_RECM) for generating recommendations, which serves the following purposes:

• Expire the generated recommendations on the expiry date.

• Generate new recommendations.