SAP Portal - Migrate Portal Application from 7.0 to 7.1

I am surprised at the poor migration support of NWDS from 7.0 to 7.1.

I recently installed NWDS 7.1 SP08. Then I started the migration of my portal applications.

I couldn't found any way to do that other than exporting/importing par files. So I did it even at the warning of deprecation.

Then I got 5 missing library errors and 1 warning. The warning is an easy piece. Just use quick fix and it will be gone.

How to deal with these missing libraries? Here is what I did.

I created a new portal application in 7.1 and found there were normally 10 libraries referenced. I opened the .classpath file of the new project, copied the 10 library definitions and pasted in the .classpath file of the newly migrated project.

It still missed libraries of 8 classes.

A few notes,

TSSAP_JAVAX_HOME/lib/servlet.jar
->
SAP_EP/resources/servlet.jar

ECLIPSE_HOME/plugins/com.sap.security_2.0.0/lib/com.sap.security.api.jar
->
ECLIPSE_HOME/plugins/com.sap.security_2.0.0.091014073932/lib/sap.com~tc~sec~ume~api~impl.jar

SAP Portal - Portal Content Translation

1. Content Administration > Portal Content Translation > Translation Worklist Coordination
2. I usually create a folder "Translations" for this purpose
3. Right click folder "Translations" and select New > Translation worklist
4. I usually name the worklist [Role]-[Entity]-[Date]
5. After the creation, enter the edit mode of the worklist.
6. Same as you edit a transport package, select objects from Portal Catalog and add them into the worklist.
7. Click the Generate the translation data.
8. Release the worklist for translation. Note, the status is now Released for Translation
9. Here is a little bit tricky. You need to close the edit and go to the "Worklist Translation" from the left index.
10. Click Search you will see the worklist. If too many, try some keywords to narrow down.
11. Select Source and Target languages
12. Enter the translation
13. Save all.
14. Mark as Translated
15. Close.
16. Now go back to Translation Worklist Coordination and select the worklist from Portal Catalog and open it once again.
17. Click Publish Translation.
    

SAP Portal - WebDynpro ABAP iView

We are running Portal 7.0.18. The WebDynpro ABAP appl is called xyz.

We created an iView and specify the appl "xyz". Both previewing and opening in a page will only result in an endless loop.

Then we figured it out the Portal was sending the request to backend ABAP server like

https:///sap/bc/webdynpro/sap/xyz/;sap-ext-sid=......

That was wrong, it should be <...>/sap/xyz;sap-ext-sid=......

SAP must mistakenly append a "/" after appl name.

I am searching for the fix from SAP for this issue. For now, I just define the appl as xyz\ and the \ will nullify the /.

... after 2 hours searching ...

OK, SAP note 1230506 - Endless loop when starting Web Dynpro ABAP is right on it.

CentOS 5 Chinese Support

Just run yum groupinstall "Chinese Support", then restart the Tomcat server.

All done.