home.social

#sapbtp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sapbtp, aggregated by home.social.

fetched live
  1. #sapbtp 👉 SAP Business AI Plattform (or short SABAP? 😉)
    #sapphire

  2. #sapbtp 👉 SAP Business AI Plattform (or short SABAP? 😉)
    #sapphire

  3. New #SAP Influencing request: Use custom logo defined in tenant settings also for Profile Management / User Profile Application influence.sap.com/sap/ino/#/id (S-User required) #SAPBTP #BTP #IAS

  4. New #SAP Influencing request: Use custom logo defined in tenant settings also for Profile Management / User Profile Application influence.sap.com/sap/ino/#/id (S-User required) #SAPBTP #BTP #IAS

  5. From Boris Zarske I've learned about the option to configure #SAPBTP #CICD Service to use X.509 Client Certificates to authenticate to #CloudFoundry community.sap.com/t5/technolog Please support the influencing request to add this also to SAP Cloud Transport Managment #CTMS influence.sap.com/sap/ino/#/id (S-User required)

  6. From Boris Zarske I've learned about the option to configure #SAPBTP #CICD Service to use X.509 Client Certificates to authenticate to #CloudFoundry community.sap.com/t5/technolog Please support the influencing request to add this also to SAP Cloud Transport Managment #CTMS influence.sap.com/sap/ino/#/id (S-User required)

  7. Ever worried about where your AI data actually lives? 🌐 SAP's new EU AI Cloud initiative promises European organizations more choice & control over their AI & cloud operations, keeping data firmly within the region. They're even partnering with Cohere, Mistral, & OpenAI!

    Does this move make you feel more secure about enterprise AI adoption in Europe?

    #AI #CloudSovereignty #SAPBTP #Europe #DataPrivacy
    Link: artificialintelligence-news.co

  8. Hurray another CodeJam next month on #SAPBTP, specifically on the btp CLI and APIs. Join us in the lovely city of Wrocław, PL on Fri 06 Jun and then you're also set for the Inside Track event the day after. Win! 🚀 community.sap.com/t5/sap-codej @sap

  9. Hurray another CodeJam next month on #SAPBTP, specifically on the btp CLI and APIs. Join us in the lovely city of Wrocław, PL on Fri 06 Jun and then you're also set for the Inside Track event the day after. Win! 🚀 community.sap.com/t5/sap-codej @sap

  10. A Kotlin-based CAP Java Application (Part 1)

    Introduction

    I recently asked myself whether it is possible to develop a full-fledged cloud application using Kotlin and the SAP Cloud Application Programming Model for Java (CAP Java). Instead of only thinking about it, I decided to start a project to check this.

    I'm developing the application in several steps, each step is accompanied by a small blog article. I won't go into every detail when it comes to CAP Java, so knowledge in this area is beneficial to follow the steps.

    The application will be a link aggregator where users can add URLs to interesting information on the web. Links can be marked as private, mutual (only visible for other logged-in users), and public (visible for all).

    Creating and Adjusting the Project

    The first step is to create a CAP Java project as described in CAPire. I'm not going to go into depth here but only show what needs to be changed to use Kotlin for developing the microservice. Make sure that you have a model and database for local development. I chose SQLite to be on the safe side when it comes to integration of multi-tenancy in a later step.

    Let's start with the required changes in the parent pom file.

    1. Add a property for the Kotlin version in the <properties>:

    <kotlin.version>2.1.0</kotlin.version>
    

    2. Add the dependency for the Kotlin standard library to the dependency management:

    <!-- KOTLIN -->  
    <dependency>  
        <groupId>org.jetbrains.kotlin</groupId>  
        <artifactId>kotlin-stdlib</artifactId>  
        <version>${kotlin.version}</version>  
    </dependency>
    

    3. Add the Kotlin compiler plugin:

    <!-- KOTLIN PLUGIN -->
    <plugin>
    	<groupId>org.jetbrains.kotlin</groupId>
    	<artifactId>kotlin-maven-plugin</artifactId>
    	<version>${kotlin.version}</version>
    	<executions>
    		<execution>
    			<id>compile</id>
    			<goals>
    				<goal>compile</goal>
    			</goals>
    			<configuration>
    				<sourceDirs>
    				<sourceDir>${project.basedir}/src/main/kotlin</sourceDir>
    				<sourceDir>${project.basedir}/src/main/java</sourceDir>
    				</sourceDirs>
    			</configuration>
    		</execution>
    		<execution>
    			<id>test-compile</id>
    			<goals>
    				<goal>test-compile</goal>
    			</goals>
    			<configuration>
    				<sourceDirs>
    				<sourceDir>${project.basedir}/src/test/kotlin</sourceDir>
    				<sourceDir>${project.basedir}/src/test/java</sourceDir>
    				</sourceDirs>
    			</configuration>
    		</execution>
    	</executions>
    </plugin>
    

    4. Adjust the Java compiler plugin:

    As we still need Java compilation of the POJOs generated by the CDS compiler we have to adjust the settings of the Java compiler plugin. This is the change entry:

    <!-- JAVA COMPILER -->
    <plugin>
    	<artifactId>maven-compiler-plugin</artifactId>
    	<version>3.13.0</version>
    	<configuration>
    		<release>${jdk.version}</release>
    		<encoding>UTF-8</encoding>
    	</configuration>
    	<executions>
    		<execution>
    			<id>default-compile</id>
    			<phase>none</phase>
    		</execution>
    		<execution>
    			<id>default-testCompile</id>
    			<phase>none</phase>
    		</execution>
    		<execution>
    			<id>java-compile</id>
    			<phase>compile</phase>
    			<goals>
    				<goal>compile</goal>
    			</goals>
    		</execution>
    		<execution>
    			<id>java-test-compile</id>
    			<phase>test-compile</phase>
    			<goals>
    				<goal>testCompile</goal>
    			</goals>
    		</execution>
    	</executions>
    </plugin>
    
    

    As the perent pom is now complete, some changes need to done in the srv/ directory.

    1. Add the dependency for the Kotlin standard library:

    <!-- KOTLIN -->  
    <dependency>  
        <groupId>org.jetbrains.kotlin</groupId>  
        <artifactId>kotlin-stdlib</artifactId>  
    </dependency>
    

    2. Create Kotlin source directory:

    Create the directory srv/src/main/kotlin, create the base package for your project and add the Kotlin class Application in the base package with the following content:

    package io.github.linkaggregator  
      
    import org.springframework.boot.SpringApplication  
    import org.springframework.boot.autoconfigure.SpringBootApplication  
      
    @SpringBootApplication  
    open class LinkAggregatorApplication  
      
    fun main(args: Array<String>) {  
        SpringApplication.run(LinkAggregatorApplication::class.java, *args)  
    }
    

    3. Delete the Java source directory:

    As we want to develop the service in Java, the directory srv/src/main/java can be deleted now.

    Now you can build and run the service!

    That's it for the first part of this series. You can find the sources for this part on Github.

    In the next part we're going to switch to Groovy and Spock to develop unit tests. So stay tuned!

    @sap @sapcap #sapcap #cap #capjava #java #kotlin #cloud #sapbtp #btp

  11. A Kotlin-based CAP Java Application (Part 1)

    Introduction

    I recently asked myself whether it is possible to develop a full-fledged cloud application using Kotlin and the SAP Cloud Application Programming Model for Java (CAP Java). Instead of only thinking about it, I decided to start a project to check this.

    I'm developing the application in several steps, each step is accompanied by a small blog article. I won't go into every detail when it comes to CAP Java, so knowledge in this area is beneficial to follow the steps.

    The application will be a link aggregator where users can add URLs to interesting information on the web. Links can be marked as private, mutual (only visible for other logged-in users), and public (visible for all).

    Creating and Adjusting the Project

    The first step is to create a CAP Java project as described in CAPire. I'm not going to go into depth here but only show what needs to be changed to use Kotlin for developing the microservice. Make sure that you have a model and database for local development. I chose SQLite to be on the safe side when it comes to integration of multi-tenancy in a later step.

    Let's start with the required changes in the parent pom file.

    1. Add a property for the Kotlin version in the <properties>:

    <kotlin.version>2.1.0</kotlin.version>
    

    2. Add the dependency for the Kotlin standard library to the dependency management:

    <!-- KOTLIN -->  
    <dependency>  
        <groupId>org.jetbrains.kotlin</groupId>  
        <artifactId>kotlin-stdlib</artifactId>  
        <version>${kotlin.version}</version>  
    </dependency>
    

    3. Add the Kotlin compiler plugin:

    <!-- KOTLIN PLUGIN -->
    <plugin>
    	<groupId>org.jetbrains.kotlin</groupId>
    	<artifactId>kotlin-maven-plugin</artifactId>
    	<version>${kotlin.version}</version>
    	<executions>
    		<execution>
    			<id>compile</id>
    			<goals>
    				<goal>compile</goal>
    			</goals>
    			<configuration>
    				<sourceDirs>
    				<sourceDir>${project.basedir}/src/main/kotlin</sourceDir>
    				<sourceDir>${project.basedir}/src/main/java</sourceDir>
    				</sourceDirs>
    			</configuration>
    		</execution>
    		<execution>
    			<id>test-compile</id>
    			<goals>
    				<goal>test-compile</goal>
    			</goals>
    			<configuration>
    				<sourceDirs>
    				<sourceDir>${project.basedir}/src/test/kotlin</sourceDir>
    				<sourceDir>${project.basedir}/src/test/java</sourceDir>
    				</sourceDirs>
    			</configuration>
    		</execution>
    	</executions>
    </plugin>
    

    4. Adjust the Java compiler plugin:

    As we still need Java compilation of the POJOs generated by the CDS compiler we have to adjust the settings of the Java compiler plugin. This is the change entry:

    <!-- JAVA COMPILER -->
    <plugin>
    	<artifactId>maven-compiler-plugin</artifactId>
    	<version>3.13.0</version>
    	<configuration>
    		<release>${jdk.version}</release>
    		<encoding>UTF-8</encoding>
    	</configuration>
    	<executions>
    		<execution>
    			<id>default-compile</id>
    			<phase>none</phase>
    		</execution>
    		<execution>
    			<id>default-testCompile</id>
    			<phase>none</phase>
    		</execution>
    		<execution>
    			<id>java-compile</id>
    			<phase>compile</phase>
    			<goals>
    				<goal>compile</goal>
    			</goals>
    		</execution>
    		<execution>
    			<id>java-test-compile</id>
    			<phase>test-compile</phase>
    			<goals>
    				<goal>testCompile</goal>
    			</goals>
    		</execution>
    	</executions>
    </plugin>
    
    

    As the perent pom is now complete, some changes need to done in the srv/ directory.

    1. Add the dependency for the Kotlin standard library:

    <!-- KOTLIN -->  
    <dependency>  
        <groupId>org.jetbrains.kotlin</groupId>  
        <artifactId>kotlin-stdlib</artifactId>  
    </dependency>
    

    2. Create Kotlin source directory:

    Create the directory srv/src/main/kotlin, create the base package for your project and add the Kotlin class Application in the base package with the following content:

    package io.github.linkaggregator  
      
    import org.springframework.boot.SpringApplication  
    import org.springframework.boot.autoconfigure.SpringBootApplication  
      
    @SpringBootApplication  
    open class LinkAggregatorApplication  
      
    fun main(args: Array<String>) {  
        SpringApplication.run(LinkAggregatorApplication::class.java, *args)  
    }
    

    3. Delete the Java source directory:

    As we want to develop the service in Java, the directory srv/src/main/java can be deleted now.

    Now you can build and run the service!

    That's it for the first part of this series. You can find the sources for this part on Github.

    In the next part we're going to switch to Groovy and Spock to develop unit tests. So stay tuned!

    @sap @sapcap #sapcap #cap #capjava #java #kotlin #cloud #sapbtp #btp

  12. Create AI-Powered Solutions Faster with AI in SAP Business Technology Platform BTP youtu.be/amBCRzK7y_g?si=pTeNgC via @YouTube

  13. @audin you might want to try out github.com/gregorwolf/terrafor the next time you need to do the initial setup of a #SAPBTP trial account.

  14. @audin you might want to try out github.com/gregorwolf/terrafor the next time you need to do the initial setup of a #SAPBTP trial account.

  15. Great to see the new #SAP Learning Journey on Administrating SAP Business Technology Platform #SAPBTP being launched. Check out the blog post buff.ly/47MyygB and the #SAPLearning site buff.ly/3XPCWqL

  16. Great to see the new #SAP Learning Journey on Administrating SAP Business Technology Platform #SAPBTP being launched. Check out the blog post buff.ly/47MyygB and the #SAPLearning site buff.ly/3XPCWqL

  17. Greetings from the great city of Utrecht! I'm here to give an #SAPCodeJam today, kindly hosted by Tiny Lommers at Capgemini and facilitated by Mientje Paais at VNSG. The topic: the #SAPBTP CLI and APIs. Oh, and generally gaining command line superpowers, as the cloud is just a load of Linux machines, right? community.sap.com/t5/sap-codej

  18. Greetings from the great city of Utrecht! I'm here to give an #SAPCodeJam today, kindly hosted by Tiny Lommers at Capgemini and facilitated by Mientje Paais at VNSG. The topic: the #SAPBTP CLI and APIs. Oh, and generally gaining command line superpowers, as the cloud is just a load of Linux machines, right? community.sap.com/t5/sap-codej

  19. I love this feature: Download an Authentication Data file from the #SAPBTP Subaccount you want to connect to the #SAP #Cloud Connector and upload it in CC to add the Subaccount. No mess with S-User Passwords anymore.

  20. I love this feature: Download an Authentication Data file from the #SAPBTP Subaccount you want to connect to the #SAP #Cloud Connector and upload it in CC to add the Subaccount. No mess with S-User Passwords anymore.

  21. #sitBE continues with Geert-Jan Klaps on #SAP Business Technology Platform as a foundation for multitenant (partner) solutions #SAPBTP

  22. #sitBE continues with Geert-Jan Klaps on #SAP Business Technology Platform as a foundation for multitenant (partner) solutions #SAPBTP

  23. Vadim Klimov with the first #sitBE presentation about Developer Experience for SAP Cloud Integration #SAPBTP

  24. Vadim Klimov with the first #sitBE presentation about Developer Experience for SAP Cloud Integration #SAPBTP

  25. The @sap/cds version 8 release is out buff.ly/4cZ8Fvr looking forward to see the download trend to continue buff.ly/3WjX9VT #SAPCDS #SAPBTP

  26. The @sap/cds version 8 release is out buff.ly/4cZ8Fvr looking forward to see the download trend to continue buff.ly/3WjX9VT #SAPCDS #SAPBTP

  27. Hey, you. Do you like learning-by-doing? Networking with fellow tech enthusiasts in the SAP ecosphere? Are you in or near NL 🇳🇱?

    Then how about this double bill of #SAPCodeJam events, brought to you by the Developer Advocates, this September? Check them out and register before it's too late 👉

    On the btp CLI and APIs, in Utrecht (25 Sep): community.sap.com/t5/sap-codej

    On CAP and HANA Cloud, in Eindhoven (26 Sep): community.sap.com/t5/sap-codej

    #SAPCAP #SAPBTP

  28. @drajt why Eclipse for #SAPBTP development? Are you just used to it? Or because of Java? Which BTP environment?

  29. I've implemented the BAdI VSCAN_INSTANCE (Interface IF_EX_VSCAN_INSTANCE) of the Virus Scan Interface (VSI) using the #SAP #BTP Malware Scanning Service in #ABAP buff.ly/3UKN2rk . This question remains: Is the usage just from an on Premise ABAP system allowed or does the usage with a #SAPBTP deployed #UI5 app makes it legal?

  30. Has anyone implemented a Fiori Elements app deployed to the #SAP Build Work Zone Managed Approuter that allows setting of Default Values like #S4HANA? Any pointers to documentation will be helpful. #SAPBTP #BTP