The main reason for this recommendation is that SAC Agent is being updated frequently to take advantage of the new connectivity types being offered in SAP Analytics Cloud. My recommendation would be to setup a new Tomcat server to deploy the SAC Agent. This can either be an existing Tomcat Java application server running in your environment or install(like I have done) a separate application server to deploy the SAC Agent war file. The SAP Analytics Cloud Agent(SAAC Agent) is just a war file that can be deployed on a Tomcat application server. Proceed to Configure Access Control in SAP HANA Cloud Connector section below and follow the steps specific to creating access control for SAP BPC NW. Note: This step is not necessary if only connecting to SAP BPC NW from SAP Analytics Cloud. edit conf/tomcat-user.xml and add the user details.When you log in for the first time the username/ password will be, Administrator / manage.
If you don’t know the port then you can run changeport.bat to change the port.by default, it is installed in C://SAP/sapcc.SAP Java Connector (SAP JCo), version 3.0.12 or higher.SAP Analytics Cloud Agent 1.0 : C4A_AGENT.Configure SAP Analytics cloud agent in your SAC tenant.Add admin S-User account to SAPCC, from which SAC account is created.
Deploy JCO ( Only for ERP and BW Connections).
#Sap jco download install
0 kommentar(er)
