Steps to be performed (in order) to configure CTS+ on Solution
manager (S00) for Portal (EP*)transports
This documentation is adapted from SAP Help and my own
experience.Generally all settings and configuration is done on S00
(except for Section 3). Execute the steps in order. Basically First
you (i) Configure CTS Deploy Web Service and then (ii) Define and
Configure Non-ABAP system (iii) Configuring Transport Organiser Web
UI. The steps in here just explain how to add one Portal
development system (ED0) to the CTS+ systems (ie S00). You need to
repeat the steps for Portal QA and Production systems with slight
variation. Of course as usual, the exact configuration will depend
on your business scenario and organisational requirements or
restrictions.1. Configuring the CTS Deploy Web ServiceThe following
steps describe how to configure the CTS Deploy Web service, using a
dual-stack system as an example:Checking the CTS Deploy Web
Service1. In SAP NetWeaver Application Server Java (i.e EP), open
the CTS server.2. In your Web browser, enter the following
URL:http:// SystemsChooseSAPSystem Create Non-ABAP System.The TMS:
Configure Non-ABAP System dialog box is displayed.Create the
non-ABAP system with a system ID and a description.Select the CTS
system as the communication system.Make the following settings,
depending on whether your system is a source system or a target
system (or both): Non-ABAP system as source systemUnder Source
System Settings, select the Activate Transport Organizer flag and
enter the client where you want to use Transport Organizer.
Non-ABAP system as target systemUnder Target System Settings,
select the Activate Deployment Service flag. Select your preferred
deployment methods and fill out the rest of the fields
accordingly.Enter a system user and password for your preferred
deployment methods.Save your settings and confirm that you want to
distribute the TMS configuration.The system now generates all
parameters and their values automatically by default. To display
these parameters, select your system in the system overview and
choose the Transport Tool tab page.ResultYou have configured your
non-ABAP systems and you can now check whether your settings are
configured correctly.
Your systems are ready to be included in a transport route in
CTS. In CTS, proceed as usual for ABAP systems. However in this
case, we are only adding the Portal Development system (ED0) to the
lansdcape and will not be configuring the transport route.7.
Configuring Transport Organizer Web
UIReference:http://help.sap.com/saphelp_nw70/helpdata/en/ea/6213584a3f49119eccd7d739e55d5d/frameset.htmNow
proceed to configure Transport Organizer Web UI before you can use
it for your transports in SAP NetWeaver application.You configure
Transport Organizer Web UI by performing the following
activities:Changing the Standard Settings for Source SystemsIf you
want to change the standard settings (configured automatically when
you created your non-ABAP systems or dual-stack systems), you must
adjust the parameters in your source systems or add new
parameters.PrerequisitesYou have created non-ABAP systems or
dual-stack systems with automatically generated standard
settings.Procedurea) Call transaction STMS.b) Choose Overview ->
Systems.c)Select a system -> Click on Display configurationThe
screen Display TMS Configuration:System appears.d) Choose the
Transport Tool tab page.e) Switch to change mode (pencil).f) As
required, add the following parameters that control the behavior of
the source systems: NON_ABAP_WBO_CLIENTClient of the CTS
systemSpecify the client in which you want to use Transport
Organizer for this non-ABAP system. NON_ABAP_WBO_INBOXPath to the
directory where Transport Organizer searches for files This needs
to be read/write and available to both S00 and EP development
system ED0. E.g NFS mount or similarThis parameter enables you to
choose between a close or loose coupling of your SAP applications
and CTS: Close couplingYou need this parameter setting when you
attach files to a transport request from a server share/mount.The
default setting uses file streaming (see parameter
WBO_FILE_TRANSFER). Loose couplingYou need this parameter setting
when you attach files to a transport request from a server and not
from a desktop (client).More information:Choosing a File Transfer
Method WBO_FILE_TRANSFERFile transfer method between applications
(clients) and the CTS system (streaming or file share/mount)You
need this parameter only if you choose a close coupling.More
information:Choosing a File Transfer Method
WBO_GET_REQ_STRATEGYAutomatically creates a transport request when
you export an object from an SAP NetWeaver Portal system or an SAP
NetWeaver PI system.More information:Choosing a Transport Strategy
WBO_REL_REQ_STRATEGYAutomatically releases a transport request if
close coupling with an SAP NetWeaver Portal system, SAP NetWeaver
PI system, or SLD system is chosen.More information:Choosing a
Transport Strategy CTS_SYSTEM_MAPPINGEnter the system ID of your
non-ABAP system if it is not the same as the name of the
corresponding non-ABAP system in TMS.If possible, always create
your non-ABAP systems in TMS with the same system ID that you gave
the non-ABAP system when you installed it.
CTS_SYSTEM_TYPEClassification of the systems in transaction SMSY
for SAP Solution Manager scenariosWhen you create a non-ABAP
system, this parameter is generated with the value JAVA
automatically. For non-SAP systems, change this parameter to
OTHERS.
Activating the Web Service for Transport Organizer Web UIUseTo
check in non-ABAP objects to a transport request, you must activate
the Web service CTS_BROWSER.Prerequisites You need authorization
for transaction SICF. All ICF services required to run an ABAP Web
Dynpro application are activated.For more information, see SAP
Note517484.Procedurea) Call transaction SICF. This transaction is a
cross-client transaction. Enter SERVICE in theHierarchy Typefield
and CTS_BROWSER in theService Namefield. Choose Execute. Select the
Web service (CTS_BROWSER) on the Maintain Services screen. Activate
the Web service by opening the context menu (secondary mouse
button) and choosing Activate Service.A dialog box for activating
IFC services is displayed.ChooseYes(with tree icon).
Starting Transport Organizer Web UIUseYou must start Transport
Organizer Web UI before you can begin editing and organizing your
transport requests.Procedure Log on to the SAP system client with
the user and password that you want to use to start Transport
Organizer. To start Transport Management System (TMS), call
transaction STMS. To do this, choose Environment Transport
Organizer Web UI. (enter the EP* portal System ID when
prompted)This starts Transport Organizer Web UI for the client to
which you are logged on.In the System dialog box, choose the system
ID of the system for which you want to organize your transport
request. This is usually the development system.
Customizing for Application TypesUseThe application type is
purely a display attribute and does not determine the deployment
method. Application types are used in the CTS_BROWSER Web Dynpro to
classify attached objects. You can also add your own application
types manually in the table CTS_RQ_APPLID.Procedurea) Call
transaction SE16.The Data Browser: Initial Screen appears.b) In
theTable Namefield, enter CTS_RQ_APPLID.c) Choose Table Contents or
Enter.TheData Browser: Table CTS_RQ_APPLID: Selection
Screenappears.d) Leave the Application field empty and choose
Execute.The Table CTS_RQ_APPLID screen appears.e) Choose Create.The
Insert Table CTS_RQ_APPLID screen appears.f) Enter the name of the
application in the Application field.When you choose the F4 help in
the Application field, the application name you entered appears in
the list box.g) Enter a description of your application type in
theDescriptionfield.h) Save your entries.Now proceeed tomake
transport settings in the application, with the steps belowCTS+
browser is now working, proceed with the following stepsMaking
Transport Settings in the ApplicationConfigure the destination
serviceIf you want to transport objects directly from an SAP
NetWeaver PI or SAP NetWeaver Portal application, you must connect
the application to the transport system.To do this, make the
following settings in your SAP application and in the transport
system:Prerequisites You have change authorization in Visual
Administrator. You have a user with the appropriate authorizations
in SAP NetWeaver Application Server Java.Procedure1. Open Visual
Administrator on the installation drive of SAP Application Server
Java.2. Choose Cluster Server Services Destinations.3. Create an
RFC connection called sap.com/com.sap.tc.di.CTSserver by choosing
Create.4. Under Connection Settings, enter the connection data of
your CTS server.5. Under Logon Data, select the Current User (Logon
Ticket) option as authentication for the connection to your CTS
server. We recommend that you use Single Sign-On (SSO).If you
cannot use SSO, select the Configured User option and enter your
preferred language, a client, and an appropriate user and
password.Enter the client entered in the parameter
NON_ABAP_WBO_CLIENT in TMS.6. Use the default settings under
Repository Connection and Pool Settings.7. Save your entries.If you
want to test the connection, choose Save and Test.ResultYou have
created a connection between your SAP application and the transport
system. You can now attach objects to a transport request directly
in your application.
The below two steps have been covered above but are included
again to ensure you have selected the correct values and to review
those values:Choosing a File Transfer Method (repeat)To add
non-ABAP objects to a transport request, you must transfer these
objects (files) to the CTS server on which Transport Organizer is
located. You can transfer a file to the CTS server in the following
ways: You can use Transport Organizer Web UI to attach objects from
the desktop to a transport request. You can use a mount directory
or a share directory. In this case, you must set the parameter
NON_ABAP_WBO_INBOX and specify in which directory you want to
search for the objects to be attached to the transport request. If
your SAP application is closely integrated with CTS (this is the
case for SAP NetWeaver Portal, PI, NWDI, or SLD systems), you can
attach objects directly from the application by default. The data
is transferred to the CTS server using SAP Java Connector (JCo). In
this case the parameter WBO_FILE_TRANSFER is set to Stream by
default.If you want to improve performance by transferring files
using a share or a Network File System (NFS), you must set the
parameter WBO_FILE_TRANSFER to ShareChoose a transport
strategy(repeat)UseYou can influence the behavior of the transport
system when you create and release transport requests by
configuring the strategy parameters. In this way, you provide
optimum support for your chosen transport process (automatic or
manual creation and release of requests).You only require these
parameters for applications that have a close coupling with the CTS
system (such as SAP NetWeaver Portal systems and SAP NetWeaver PI
systems).PrerequisitesYou have configured the connection between
your application and the CTS server.Procedure1. Call transaction
STMS.2. Choose Overview Systems.3. Select a system.4. The screen
Display TMS Configuration:System appears.5. Choose theTransport
Tooltab page.6. Switch to change mode.7. Add the following
parameters: WBO_GET_REQ_STRATEGYAutomatically creates a transport
request when you export an object from an SAP NetWeaver Portal
system or an SAP NetWeaver PI system.The following values Ive used
SmartThe system creates a transport request (if not already
available) and flags it as the standard request.
WBO_REL_REQ_STRATEGYAutomatically releases a transport request in
an SAP NetWeaver Portal system or an SAP NetWeaver PI system.The
following values Ive used AutoThe system releases a transport
request automatically as soon as an object is added to the request
in an SAP NetWeaver Portal system or an SAP NetWeaver PI system.E.g
If you want to involve the developers of your SAP NetWeaver Portal
or SAP NetWeaver PI application as little as possible in transport
system activities, configure the strategy parameters as follows:
WBO_GET_REQ_STRATEGY = Smart WBO_REL_ REQ_STRATEGY = AutoWhenever
an SAP NetWeaver Portal developer, for example, exports non-ABAP
objects, the system creates a new transport request automatically
and then releases it
