A SAP user is required to support the Jenkins Integration.

The Integration could potentially use the existing AC_BATCH user, however given that this User is what the Test Results will be signed off against as part of the Integration – most customers might prefer to use a seperate System user for the Jenkins integration to help differentiate events relating to the Jenkins Integration from other Integrations or other events such as Scheduled Imports within ActiveControl.

If creating a seperate User, it should have the same authorisations as the AC_Batch user.

The credentials of this SAP system user need to be stored in Jenkins to be referred in the scripts:

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment