on 06-10-2007 2:05 PM
We want to Solution manager 4.0 to control ABAP and JAVA change
across the enterprise.
The only question is that whether we can use Solution Manager to replace NWDI.
Please advise, I'll give points. Thanks!
Hi Laura
Even i have the same requirement, unfortunately its is not vailable right now in solution manager SP11.
If you find something then please let me know.
Regards
Sukhii
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
The OTO is the TMS functionality to control non-ABAP transports, it is delivered with Basis SP12.
The integration between OTO-TMS functionality with the Change Request Management, will be available with SP12 for ST.
ST 12 is not yet released in swdc.
Hope this helps,
Dolores
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sukhii,
This new functionality is called CTS+ or OTO project and is comming in SP12 for Basis:
This enhancement enables you to use the transport functions in Transport Organizer and Transport Management System to transport non-ABAP objects. This includes objects such as the following:
- Objects from the SAP NetWeaver usage type EP (Enterprise Portal Archives, EPAs)
- Objects from the SAP NetWeaver usage type PI (XI transport files, TPZs)
- Objects from the SAP NetWeaver usage type DI (software component archives, SCAs; development component archives, SDAs)
The objects are transported in transport requests (type Workbench Request) along the transport routes defined between systems in CTS. You can include non-ABAP objects in transport requests either in CTS (transaction SE09) or on a Web Dynpro UI.
This enables you to manage transports between non-ABAP SAP systems in a central CTS.
A function for creating non-ABAP systems in CTS has been added to the existing UIs. To deploy objects in non-ABAP systems, you require a NW Java Server as well as SAP NWAS ABAP.
Effects on System Administration
You can now administer transports in a central system by creating non-ABAP systems and defining appropriate transport routes.
Effects on Customizing
Any existing settings in CTS are preserved
For the moment in the Solman system this functionality will be available in ST12 but still is not clear for which scenarios , probably for PI and EP.
Best regards,
Dolores
Hii Dolores
Thanks again for your informative reply, This will be really great. But I think for Administrators this will be a big configuration.
Wil SAP Provide config docs for this ?
OR We have to do R&D for this?
I had heard about this ST12 But Will this functionality be integrated with CHaRM or developments will be required?
Regards
Sukhii
Hello Laura,
Insteresting question, I will try to answer as best as I understand these concepts.
1. The OTO is the TMS functionality to control non-ABAP transports, it is delivered with Basis SP12.
So, this means that with Basis SP12 this functionality is available, independenly of using or not a solman system.
Your question is: can I sustitute the CMS (Change Management Service) of my NWDI for this new functionality? technically the answer should be yes
According to the description of OTO project or CTS+ functionality that you can see above this included:
- Objects from the SAP NetWeaver usage type DI (software component archives, SCAs; development component archives, SDAs)
So... yes! you could use this new functionality if your landscape DEV->CONS->TEST->PRD is in Basis SP12
Of course as this is a quite new patch I would do all the requered tests before.
2. After the solution manager system appears also in scene.
For that solman component ST SP12 has been release, this component allow solman system to use the Basis SP12 CTS+ functionality, again if the saellite involved are in basis SP12.
Hope this helps,
Dolores
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.