Challenge
At one of our customer we had to set up SAP Process Orchestration together with CTS+ for transporting both PI/SLD and BPM objects and together with NWDI for storing and administering the sources and builds. Target was to use CM Services instead of CMS.
I was looking for a proper guide, however was only successful to find the following good blog from devendrassoni. Unfortunately this blog was only covering the PI/SLD part of Process Orchestration:
Now, the challenge was how to also cover the setup for BPM. Therefor I decided to write this guide to give an overview about all required steps to get this whole thing running.
Basic Strategies for BPM transports
Basically there are two options available how BPM processes can be transported in the landscape by using CTS+:
- Source Transport (Granularity Options: Activity or SCA)
- Deployable Transport (SCAs)
The decision for transporting sources or deployables does not have any influence on what has to be configured for the development system in STMS.
The only difference is the required settings in the CM Services UI for export mode (see screenshot below and refer to the CM services guide for further details (http://scn.sap.com/docs/DOC-16163). Advantage of the "Source Export" mode is that you can transport either sources based on activities (changed source code) or on SCAs. Both is possible. In case of mode "Deployable Export" only SCAs can be deployed and the setup of a development configuration is only required for the development system. A detailed explanation can be found in the CM services guide mentioned before.
Activity Based Transports
In our given customer project we have decided to go with the option "source export" . This decision requires that a rebuild of the sources has to be done for every system involved in the landscape (i.e. development, user-acceptance and production system).
The transport of activities is triggered directly from within the SAP NetWeaver Developer Studio via the Transport View in the Development Configuration Perspective of the NWDS. When releasing an activity the sources are exported and attached to a transport request in CTS+. The file format of the attached activity package is called *.dip (Development Infrastructure Package). Transporting sources through the system landscape requires a development configuration (with DTR workspaces and CBS buildspace) for each target system that is part of the transport route in your landscape. The import is started from the import queue of the target system on the CTS+ system. Compared to the transport of deployable units the import process for sources triggers a rebuild within each CBS buildspace.
To ensure a new build in each system, a development configuration needs to exist for every system. This means that during the creation of the TMS settings always a development configuration needs to be created. Whenever an import is started, a re-build is triggered for the SDAs which contain the changed source files and for all dependent SDAs. The sources are integrated into the respective DTR workspaces.
Main characteristics for activity-based transports:
- Each system configured in TMS (i.e. development, test and production) needs to have a development configuration
- Each system has a Java URL assigned since each system acts as a deploy target
- Workspaces in DTR and Buildspace in CBS are created for each system
- The name of the buildspace in CBS is the same as the SID of a system in TMS
Setup Overview
Important:
It is NOT recommended by SAP to have NWDI installed on the same machine as PO or Enterprise Portal (update of one usage type requires also the update of the other usage type). Unfortunately the setup at our customer is not the recommended one, since NWDI is currently on the same machine as PO dev. Therefore the guide below describes the setup based on this assumption. I added a remark in brackets where not the PO development system should be added, but rather the NWDI system on a separate machine
1. PO Development System Settings
1.1 Transport Settings
Important: This guide does not cover the setup of CTS+. In our case the Solution Manager ABAP stack (system-ID DS1, as seen in the descriptions below) was the system hosting the transport landscape (CTS+ system).
1. Start transaction STMS in Solution Manager (or in any other ABAP stack hosting the CTS+ system) and goto “System Overview”
2. Create a new “Non-ABAP System”:
3. During creation, the following information needs to be provided:
- System: Here, the development PO runtime system which should be attached to NWDI and CTS+ needs to be entered. In our case system-id was DI1
- Communication System: Here, the system needs to be added which acts as CTS+ system. In our case this was the Solution Manager (DS1)
- Development Infrastructure: This checkbox needs to be checked to ensure that a development configuration is created for the development PO system. Button SLD allows entering the URL to the SLD.
- Source System Settings: This activates the transport organizer to create transport requests for this system. This needs to be done for each system for which exports should be done (usually only required for the PO development system).
- Target System Settings: Here the PO development runtime system currently configured needs to be entered. The PO development hostname needs to be entered and the following methods need to be chosen:
- XI/PI: For the transports of PI objects (ESR and ID objects)
- SLD: For the transport of SLD objects in the landscape
- DC (Deploy Controller): This is required to ensure that a runtime system is created in the development configuration in NWDI later. This is needed for the transport of BPM processes.
4. When a non-ABAP system is saved the first time with a development configuration (“Create Development Configuration” is checked) additional data is required. In this case the following popup windows will appear:
- System Landscape Directory: Here the URL of the SLD used by NWDI has to be entered
- Set User and Password for DI SLD: Here the user of the CM Services needs to be entered which is used to communicate with the SLD entered above. This user is usually NWDI_CMSADM.
- Set User and Password for DI Service: Here the user of the CM Services needs to be entered which is used to communication with DTR/CBS. This user is usually NWDI_CMSADM.
6. After the settings are saved, the user for the XI/PI deployment needs to be entered. In our case user NWDI_CMSADM was used.
IMPORTANT:
- Please be aware of SAP Note 1688705 for the SDM/DC user and connection settings!
- Also make sure that user NWDI_CMSADM has user group “SAP_SLD_ADMINISTRATOR” assigned in IDM. Otherwise the connection to the SLD will not work properly
7. After the changes are saved and distributed, the browser with the NWDI configuration opens automatically. Here you need to enter a user which has appropriate rights to change NWDI configuration.
1.2 Creation of a development configuration
1. After login, the development configuration has automatically been created as type “CTS System”:
2. Goto the “Local Settings” tab and enter the following values:
- Repository Location: http://<NWDI hostname>:50000/dtr
Important: In our case this was the PO development system where also NWDI was installed!
This is not recommended by SAP, see comment above
- Build Tool Location: http:// <NWDI hostname>:50000
Important: In our case this was the PO development system where also NWDI was installed!
This is not recommended by SAP, see comment above
- Transport Settings: Choose “Source Export” with “Software Components” and “Activities” checked.
- Export Destination: sap.com/com.sap.tc.di.CTSserver
The Runtime System has automatically been set based on the checked DC (Deploy Controller) method in the STMS settings (see above) and cannot be changed here in edit mode. This would require the change of the TMS settings and a recreation of the development configuration.
3. To add the required software components to the configuration, go to tab Software Component Definition -> Add SC
4. The “Add Software Components” window appears. If the required SWC is not available in the SLD yet, the “Create New Software Component” wizard can be started.
5. Create the required SCs in SLD and assign those to the Development Configuration.
6. Save the Development Configuration.
1.3 Adaption of the Transport Settings
After the creation of the development configuration, the transport settings in STMS for the development PO system need to be changed in the CTS+ system (in our case this was DS1).
1. Start transaction STMS -> System Overview. Double-Click on the PO development system.
2. Goto tab “Transport Tool -> Change mode”
3. Perform the following steps:
- Change the value of parameter DEPLOY_WEB_SERVICE from value CTSDEPLOY to CTSDEPLOY_DI
- Remove parameter DEPLOY_DATA_SHARE
- Add parameter CTS_FILE_PROVIDER_URI with value jco:destination=NWDI_TRANS,buffersize=100000
- Add parameter NON_ABAP_WBO_INBOX with value /usr/sap/trans/EPS/in
4. Make a test of the configuration afterwards. All statuses need to be green:
2. PO User-Acceptance System Settings
2.1 Transport Settings
1. Start transaction STMS and goto System Overview. Create a new system with the following settings:
- System: Here, the PO user acceptance runtime system which should be attached to NWDI and CTS+ needs to be entered.
- Communication System: Here, the system needs to be added which acts as CTS+ system (DS1 in our case).
- Development Infrastructure:
This checkbox needs to be checked to ensure that a development configuration is created for the PO user acceptance system. - Source System Settings:This activates the transport organizer to create transport requests for this system. Since no transports are exported from the PO user acceptance system this needs to be left unchecked (check is only required for the development system).
- Target System Settings:Here the PO user acceptamce hostname currently configured needs to be entered. The method DC and XI/PI needs to be chosen. SLD was not chosen in our case since the PO user-acceptance system was using the same SLD as the PO development system and therefore no SLD transports were required.
2. Enter all required users as done for the PO development system setup in STMS.
3. After saving, again automatically the browser for NWDI is opened. As for the setup for the development system, enter the login and password. The development configuration for the PO user-acceptance system is automatically created.
4. Goto Edit mode of the PO user-acceptance configuration and select the checkbox “Copy Definition From:” and select the PO development system. This copies all the local settings and software components definitions from the already existing PO development system configuration.
5. Change the settings back in STMS as follows:
3. Add the required SWCVs to the Development Configuration
For each type of development different Software Components are required. A set of the required SWCVs for each development type can be found in SAP Note 1572743.
For BPM processes the following SCs are required:
COMP_BUILDT
BPEM-BUILDT
BPEM-CONTENT
BPEM-COLLAB
BPEM-FACADE (for BPM public API usage)
BPEM_MM
CU-BASE-JAVA
CU-BASE-WD
DATA-MAPPING
ECM-CORE
ENGFACADE
ESCONF_BUILDT
ESMP_BUILDT
FP-INFRA
FRAMEWORK
MOIN_BUILDT
SAP_BUILDT
SERVICE-COMP
WD-RUNTIME
3.1 Dowload of required SCA files from SAP Marketplace
For each of the above listed SCs an SCA-file needs to be deployed to the PO system. If some of the SCAs are missing, those can be downloaded from the SAP Marketplace. To do this follows the steps below:
1. Goto SAP Marketplace -> Software Dowloads -> Search for Support Packages and Patches and enter the name of the SCA file you are looking for:
2. Download the appropriate SCA file according to the used PO version:
3. Upload all these SCA files to the inbox folder of the PO development system. The inbox folder is a folder on the PO system, standard path is /usr/sap/trans/EPS/in.
3.2 Start of the Synchronize Service
The Synchronize Service is used to compare software component versions in the runtime system with those in DTR/CBS and, if necessary, to adapt the development environment. It is no longer necessary to use an upload system and to create transport request manually to bring the required SCs into DTR and CBS (as done in older NWDI versions).
To start the Synchronize Service follow the steps below:
1. Goto NWDI -> CM Services and select the PO development system:
2. Select the PO development system from the system list. A list of all software components and its versions on the runtime system and the selected development configuration is shown:
3. Click on the Next button
4. Enter the inbox path to which the SCA files have been uploaded in step 3.1 (standard path is /usr/sap/trans/EPS/in). In this path all downloaded SCAs need to be placed which are required for a specific development. Then click on the Next button:
5. An overview of all available SCAs in the entered inbox folder is shown:
6. Now Select “Import Archives” as action wherever possible and select the version of the downloaded SCA.
7. Afterwards an overview is displayed:
8. Select Synchronize at the bottom of the list:
9. Wait till the synchronization is finished.
Closing Words
After completion of the above configuration steps also for all the other systems in the landscape, the development process should be business as usual:
- Configure the NWDS to connect properly to NWDI
- Import the development configuration of the PO development and finally start developing
Please let me know in case of any errors, additional required steps to be described or any other comments.
- SAP Managed Tags:
44 Comments
