cancel
Showing results for 
Search instead for 
Did you mean: 

Compatibility problem deploying BPM

0 Kudos

Hello.

I am experiencing problems deploying a BPM DC in my SAP PO system.

Landscape es NW 7.4 SP08 - JVM 1.6.0_81, no transport system for PO, so I am deploying through the deployment perspective in NWDS.

I have tried with several NWDS versions and JDK 1.6.0_31:

  • 7.31 sp03.0000
  • 7.31 sp07.0014
  • 7.31 sp08.0013
  • 7.31 sp13.0000
  • 7.31 sp16.0001
  • 7.31 sp17.0008

With all of them I keep getting the following error:


Description:

        1. java.io.IOException: Could not instantiate network [MyDevelepmentComponet].

The given process model was built with a NWDS or development track of a higher version than the target runtime. Revision number of built process model: 4.7. Revision number of process runtime: 4.6. Please refer to SAP note 1600131 for details.

Exception:

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

Reason: ASJ.dpl_dc.001085 Operation [deploy] of [MyDevelepmentComponet] failed.

What can I do? Could it be roles?

Thanks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Finally deployed the component successfully.

Seems it was a bug in my laptop caused by a recent installation of Microsoft SQL Server 2014 x64.

Had to build a new clean development environment in a virtual machine, with Windows XP, JDK 1.6.21, and NWDS 7.31 SP13 P0000.

Thanks anyway.

Answers (1)

Answers (1)

former_member186851
Active Contributor
0 Kudos

Hello Juan,

check the below link and PI version ,use the correct NWDS accordingly

Stop using the wrong NWDS version! © - Hav... | SCN

0 Kudos

Hi.

Accordingly to the link you posted, the correct version of NWDS for my landscape is 7.31 sp13.0000, which I already used and got the error.

Do you think it could be a local java runtime issue? As I mentioned before, I'm using JDK 1.6.31.

former_member186851
Active Contributor
0 Kudos

Hello Juan,

Try with lower version of NWDS once and also JDK could be another reason. Check what is in PI and install JDK accordingly.

0 Kudos

Already did that as you can read in the post and first reply. I'm now using JDK 1.6.45. Not working.

Something is making the runtime built number to remain as 4.7 and I don't know how to avoid this.

Also I don't know how this validation works to see if there is some kind of workaround, I explored the generated SDA file looking for this number but couldn't find it.

former_member186851
Active Contributor
0 Kudos

Hello Juan,

In NWDS,Try changing the JDK version as per PI and complier in the below options(highlighted in yellow).