com.sap.portal.navigation.masthead.par from Portal 7.0 to 7.30 deployment

[Former Member]

Hi all,

I must to deploy the "com.sap.portal.navigation.masthead.par" from Portal 7.0 to Portal 7.30

I'm doing the following steps:

- Convert .par to .ear

- Import .ear to NWDS 7.30

- Deployment perspective > Import > File System > com.sap.portal.navigation.masthead.ear > Start

Results log:

S U M M A R Y

~~~~~~~~~~~~~~~~~~~

Successfully deployed: 0

Deployed with warnings: 0

Failed deployments: 1

~~~~~~~~~~~~~~~~~~~

[ERROR CODE DPL.DCAPI.1031] AllItemsAlreadyDeployedValidationException.

Reason: ASJ.dpl_dc.003456 All batch items are marked as AlreadyDeployed because of Version check.

1. File:D:\Documents and Settings\corellavpd\Escritorio\com.sap.portal.navigation.masthead.ear

+ Name:com.sap.portal.navigation.masthead+

+ Vendor:sap.com+

+ Location:SAP AG+

+ Version:1+

+ Deploy status:AlreadyDeployed+

+ Version:LOWER+

+ Description:+

+ 1. Already deployed component has version:7.3005.20110929162215.0000+

(...)

How can I deploy in Portal 7.30 an older version of "com.sap.portal.navigation.masthead.par" ?

Thx!

M.

Edited by: ALL NEW Arinso on Nov 17, 2011 12:54 PM

[detlev_beutner · Accepted solution]

Hi María,

Within the "Deployment Perspective", you have a section "Settings" (folded, at the bottom of the "Deployment Job" tab).

Unfold it and change the "Deployment Strategy" to "Update deployed archives with any version". (It's just like the corresponding setting in SDM).

Hope it helps

Detlev

PS: I would do the conversation otherwise - import the old PAR (with sources) into 7.3, then check if it compiles against 7.3 libs, then create the EAR out of it and deploy it).

[Former Member · Accepted solution]

Hello Detlev,

Yes, I changed the Deployment Strategy and I could deploy the .ear file... but after that the head page gives me an error and I restored the original one.

Then, I'm following your steps:

- import the old PAR (with sources) into 7.3 >>> OK, I downloaded PAR file from Portal 7.0, and I did an Import from local machine.

- check if it compiles against 7.3 libs >>> How can I do it??

In WD Java app in the context menu I have "Deploy" option, and I can see the app into "Deployment" perspective; but I can't see the imported PAR file into "Deployment" perspective and I have no option in context menu to deploy...

Anyway, the .jsp files gives me a lot of errors inside NWDS... I think all of them by the "page import" libraries...

Any help...

Thx!!

Miguel Angel.

[Former Member · Accepted solution]

I guess I should follow this link: http://help.sap.com/saphelp_nw73/helpdata/en/49/db96bf5dba551de10000000a42189c/frameset.htm

After the Export to EAR file, I can see it into Deployment perspective:

Import > Workspace > ...

But my question is... if the .ear file is created, it means everything is ok? Because the .jsp files has errors and, like I said before, deploying directly the .ear file (from the converted .par file) gives me as a result an error in the header of the portal page...

Thanks!

M.

[detlev_beutner · Accepted solution]

Hi Miguel Angel,

In the "Enterprise Portal Perspective", you should have the "Create Portal Archive (EAR File)" icon in the toolbar (if this is not by default, activate the "Enterprise Portal Project Actions" via "Customize Perspective". That way you build the EAR and that way the project appears under the deployable projects in the deployment perspective.

> check if it compiles against 7.3 libs >>> How can I do it??

You compile your sources against some libs (Java standard). If you develop against the portal, you always need the libs you compile against. So with 7.3, the JARs coming with 7.3. This should be near "trivial" if you know what you do This is really really extreme basic knowledge; anyhow, it is a bit different than with 7.0, as the portal applications are not longer deployed as portal applications, but as J2EE applications, so the JARs are a bit distributed... I will publish a blog about such things in a few weeks, but if you have the same experience in 7.0, you should know what you need....?!

(Of course, only JSPs are not compiled at development time, but I hope your Java knowledge goes behind...)

Best regards

Detlev

[detlev_beutner · Accepted solution]

> Because the .jsp files has errors and, like I said before,

> deploying directly the .ear file (from the converted .par file)

> gives me as a result an error in the header of the portal page

As just written: JSPs are not compiled during development time. So go and check the default trace for the error and it's details...

[Former Member · Accepted solution]

Hi Detlev,

Thanks so much for your reply. Regarding "Create Portal Archive (EAR File)" everything is understood, thanks! In NWDS 7.3 everything must be deployed via .ear file

Regarding the libs... yes, of course I know I compile the sources against some libs Then, I'm gonna type it an example:

- NWDS 7.0 > import com.sap.portal.navigation.masthead.par

Everything is ok and working. Now, the same in 7.3:

- NWDS 7.30 > import com.sap.portal.navigation.masthead.par > LogInRedirect.jsp > exactly the same code as NWDS 7.0 (of course), but with errors in lines:

<%@ page import = "com.sapportals.portal.navigation.*" %> >>> The import com.sapportals.portal.navigation cannot be resolved

<%@ page import = "com.sapportals.portal.prt.runtime.PortalRuntime" %> >>> this is resolved correctly into SAP_EP\resources\prtapi.jar

I understand I must to add the corresponding libs for "com.sapportals.portal.navigation.*" to be used... but how I could know which one and where is located? I hope I'm explaining myself clear...

Thx!!

M.

Edited by: All NorthgateArinso on Nov 23, 2011 4:47 PM

[detlev_beutner · Accepted solution]

Hi Miguel,

> how I could know which one and where is located?

Use ClassLocator, see for further details. The latest version of ClassLocator works with NWDS 7.3, but has some minor disadvantages, the biggest is it does not take JARs into account with a "~" in it's name. So if ClassLocator does not bring up the classes you are looking for, you have to do a manual search (using WinRAR for example) or use JarClassFinder (not the best tool in the world) or repair ClassLocator (best approach ).

Hope it helps

Detlev

[Former Member · Accepted solution]

Hi Detlev,

Mmmm... it seems there's not at all too much code compatibility between 7.0 and 7.3... a lot of missing libs references into my WD Java & Portal Apps... so I'll need to make a deep search of all of the missing libraries...

Thanks so so much for the reply!

Miguel Angel.