MSS iViews WDJ some iViews under Team, Organization, and PCR tabs are not working

[Former Member]

Hi

We have upgraded Enterprise portal from XX to 7.31 SP 21. After upgrade under Team, Organization and PCR tabs few iViews are giving errors. We have fixed taglib errors, and changed enum to ENUMS. But we still cannot these iviews work.

Process followed:

1. our Basis admin gave us the EAR files that have errors in iViews.

2. we have imported the EAR file into NWDS 7.31 file Import --> Java EE --> EAR, we get 3 components. for ex: 1. com.sap.pct.hcm.reminderofdates, 2. com.sap.pct.hcm.reminderofdates_web, and 3. Reminderofdates as a folder.

3. In _WEB component (2), we have the errors displaying. so when I fix the errors for instance in the file Reminderofdates.jsp we had enum references. so for 7.31 we have added com.sap.portal.htmlb.jar in the libraries, and changed the references to enums.

changed the taglib code from:

<%@ taglib uri="htmlb" prefix="hbj" %>

TO:

<%@ taglib uri="prt:taglib:tlhtmlb" prefix="hbj" %>

Save, export the _WEB file to a folder, and deploying again. But nothing is changing.

in few blogs I have read ComponentRequest and taglib still shows error, but can be deployed.

The deploy says success. But we dont see any thing on this iview.

adding few screenshots:

Anyhelp is really appreaciated.

Thanks

Hima

[former_member189220 · Accepted solution]

Hello,

How have you imported these EAR file? In case this is an embed app in the EP the supported way (by SAP), is to use NWDI and "modify" this custom code with the help of NWDS.

More details in my reply of this forum thread

https://answers.sap.com/questions/530347/sap-portal-webdynpro-java-project-from-ear-srczip.html

Regards,

[Former Member · Accepted solution]

Milen,

Thank you for the reply.

Importing EAR file:

1. Basis admin taken PAR file from 7.0 Portal file from Production which is still not upgraded, and migrated using PAR migrate tool, and given to us as .EAR file.

2. This EAR file we have imported as JAVA EE -->> EAR . which inturn in the project explorer giving 3 folders. for example, reminder of dates ear file when i import com.sap.pct.hcm.reminderofdates.ear file, I will get com.sap.pct.hcm.reminderofdates, com.sap.pct.hcm.reminderofdates_WEB, and ReminderOfDates folders, where _WEB folder shows the errors.

3. The way we try to fix these errors are by adding the respective libraries, etc.

4. After I post this message now we are able to get htmlb.lib file from basis, and add that also to the library. But when we deploy, we get the message deployment is successful. But when we open the portal the iViews shows error. the logs shows as Compilation errors.

Thanks

Hima

[former_member189220 · Accepted solution]

Hello Hima,

This way of migration is neither recommended nor supported by SAP.

It is not possible to retrieve the correct project structure. In addition the embed EP application do use the SAP Component Model, which you need to ensure you have implemented in the project structure and the deployment descriptor.

All of this, you have ready to use when you implement this migration with NWDI. SAP can not provide you any directions on how-to do that without NWDI. I have been told that it is possible to make a migration without NWDI - f.e. with Jenkins, Maven and Git Repository. However, you need to find out how to implement this migration without NWDI.

Regards,

[Former Member · Accepted solution]

Thank you Milen,

Yes, I am in the process of figuring out. But thought if anyone already done this kind of migration, could get somehelp.

Also we have started looking into the options of migrating to Webdynpro ABAP.

Thanks

Hima

[former_member189220 · Accepted solution]

Hello Hima,

I was told, by the ESS/MSS experts, that WebDynpro ABAP ESS/MSS is a more advanced product comparing to its counterpart of WebDynpro Java.

However, migration of MSS WebDynpro Java to MSS WebDynpro ABAP is not possible (in the real sense of the term "migration"). MSS Web Dynpro Java and MSS Web Dynpro ABAP are too completely different products. These products have different database structure, different application logic and even different UI. SAP has not provided to customers a standard migration procedure. There is no tool/product/feature for this.

This means, this "migrating to Webdynpro ABAP" process is actually a whole new project. In case you need to migrate only your data, then it is easier. In case you need to migrate a customization - it is a "little" bit more complicated.

It is necessary to be involved database expert(s), MSS WebDynpro Java expert(s), MSS WebDynpro ABAP expert(s) and most probably would be good there to be a Project Manager to supervise the process.

In the process, the database structure of both applications has to be "mapped" - the data of which schema.table.column to which data of schema.table.column corresponds. Most probably this will require to process the data itself because the database is entirely different. Then the data itself has to be "transitioned" (moved) from the database of "MSS WebDynpro Java" to the database of "MSS WebDynpro ABAP". Then the WebDynpro Java customizations have to be written again ("from scratch"), but on the ABAP programming language. After all this is done, it is necessary this to be tested. In case of errors, fixed and so on till this new product is ready to be used by the end user.

All in all, this is rather, a creation of new database and application, than a migration.

Regards,