Regarding Transport Package in portal

[Former Member]

Hi All,

I deployed my webdynpro application into portal. I created a Folder and placed all the iviews and pages into it and made a Transport the package (and exported into my local machine). The epa file i want to imported into another server. The deployment was successfull. But i cant see my package or folder or package anywhere in content administrator. Where else can i find it? Where can i see the imported transport package?

Can anyone please help me out in this?

Regards,

Divya

[Former Member · Accepted solution]

Hi Divya,

You need to note one thing that while creating a transport package(say u want to tranport a all content in a folder called divya), you need to also include the folder structure which is above ur transport folder. So that the folder stucture gets created in the new server or system, otherwise the system will not know under which folder to place ur divya folder. Also the Webdynpro EAR files are to be deployed to the NEW server through SDM, it will not come in the new system unless u deploy the EAR file.

AWARD POINTS if this is useful..

Thanks

Yusuf

[Former Member]

Hi Divya,

Actually the problem is, the export functionality creates an epa file that includes the zipped epa file itself. So we need to extract to a temporary folder and import the extracted epa file in the Import Wizard.

These are some basic rules for Transport packages:-

The imported objects are created in the same Portal Catalog folder in the target system as in the source system. Since you can export entire folder hierarchies, the folder hierarchies are built analogously in the target system to the source system during import. All the attributes of a folder (name, description) are included in the export, and therefore exist in the target system after the import.

The following rules apply for storing the migrated objects in the target system:

1) If the folder hierarchies in the Portal Catalog are completely identical in the source and target systems, the object is created or, if it already exists, it is overwritten in the target system.

Example:

a) If the path for the content administrator role in the source and target systems is identical (Portal Content ® Portal Administrator ® Content Administrators), the role is created in folder Content Administrators in the target system analogously to the source system. If the role already exists in the target system, it is overwritten when the new version is imported.

b) If a folder hierarchy does not exist in the target system, you should always export the portal objects together with the entire folder hierarchy, and not export only the individual objects. The path with the folder names is built in the target system during the import. If you do not include the entire folder hierarchy in the export, the hierarchy is built during the import, but only object IDs appear instead of the folder names. This is because the folder attributes are not exported and imported.

c) If you only export part of the folder hierarchy, but not the complete hierarchy, and import this part into the target system, this part is created together with the folder name. The missing hierarchy levels are built in the target system, but only the IDs appear instead of the folder name.

Go through each example and find your case in them.

Regards,

Shailesh Nagar

Edited by: Shailesh Kumar Nagar on Feb 20, 2008 7:57 AM

[Former Member]

Hi

did u get any errors while importing the epa file in the server?

if u have imported the epa file successfully then u can the content in the content administrator -> portal content->migrated content folder where u can able to see all your info related to epa file.

Regards

Sunil

[ rewarded points helpful for helpful answers]

[S0019300750]

Hello Divya,

I guess the transport package was not created properly.

Please open that transport package in source system and check whether all the iViews you wanted to transport are present inside it or not.

If present export it to local system once again and import to destination system.

If not present add them to transport package.

You should see all the iviews in their same locations as they are in source system after successful transport.

• Award pts for useful answers *

[Former Member]

Hi,

Logout and login to portal and check if the folders are present. If not, Open the epa using winzip and check if the objects are added correctly in that. If all the objects are present, then try to import it again and check.

Regards,

Harini S