XPI Inspector deployment fails using SUM on PI 7.4 SP7 AEX

[JaySchwendemann]

Hi all,

header says it all. We are on PI 7.4 SP7 AEX and try to deploy the (hopefully current) xpi_inspector_ear.ear  (version 2014.11.25.16.16.14) and the SUM 10 SP 12 Patchlevel 0.

However, no luck. We got the following error within SUM in Step 5.3 (Configuration) and referred Target Version Report

We know about the Knowledge Base Article http://service.sap.com/sap/support/notes/2010715 but we are not complete confident about deploying via telnet as we always think of this as a last resort. Shouldn't this be working out of the box using SUM?

Any thoughts on this. Did we miss something?

Many thanks and kind regards

Jens

[JaySchwendemann · Accepted solution]

SAP finally stated to my call that using TELNET is the supposed  way of newly installing XPI Inspector. They also promised to further clarify KB http://service.sap.com/sap/support/notes/2010715

[former_member184720]

I did this several times using NWDS on different platforms and never faced any issues.

May be you can give a try with NWDS deployment perspective..

[JaySchwendemann]

Hi all,

Former Member

thanks for the input, will try with Basis if this works (confident it will).

@All:

After digging into some more notes I'm beginning to think that behavior of SUP might be a bug.

This note states that SUM automatically converts an EAR file to an SDA and SUM would be the preferred way for deployment of SDA files. http://service.sap.com/sap/support/notes/1715441

However, this one http://service.sap.com/sap/support/notes/1641062 which is linked from 1715441 suggests one should (manually) wrap the SDA into an SCA because only SCA files can be deployed from scratch via SUM. Update of SDA files would be possible

I think if this is a limitation of SUM not to be able to deploy ear files, it should be either fixed by SAP (preferred of course) or clearly addressed as such in the respective notes, even the best within the central XPI Inspector note http://service.sap.com/sap/support/notes/1514898

I'm going to open a call on this as I think one should be able to deploy SAP delivered components such as XPI Inspector withouth having to deal with SDAs or SCAs or whether there's already a deployed version of the XPI Inspector.

I'll keep you posted on this matter.

Cheers

Jens

[Former Member]

HI Jens,

I am facing the similar issue.

Can you please post the solution if you are able to reslove this.

Thanks

Hari.

[JaySchwendemann]

Hi Hari,

unfortunately SAP didn't provide a solution as of now. The call is still open but I think what's gonna happen is that they revise KB http://service.sap.com/sap/support/notes/2010715 which has a poor style in wording and structure.

However, there will not be any change in functionality, I'm afraid. SUM stays put in not allowing deployment of fresh .ear files which in my opinion is the main pain point.

We did overcome this by deploying XPI Inspector via telnet as described in above mentioned KB following the paragraph named "Telnet - Deploy and Undeploy the XPI Inspector"

HTH, Cheers

Jens

---EDIT----

You might consider opening a call for this matter also. The more customer attention is brought about this limitation of SUM, the more likely a future fix will be (though I must admit it's probably not overly likely to happen very soon). Component I opened the call with was BC-UPG-TLS-TLJ but SAP changed that later on to BC-XI-CON-AFW.

[Former Member]

Hi Jens,

try to use NWDS.

Window->Preferences->SAP AS Java-> add  (and make the new system default) > add Hostname and instance number  after that go to

Window->Show View->Other..->Deploy View

Click External Deployable Archives

Then Add Element from the menu above.(+)

Then choose your ".sda"

Make sure Update Strategy is "Update deployed archives with any version"

Then click "Deploy" from the menu.

[JaySchwendemann]

Thanks Peter for elaborating on deployment option via NWDS. I did not try this but sure will come handy for someone who will have a look at this thread.

As already mentioned, we worked around this issue by using telnet deployment. I will however leave this thread as unanswered until SAP posts back with an answer to my pending call.

Cheers

Jens

[Former Member]

Hi Jens,

Thanks for your quick reply.

Thanks

Hari.