CTS+ Configuration : SAP Data Services (4.2 SP10)
Hello,
We have recently upgraded our SAP Data services from 4.1 to 4.2. The change management was done by functional team including its administration. Now they want to pass administration and change management to us (SAP BASIS team).
What we did was implement SAP Data Services 4.2 SP10 in parallel of existing Data Services 4.1 and port over all repositories. Now being SAP BASIS admin we thought to implement CTS+ plus on this so its make everyone life easy to move changes across landscape and have more control over it.
Today I am sharing you that how we configured CTS+ on SAP Data Services. If you want to know more about configuration you can look at the SAP Help .
Prerequisites for implementation:
SAP Solution manager 7.2
SAP Data Services 4.2 SP10
Note: Make sure you read through SAP Note : 2236955 – CTS+ and HTTP-based deployment offering: Requirements
Steps to configure CTS Plus:
-
Create Non-ABAP system for your SAP Data Services Development system
Log-in to your SAP Solution manager TMS system and run STMS TCode
Go to System overview page (Overview >> Systems)
Create Non-ABAP System (SAP System >> Create >> Non-ABAP System)
Provide information as below
| System | : Data Services DEV system SID |
| Description | : Anything you like to put here |
| Select | : Activate Transport Organizer check box |
| Client | : Your productive client for SAP solution Manager |
-
Configure Tranport tool Parameters for Development System
Go to configuration of system by double clicking on it and click on Transport tool
Provide parameters as below
| WBO_GET_REQ_STRATEGY | SMART |
| WBO_REL_REQ_STRATEGY | MANUAL |
-
Configure Application
On System overview Page navigate to Extras >> Application Types >> Configure
Click New Entries
Provide Information is as below
| Application ID | : BODS |
| Description | : SAP Data Services and CTS+ |
| Support Detail | : http://service.sap.com (ACH:EIM-DS) |
On next message screen press Yes
-
Import Configuration on Target Data Services system QAS/PROD
Login to SAP data Services(http://host:port/DataServices/launch/logon.action) and Navigate to Administrator >> Object Promotion >> Import Configuration
Navigate to CTS tab
Select the repository and press Save
You will see Path prefix created and this path will be use on HTTP destination (next step)
-
Define HTTP Destination in TMS system
Open SM59 and create RFC type ‘G’
Provide information below
Technical Setting TAB
| RFC Destination | <SID_of_PROD/QAS>_DESTINATION |
| Description | SAP Data Service Deploy destination |
Target System
| Target Host | Data Services Host name |
| Service Port | Tomcat Port |
| Path prefix | Path from step :Import Configuration on Target Data Services system QAS/PROD |
Logon and Security
Provide user as Administrator and password of it and save destination
-
Create Non-ABAP target system for your SAP Data Services QAS/Production system
Log-in to your SAP Solution manager TMS system and run STMS TCode
Go to System overview page (Overview >> Systems)
Create Non-ABAP System (SAP System >> Create >> Non-ABAP System)
Provide information below
| System | : Data Services QAS/Production system SID |
| Description | : Anything you like to put here |
| Select | : Activate deployment Service check box |
| Methods | : Other checkbox |
On next screen Press New Entries button
Select BODS from the list (You created this on step: Configure Application)
Provide HTTP Destination (You created this in step : Define HTTP Destination in TMS system)
Save changes
-
Configure Web Service for Deployment
In your solution manager productive client run TCode ‘SOAMANAGER’
On next this screen click “Web Service Configuration under Service Administration
Search for EXPORT_CTS_WS
Open next screen by clicking on service and press “Create Service” Button (I have couple more listed there For PI and BOBj)
Provide service name and description and New Binding name
Example : EXPORT_CTS_DS
On next screen check User ID/Password and press next
Provide alternative Access URL : /export_cts_ds
Note: SAP strongly recommend to include current client in value of ‘Alternative Access URL’, i.e. better use something like ‘/100/export_cts_ds’ – to avoid ambiguities if similar configuration should ever be done in other clients.
Click Finish
Now you see service is created as below
-
Create user for RFC for Export Configuration
Create service user “BOLM_DS” in Solman working client with SAP roles below
SAP_BC_WEBSERVICE_CONSUMER
SAP_CTS_PLUS
-
Create export configuration in Development Data Services System
Login to SAP data Services(http://host:port/DataServices/launch/logon.action) and Navigate to Administrator >> Object Promotion >> Export Configuration >>Add
Provide all required information as shown in below picture and test connection
For any error check SAP Note : 2474199 – Failed to connect to the CTS server. Verify the connection configurations: Cause: Incorrect System ID configuration – SAP Data Services
-
Create Transport Layer
Create SAP transport layer in TMS system for Data Services Transports
-
Create Transport target
Create transport target for your dev system to QAS as Consolidation and from QAS to Prod as Delivery
-
Export/Import testing
Navigate to SAP Data Services Development system Administrator screen and click on Object Promotion
Select repository type and Type
Select the objects you want to add and press export button
Wait till export completes
Once export complete release transport for next system
Import transport in your target queue
You have successfully configured CTS+ for your SAP Data Services. I tried to show you end to end process and I use SAP Help to configure it.
If you want to know more about configuration you can look at the SAP Help
Thank you
Yogesh Patel
Hi Yogesh,
Very helpful!
Thank you.
Best Regards,
Mahesh
Hi Yogesh,
Very nice&detailed document, thanks indeed.
Do however have one comment: In section 'Configure Web Service for Deployment' we would strongly recommend to include current client in value of 'Alternative Access URL', i.e. better use something like '/100/export_cts_ds' -to avoid ambiguities if similar configuration should ever be done in other clients.
[Actually the 'Calculated Access URL' will always contain this client and may be used alternativly.]
Regards,
Hans-Dieter (CTS+ Dev. Expert, Walldorf/Germany)
Hello Hans-Dieter Frey,
That is totally true. I generally don't use it but it is nice to have!
Thank you
Yogesh
Hello Hans-Dieter Frey
I added note to the document. Since I have only one working client in SAP Solution manager I have it done this way.
Thank you again for the informative comment.
Regards,
Yogesh
Excellent Blog Yogesh Patel !!!
Hi Yogesh Patel,
If the schema for tables is different between dev and qas, is there any place to set the mapping?
Regards,
Shidong
Sorry but is this question for DS CTS+ config?
-Yogesh
Hi Yogesh,
Thank you very much for the detailed information on the BODS CTS+ configuration.
We have a situation where we would like to modify the objects in QA & production from a modification done in Dev, we imported the changes to QA data services and nothing was updated on target system.
Can you please suggest do we have option to overwrite the changes in Data Services Quality and Production when we import the changes from dev system using CTS+ ? If yes then can you suggest what are we need to do in administration point of view to overwrite the existing changes in quality and production systems ?
Regards
Srinivas
Generally when you import transport there is an option to overwrite originals on screen below
Hi Yogesh,
Thank you for the reply. i already tried with this option while importing transport request solution manager and it did not work for me, changes were not updated in quality system though i used overwrite original option. Please let me know if you know any other work around on it.
Regards
Srinivas
Try option 2,3 and 4
Yogesh,
This is a great write up, thank you for putting it together. I have a question on if you can configure multiple RFC Destinations for multiple repositories in QA/PRD with just one BODS system in STMS? In our current deployment, we have multiple Local Repositories in both QA/PRD to facilitate separation of work between development and operations teams that we would like to configure within the STMS system for transports. What we're seeing from your write up and the documentation from SAP is that this is a one-to-one relationship and can't be expanded upon.
Any insight from you would be really great.
Thanks
Genu
Hello Genu,
From STMS/CTS+ perspective the relation between RFC and system is exactly 1:1 (per application type, to be exact). As application type is fixed to value BODS here very probably this will require creation of multiple target systems on STMS/CTS+ side (on per target repository), and either connect via multiple delivery routes or via transport group to previous/’downstream’ system(s).
Regards,
Hans-Dieter (CTS+)
Hello,
We have done the configuration as you mentionned. We are facing 2 major problems.
1-The configuration doesn't support multiple user at the same time. All the exported modifications from different developpers are ending up in a transport that doesn't belong to the user. In your exemple BOLM_DS which is not acceptable for tracability required by the internationnal standard SOX. How do we support multiple users working at the same time.
2-It doesn't support CHARM from solman. The transport must be created by CHARM and CHARM put the owner as being the developper who create the transport, not the user BOLMDS. How do we bring back the ZIP file in the transport that belong to the user.
Hello Dominique,
For #1 please try to change the parameter WBO_GET_REQ_STRATEGY to CREATE, it worked for me (step “Configure Tranport tool Parameters for Development System” in this document). Also the developers will be able to change the request owner through Transport Organizer.
Regards,
Hello Yogesh,
Can you please explain about the Target repositories for import systems, while migration object from DEV --> UAT ,
Hello,
Any update related to Dominique's Belisle message from May 28, 2019 above?
Is it possible to create Data Services transport not associated with one user defined in Export Configuration?
How to associate transport created earlier in Transport Organizer and flagged as Preselect Request with objects selected to export?
Regards,
Marek