Prerequisites for the Refresh Cycle
Connection between SAP and Angles for SAP
During the refresh cycle of Angles for SAP (AgS), a connection to SAP is needed to extract the data. If the connection to SAP is unavailable, this will cause the refresh cycle to fail. AgS will be available, but it will contain old data. Configure your monitoring tools to check the ports used between the AgS Model Server and SAP before starting the Refresh Cycle.
AgS uses the following ports to connect to SAP:
Protocol |
Ports used |
|---|---|
SimpleRFC |
33xx |
SimpleRFC with load balancing |
36xx |
Angles for SAP account in SAP
To extract data from SAP to AgS, an SAP user account is needed. This user account should have the user type SYSTEM. The user must be valid and may not be locked out. Make sure that the password of this user never expires. When this user is locked out or expired, this will cause the AgS refresh cycle to fail. AgS will still work but it will contain old data.
Checklist for a successful refresh cycle
The following table lists out the detailed prerequisites for a successful refresh cycle. Before executing a refresh cycle, ensure that all the requirements are met .
|
|
Infrastructural and Organizational Prerequisites |
Responsible party |
|
Hosted On-Premise |
AgS-IaaS |
||
PR1 |
Ensure Sufficient AgS Hardware |
Customer |
AgS |
PR1a |
|
Customer |
AgS |
PR1b |
|
Customer |
AgS |
PR1c |
|
Customer |
AgS |
PR2 |
Ensure that QAS and PRD are maintained as separate systems |
Customer |
AgS |
PR3 |
Include AgS in the list of mission-critical applications and ensure effective disaster recovery and change management processes Notify the AgS support team when AgS-impact analysis is done in case of Windows OS maintenance activities |
Customer |
AgS |
PR4 |
Ensure that the AgS download performance on SAP is adequate |
Customer |
Customer |
PR5 |
Remove the EAdata folder and the folder where the application is installed from backup. These folders do not need backup. |
Customer |
AgS |
PR6 |
Include AgS SQL-server DB in backup |
Customer |
AgS |
PR7 |
Remove or Disable AgS from any anti-virus software |
Customer |
AgS |
PR8 |
Ensure that AgS to SAP connection is available and that there is sufficient bandwidth between SAP and AgS |
Customer |
Customer + AgS |
PR9 |
Ensure that the latest AgS patch or Service pack is installed |
Customer |
AgS |
PR10 |
Ensure that automatic updates are turned off for Windows and Java |
Customer |
AgS |
|
PR11 |
Ensure a valid AD-domain user for AgS AS Server and, in case of AgS-IaaS,that the ADFS service is running |
Customer |
Customer + AgS (ADFS) |
PR12 |
Ensure that all security certificates remain valid (extend certificates on time) |
Customer |
Customer |
PR13 |
Provide valid Windows authentication accounts |
Customer |
AgS |
PR14 |
Provide appropriate Windows authorization for AgS scheduled tasks |
Customer |
AgS |
PR15 |
Ensure that the SAP-user account is enabled and not expired |
Customer |
Customer |
PR16 |
Arrange for an adequate SAP-authorisation profile that corresponds with the SAP function module used. |
Customer |
Customer |
PR17 |
Ensure that a logical file path is available (IF FTP / sFTP or SMB) |
Customer |
NA |
PR18 |
Ensure that the SMB/ sFTP / FTP user credentials are not expired |
Customer |
NA |
PR19 |
Ensure that the RFC-destination is enabled in SAP-gateway |
Customer |
NA |
PR20 |
Ensure sufficient space on SAP |
Customer |
Customer |
PR21 |
Ensure that the VPN connection between AgS-system and SAP is established |
Customer |
Customer + AgS |