Watch out for our new book Extending SAP S/4HANA. Side-by-Side Extensions with the SAP S/4HANA Cloud SDK, in stores since May 30th, 2018. It features the complete end-to-end story of building extensions for SAP S/4HANA using the SAP S/4HANA Cloud SDK, with many code examples and in-depth explanations.

ScpCfService that gives easy access to services on Cloud Foundry defined in the VCAP_SERVICES environment variable. It includes methods for quickly retrieving the URIs and credentials for the service, as well as for adding required bearer token headers according to OAuth2 authentication flow.ScpCfService.of constructor method, access the base URL for calling the service with the method getServiceLocationInfo, and use the method addBearerTokenHeader to apply required authorization headers to an HTTP request. See our deep dive for an in-depth introduction.com.sap.xs.auditlog). The SAP S/4HANA Cloud SDK includes abstractions for easily accessing the audit logging service on SAP Cloud Platform, which we have updated to the new API with version 2.1.0 of the SAP S/4HANA Cloud SDK.com.sap.cloud.s4hana.cloudplatform:auditlog:AuditedDataObject for information about the data being accessed/modified and AuditableDataSubject for the owner of the data being accessed/modified. Wherever the API previously expected String-typed parameters objectId and objectName, it now requires objects of the two new classes instead.AccessRequester objects. When using the ofCurrentRequest constructor method, the tenant will be automatically retrieved from the current request. If you experience issues with tenant identifiers in tests, make sure to mock the tenant using mockCurrentTenant() in MockUtil.message except for security event audit log messages.slf4j. Furthermore, like the other archetypes, projects created by the scp-cf-spring archetype log in the JSON format suitable for use in Kibana when run on Cloud Foundry. Locally, a human-readable format is used. Unit and integration tests in all archetypes use slf4j-simple, so that the log level can easily be configured using the Maven command line parameter -Dsurefire.logLevel=<level>.Jwt and JwtDecoder classes in favor of using the java-jwt library and its DecodedJWT class. The JWT token is now explicitly validated, instead of implicitly relying on the security setup.httpcore) and 4.5.5 (client libraries).cx-server) that runs the Jenkins instance and other tools is optimized for running on Linux machines. With version 8, you can now use the cx-server on Windows for evaluation purposes. This feature lowers the barrier to try out the continuous delivery toolkit for all Windows users, because you don't need to get a Linux server just to try it out anymore.cx-server on Windows, simply run the cx-server.bat script, which is now generated by the archetypes in addition to the Linux script in the folder cx-server. Both now use a dockerized script for starting the cx-server - see the architecture decision record for additional background information.cx-server commands is supported on Windows. Running the cx-server on Windows is not intended for running a productive instance of the cx-server.cx-server on Windows, we have also automated the update of the cx-server script, so running cx-server update script is not required anymore after you have once updated to this new version.orgToken was configured directly in pipeline_config.yml. Now, it has to be configured as a secret in Jenkins and the credentialsId needs to be configured in pipeline_config.yml. See the updated documentation for further info.whitesource.config.json for the frontend and pipeline_config.yml for the backend). Now, the frontend configuration is generated from pipeline_config.yml, which means that the whitesource.config.json has to be deleted in order to avoid name clashes.--headless parameter. Since we cannot assume that the application developer always implements the --headless parameter, we instead provide an X server and leave the decision to the application developer. If your frontend unit tests need the --headless parameter, please add it to your npm ci-test script in package.json.sdk-bom dependency.2.1.0.<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.sap.cloud.s4hana</groupId>
<artifactId>sdk-bom</artifactId>
<version>2.1.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
<!-- possibly further managed dependencies ... -->
</dependencyManagement>-DarchetypeVersion=2.1.0 (or RELEASE)../cx-server update image
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 26 | |
| 24 | |
| 21 | |
| 13 | |
| 11 | |
| 9 | |
| 9 | |
| 8 | |
| 8 | |
| 8 |