I followed the example http://www.saptechnical.com/Tutorials/XI/Adapter/Index.htm but monitor log is see errors (see attached txt) and NWA - JAVA EE applicaion status shows "Failed to start "and I can not find the solution, which may be the problem?

SAP PI 7.11 (java - ABAP)

NWDS 7.3

C 😕 Program Files (x86) / SAP / SAP JVM 6 (i486 61_REL opt) / bin

EJB Development with EJB module version 2.1 (SAP J2EE 1.4 ejb PROYECT)

regards,

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (5)

Hi.

If you are on PI 7.11, you have to use corresponding NWDS 8.10.* version.

Please, check https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/711/NWDS_platform.html to download latest NWDS for PI 7.11

Regards,

Sergey.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi-

I could download the latest version of nwds711, but when wanting to lower the jar package reaches 7%, then no more continuous, there is no way complete as is currently down version nwds730 today.

from already thank you very much for all the help.

Regards,

Diego

Thank you all for the help, I give up, no way to do work.

it says the following url

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e674... but I can not make it work.

Regards,

Diego.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Diego,

I have made 2 adapter modules using that document and it took 3-4 weeks to succeed, step by step progress is what will make you reach to success. I tried opening your code but i couldn't open it.

1. There is always some problem with Jar compatibility and line of code relative to the import statements.

2, Untill unless the AS Java is properly configured you never get successful deployment.

3, After deployment correct module keys and then if ICO works fine, it will work. Try again

Please provide your codes along with import statements once again.

Regards,

Vikas

Hi Vikas

Here you step everything that I have in the project.

Regards,

Diego

Thanks Diego,

Your application-j2ee-engine.xml is missing engine.security.façade

<?xml version="1.0"
encoding="UTF-8" standalone="no"?>

<application-j2ee-engine

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">

<reference

reference-type="hard">

<reference-target

provider-name="sap.com"

target-type="service">engine.security.facade</reference-target>

</reference>

<reference

reference-type="hard">

<reference-target

provider-name="sap.com"

target-type="library">engine.j2ee14.facade</reference-target>

</reference>

<reference

reference-type="hard">

<reference-target

provider-name="sap.com"

target-type="service">com.sap.aii.af.svc.facade</reference-target>

</reference>

<reference

reference-type="hard">

<reference-target

provider-name="sap.com"

target-type="interface">com.sap.aii.af.ifc.facade</reference-target>

</reference>

<reference

reference-type="hard">

<reference-target

provider-name="sap.com"

target-type="library">com.sap.aii.af.lib.facade</reference-target>

</reference>

<reference

reference-type="hard">

<reference-target

provider-name="sap.com"

target-type="library">com.sap.base.technology.facade</reference-target>

</reference>

<reference

reference-type="hard">

<reference-target

provider-name="sap.com"

target-type="library">com.sap.xi.repository</reference-target>

</reference>

<fail-over-enable

mode="disable"

xsi:type="fail-over-enableType_disable"/>

</application-j2ee-engine>

------------------------------

Try this in engine.xml file. And then follow that document steps to create adapter module to deploy.

PS- 1. Do CLEAN n BUILD for EAR and EJB projects rather than just BUILD.

2. You can not delete content of EJBPROJECT->build via NWDS then go to workspace directory-><EJBPROJECT>->build-> classes->com->sap-> and delete all contents except "usermodule" folder/directory.

3. After deleting do not build again and then deploy again and see what happens.

--- > you can also go to window->show view-> deploy view and in that right click on external deployable archives ->Add , then browse your excelparacionEAR folder-> under that there will be excelparacionEAR.ear, select this ear and deploy.

Try it, your code looks fine ( please also tell is there any external file which you need to use like workbook, props, properties file).

Regards,

Vikas

Hi - Regards,

Here you deploy the result of step.

Regards,

Diego

Hi Diego,

I found another post mentioning the same trouble of trying to deploy with NWDS 7.3 on PI 7.11 system:

Here is a link to a PDF that gives all the detailed steps for deploying an adapter module, maybe there is something that was missed?

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e674...

Regards,

Ryan Crosby

S U M M A R Y

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

Successfully deployed: 0

Deployed with warnings: 0

Failed deployments: 1

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

Unexpected exception

1. File:C:\Users\Diego\Documents\SAP\eclipse\workspace\excelseparacionEAR\excelseparacionEAR.ear

NULL

Deploy status:Initial

Version:null

Exception:

com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] P4RuntimeException.

Reason: Unexpected exception

at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:917)

at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)

at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)

at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:278)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:844)

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)

at com.sap.engine.services.dc.cm.deploy.Deployer_Stub.deploy(Deployer_Stub.java:284)

at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:575)

at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:657)

... 4 more

Caused by: java.io.IOException: Ping timeout exceeded while waiting for input from Socket[addr=/10.23.18.15,port=50004,localport=53146]

at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:489)

at java.lang.Thread.run(Thread.java:678)

Hi Diego,

It does indicate a potential network issue with reference to a timeout being exceeded so it's possible you could be making progress since this is a different error than before.

Regards,

Ryan Crosby

Hi-

1- Attempt

when performing the deploy from NWDS me indicates the error should be for the vpn problem.

Error:

Exception:

com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] P4RuntimeException.

Reason: Unexpected exception

2- Attempt

Now the conversion the EAR file to SDA was performed with scripts found within the PI server

Provided archive file is a version deployment. In this case as component already exists – first we need to convert the .ear file to .SDA file then stage that .SDA to /usr/sap/trans/EPS/in . SAP provides scripts to convert the file extension. Deploy using JSPM. Select Hot Fixes as package type during deployment. SAPFreelancing :: Blogs :: Blog Detail</title> <!--[if gte IE 9]> <style type="t...

Error:

1. Warning occurred on server 6300850 during deploy JavaEE/excel

separacionEAR : References Test: There are no matching deploy time references (d

escribed in META-INF/SAP_MANIFEST.MF)

2. Exception has been returned while the [JavaEE/excelseparacion

EAR] was starting. Warning/Exception :[

][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ER

ROR CODE DPL.DS.5029] Exception in operation [startApp] with application [JavaEE

/excelseparacionEAR].]]

How difficult is to launch a module in PI, where you can entrontrar information as JavaBeans works within PI?

Regards,

Diego

Hi-

Here I pass the source code to see if any errors are,txt extension change by zip

Thanks for the contributions.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Diego,

I found this post regarding the same issue you are having now:

Maybe the information here can help you get it deployed and running.

Regards,

Ryan Crosby

Hi-

leave some files:

SDA + log file error (ExcelAdapterSDA.txt - TXT extension change by zip)

images NWDS

Image Error NWA

SAP PI 7.11 (java - ABAP)

NWDS 7.3

If you want you can try the SDA file, has implemented the same code, just to see if it was done was displayed well, but does not work.

It may be that the references are not corrrectas?

References

hard

provider=sap.com

serviceengine.security.facade

hard-

provider-name=sap.com

library-engine.j2ee14.facade

hard-

provider-name=sap.com

service-com.sap.aii.af.svc.facade

hard-

provider-name=sap.com

interface-com.sap.aii.af.ifc.facade

hard-

provider-name=sap.com

library-com.sap.aii.af.lib.facade

hard-

provider-name=sap.com

com.sap.base.technology.facade

What can be the problem?

the NWDS version 7.11 can not get to download

Regards,

Diego

Hi Diego,

The jxl.jar file is missing in your .sda file. Have you deployed that separately because I do not see it included as a library in your archive. The references appear to be correct... I checked from the recent deployment that I have done and I had all the same references. Are you still getting the same error mentioned above about the reference items because that's indicating that the system is trying to find those for deployment when they should already be deployed in the system. If so, then it might be worth trying the deploy using JSPM or the shell script that can be used.

Regards,

Ryan Crosby

hi Regards

Used JSPM and script, but I still have the same problem. Probe with another example without external library and the problem continues.

Regards,

Diego

Hi Diego,

You have two issues at this point. The first thing is getting the external library setup to be deployed inside your .ear/.sda file. The second piece seems to be related to some deployment issue that is probably coming from your NWDS installation. Use this link to find the 7.11 NWDS version and install the SP version that matches your PI system.

NWDS Download

Regards,

Ryan Crosby

your code appears like this. can you please provide your code?

Hi Vikas

the attachment ExcelAdapterSDA.txt.zip (4.7 K) is necessary to eliminate the extension ZIP, then by ZIP reeemplazar txt extension, then unzip

Regards,

Diego

Hi Diego,

Java 5 and above are good to go. This is happening because the adapter module is not deployed properly.

Which tool you used to deploy the Adapter Module?

If you have used NWDS then you must get a successful message saying -

S U M M A R Y

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

Successfully deployed: 1

Deployed with warnings: 0

Failed deployments: 0

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

.........

Please share this information about what tool you used and screen shot of message after deployment finished.

Thanks and Regards,

Vikas

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi-

Initially the deploy from NWDS 7.3 was used, but having problem with the VPN, he began to use the URL according http://sapfreelancing.com/blog/detail/id/1303

Libraries for the first AF used 3.0/7.0

aii_af_mp.jar

aii_af_ms_api.jar

aii_af_trace.jar

aii_af_svc.jar

aii_af_cpa.jar

then changed by Libraries for AF 7.1

com.sap.aii.af.lib.mod.jar

com.sap.aii.af.ms.ifc_api.jar

sap.com ~ tc ~ logging ~ java ~ impl.jar

com.sap.aii.af.svc_api.jar

com.sap.aii.af.cpa.svc_api.jar

for tests with both libraries the status shows "Failed to start"

Thanks and Regards,

Hi Diego,

Did you include any external libraries that are setup to run on Java 6? The error indicates that you have something in there that is set to run on 6 for instance but your PI system JVM is 5.

Regards,

Ryan Crosby

hi - Ryan Crosby

I have an external libreia JXL.jar, I'm going to fix if it is for java 5

Thanks and Regards,

Hi Diego,

I just did a module myself for that and I know most versions were for 1.6 but there was one slightly older version compiled for 1.4 that worked in my scenario. If you use that version then your deployment should be fine and hopefully the older version will still fit your requirement.

Regards,

Ryan Crosby

Generate all went back to the library again if jxl.jar, they used only

used : Java 5.0 (1.5),

then changed by Libraries for AF 7.1

com.sap.aii.af.lib.mod.jar

com.sap.aii.af.ms.ifc_api.jar

sap.com ~ tc ~ logging ~ java ~ impl.jar

com.sap.aii.af.svc_api.jar

com.sap.aii.af.cpa.svc_api.jar

whose files were used Manifest:

Manifest-Version: 1.0

Edition: 711SP10

Created-By: 1.5.0_15-b04 (Sun Microsystems Inc.)

Ant-Version: Apache Ant 1.6.5.

Same error.

file is attached with the error

Hi Diego,

It appears to be a different deployment issue at this point. You are getting a NamingException instead of an UnsupportedClassVersionError that you had earlier. You are further along in your processing but it's complaining about something with respect to the JNDI name that you have given in your application EAR file. Once you are able to resolve this problem then most likely your adapter module will be set to go...

Regards,

Ryan Crosby

to perform the deploy, I then display the following:

sdu id: [JavaEE_excelseparacionEAR]

sdu file path: [P:\usr\sap\PPD\DVE\j2ee\cluster\server0\temp\tc~bl~deploy_

controller\archives\126\183555951860990\excelseparacionEAR.sda]

version status: [NEW]

deployment status: [Warning]

description: [

1. Warning occurred on server 6300850 during deploy JavaEE/excel

separacionEAR : References Test: There are no matching deploy time references (d

escribed in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.

com/engine.security.facade, sap.com/engine.j2ee14.facade, sap.com/com.sap.aii.af

.svc.facade, sap.com/com.sap.aii.af.ifc.facade, sap.com/com.sap.aii.af.lib.facad

e, sap.com/com.sap.base.technology.facade] (described in the META-INF/applicatio

n-j2ee-engine.xml)., file: excelseparacionEAR.sda, column 0, line 0, severity: w

arning

2. Exception has been returned while the [JavaEE/excelseparacion

EAR] was starting. Warning/Exception :[

][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ER

ROR CODE DPL.DS.5029] Exception in operation [startApp] with application [JavaEE

/excelseparacionEAR].]]

===== END DEPLOY RESULT =====

===== SUMMARY - DEPLOY RESULT =====

*** --- *** --- *** --- ***

SDA(s) ADMITTED FOR DEPLOYMENT [1]:

- [Success] : [0]

- [Aborted] : [0]

- [Warning] : [1]

- [Skipped] : [0]

- [PrerequisiteViolated] : [0]

- [AlreadyDeployed] : [0]

- [Filtered] : [0]

*** --- *** --- *** --- ***

# LIST OF Warning ITEMS #

* SDA: JavaEE_excelseparacionEAR

===== SUMMARY - END DEPLOY RESULT =====

Bedore reference application-j2ee-engine

<reference
	reference-type="hard">
	<reference-target
		provider-name="sap.com"
		target-type="service">engine.security.facade</reference-target>
</reference>
<reference
	reference-type="hard">
	<reference-target
		provider-name="sap.com"
		target-type="library">engine.j2ee14.facade </reference-target>
</reference>
<reference
	reference-type="hard">
	<reference-target
		provider-name="sap.com"
		target-type="service">com.sap.aii.af.svc.facade</reference-target>
</reference>
<reference
	reference-type="hard">
	<reference-target
		provider-name="sap.com"
		target-type="interface">com.sap.aii.af.ifc.facade</reference-target>
</reference>
<reference
	reference-type="hard">
	<reference-target
		provider-name="sap.com"
		target-type="library">com.sap.aii.af.lib.facade</reference-target>
</reference>
<reference
	reference-type="hard">
	<reference-target
		provider-name="sap.com"
		target-type="library">com.sap.base.technology.facade</reference-target>
</reference>

change refence application-j2ee-engine for :

<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="library">com.sap.aii.af.lib</reference-target>
</reference>
<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="service">com.sap.aii.adapter.xi.svc</reference-target>
</reference>
<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="service">com.sap.aii.af.svc</reference-target>
</reference>
<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="service">com.sap.aii.af.cpa.svc</reference-target>
</reference>

Deploy SDA:

If there is an offline deployment, Telnet connection to host may be lost, but th

e result can be seen using [get_result] command

Processing deployment operation, wait...

===== PROGRESS START =====

com.sap.engine.services.dc.cm.deploy.AllItemsAlreadyDeployedValidationException:

[ERROR CODE DPL.DC.3456] All batch items are marked as AlreadyDeployed because

of Version check.

===== DEPLOY RESULT =====

sdu id: [JavaEE_excelseparacionEAR]

sdu file path: [E:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0\temp\tc~bl~deploy_

controller\archives\128\186177714476071\excelseparacionEAR.sda]

version status: [SAME]

deployment status: [AlreadyDeployed]

description: [

1. Already deployed component has version:1

2. Already deployed component has version:1]

===== END DEPLOY RESULT =====

===== SUMMARY - DEPLOY RESULT =====

*** --- *** --- *** --- ***

SDA(s) ADMITTED FOR DEPLOYMENT [1]:

- [Success] : [0]

- [Aborted] : [0]

- [Warning] : [0]

- [Skipped] : [0]

- [PrerequisiteViolated] : [0]

- [AlreadyDeployed] : [1]

- [Filtered] : [0]

===== SUMMARY - END DEPLOY RESULT =====

I'm getting closer to the solution, so I think

hi,

go to NWA and delete the already deployed module. And then redeploy it. It must work then and give a successful deployment result.

Things are pretty simple with NWDS, you can configure the network setting also in NWDS and then even if it exists on server NWDS overwrites if it is with same JNDI name.

Regards,

Vikas

to perform the deploy, I then display the following:

sdu id: [JavaEE_excelseparacionEAR]

sdu file path: [P:\usr\sap\PPD\DVE\j2ee\cluster\server0\temp\tc~bl~deploy_

controller\archives\126\183555951860990\excelseparacionEAR.sda]

version status: [NEW]

deployment status: [Warning]

description: [

1. Warning occurred on server 6300850 during deploy JavaEE/excel

separacionEAR : References Test: There are no matching deploy time references (d

escribed in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.

com/engine.security.facade, sap.com/engine.j2ee14.facade, sap.com/com.sap.aii.af

.svc.facade, sap.com/com.sap.aii.af.ifc.facade, sap.com/com.sap.aii.af.lib.facad

e, sap.com/com.sap.base.technology.facade] (described in the META-INF/applicatio

n-j2ee-engine.xml)., file: excelseparacionEAR.sda, column 0, line 0, severity: w

arning

2. Exception has been returned while the [JavaEE/excelseparacion

EAR] was starting. Warning/Exception :[

][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ER

ROR CODE DPL.DS.5029] Exception in operation [startApp] with application [JavaEE

/excelseparacionEAR].]]

===== END DEPLOY RESULT =====

===== SUMMARY - DEPLOY RESULT =====

*** --- *** --- *** --- ***

SDA(s) ADMITTED FOR DEPLOYMENT [1]:

- [Success] : [0]

- [Aborted] : [0]

- [Warning] : [1]

- [Skipped] : [0]

- [PrerequisiteViolated] : [0]

- [AlreadyDeployed] : [0]

- [Filtered] : [0]

*** --- *** --- *** --- ***

# LIST OF Warning ITEMS #

* SDA: JavaEE_excelseparacionEAR

===== SUMMARY - END DEPLOY RESULT =====

Hi Deigo,

It may be your java version, as far as I know PI 7.11 should be Java 5.0 (1.5).

Regards,

Mark

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi -mark,

was changed to the Java 5.0 (1.5), but still showing the same mistakes, where I can attack the problem?

Ask a Question

Top Q&A Solution Author

User

Count

SAP PI - develop Adapter Module (Error).

Accepted Solutions (0)

Answers (5)

Answers (5)

1- Attempt

2- Attempt

Re: Are there plans to update the Spring framework...

Vendor Invoice Screen 'Payment' tab screen field '...

I have data like Date, Net, Gross. I want to deriv...

Re: Re Generate Co files and data files

Re: error during install SAP S/4HANA Server 2022