cancel
Showing results for 
Search instead for 
Did you mean: 

TRANSPORT com.sap namespace

Former Member
0 Kudos

HI,

although, it is not recommended to change the iviews in com.sap.portal namespace. Due to few requirements, I had to do that.

now i want to transprot this content to QA,prod.. could you please let me know how can this be achieved.

Thank you

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Reddy,

Have a look at the following documents:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/38cf1698-0301-0010-d8a9-ae9...

&

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/519d369b-0401-0010-0186-ff7...

The first PDF is a very good How-To Guide.

Let me know if you need anything more.

Thanx,

Gaurav Gandhi

Former Member
0 Kudos

hi,

thanks for the reply. I know how the transport procedure works, but by default SAP export/import tool will not allow you to export and import objects in com.sap namespace. for that we need to tweak the pcdstartup.properties.

I wanted to know if there is any other procedure for this instead of changing the pcdstartup.properties, as we need to transport only one iview of this type.

Thank you

Former Member
0 Kudos

hi

use netweaver developer studio and open the par in it u will get par file in deployment directory under pcd in usr.

deploy it in QA with the help of windows -->preferences and configure your QA server address and user id and password.

hope thsi helps you .please don,t forget to gove points

with regards

subrato kundu

Former Member
0 Kudos

Hi Reddy,

Yes, by default you will not be able to transport com.sap namespace objects in a transport package.

But just very recently, i found out that even with this setting in pcdstartup.properties, we can still transport SAP.COM objects.

what my team did was that they created a transport package and added only sap.com namespace objects. & then tried to transport. It worked. It was then found that if we mix the customer namespace objects with the sap.com objects in the same transport package, it does not works.

You can also check like this.

It worked for us & we have been using this way now for transporting sap.com objects across multiple environments.

Regards

Gaurav

Former Member
0 Kudos

Hi Gaurav,

Thank you for the reply.. Hmm.. your solution didnt work for me... I am on SP14, what about your version?

a small question.. in which namespace did you create the transport package itself (in sap namespace?).. if not then it would be a mix of custom and sap namespace, which you were mentioning.

I am not sure whether the strategy you were mentioing is a bug or feature in previous releases.. might be they fixed it with this release..

what do you think?

Thank you

Former Member
0 Kudos

Hi Reddy,

Our Portal Veriosn: SP11

and the transport package is created in customer namespace only..i never tried creating anything is com.sap namespace but i dont think it should be done..

Well in your case, you can direclty modify the object in diff environment.

or since you are on SP14, you can make a copy the iView & do a "Change Id", in this way you can transport the copied iView.

Hope this helps

Thanx,

Gaurav

Former Member
0 Kudos

hi

There is a file called PCDstartup.properties where you have to define the export and import folder of usr directory.this actually transport the packages in export folder of DEV and which becomes your import folder for QA .use system administaration transports created a folder called Trans and create all trasnport packages in it . In transport packages always add roles or iviews and include dependencies by clicking on check box available when you open the transport package after editing at bottom. there are also how to guides available regarding transport as how to transport content from EP6 as well best practices from the sdn as well servicemarketplace.hope this helps you please don,t forget to give points

with regards

subrato kundu