You configure the OAuth Client data in the SAP BTP cockpit and the SAP Cloud Integration Web UI. In the SAP BTP cockpit, you create a service instance of type xsuaa and provide the client ID and secret. In the SAP Cloud Integration Web UI, you create an OAuth2 credentials artifact and provide the authentication URL and token service URL.

You can configure SAP Commerce cluster settings in the %HYBRIS_BIN%/config/local.properties file for each cluster node. You can specify different cluster settings for each node, such as cluster.id, cluster.broadcast.method, or cluster.tcp.port. You can also set the cluster.node.autodiscovery to True to enable cluster ID autodiscovery, which allows nodes to join a cluster without specifying the cluster ID explicitly. You do not need to specify the same cluster settings for each node, nor do you need to specify them in the %HYBRIS_BIN%/config/tomcat/conf/server.xml file

The actions that you perform to use the EDMX schema are using the <Association> ... </Association> tag as a representation of the relationship between entity types, defining the structure of the payload that the Integration API will support for both inbound and outbound requests, and using odata2webservices to get the EDMX schema for the integration object. The EDMX schema is an XML-based format that describes the data model of an OData service. It defines the entity types, properties, associations, and functions that are exposed by the service. You can use odata2webservices to generate the EDMX schema for an integration object based on its item types and attributes. You do not use ComplexType and EdmSimpleType as part of the <Association> ... </Association> tag, nor do you update the EDMX schema by downloading it, changing it, and re-uploading it within the SAP Commerce Backoffice. Reference: 1