WmPRT

Diego_Vescovi · February 10, 2020, 5:58pm

Good evening,
I’m facing a strange issue while trying to dig into logging management but a strange java exception caught my attention:


com.wm.util.BasisException: [BAA.0000.0062] not found in "com.wm.app.prt.audit.schema.ProcessStepRecordType".

After this I looked for WmPRT package, but, surprise surprise, I don’t have it and can’t find it anywhere on local installation.
Is this normal? if so, what can be causing this problem? if not, where can i get this package from? I just can’t do a clean installation at the moment. Hope in your help.

Regards.

Stacktrace here:


472| INFO | jvm 1 | 2020/02/10 16:52:20 | at java.lang.Thread.run(Thread.java:748)
473| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.util.pool.PooledThread.run(PooledThread.java:134)
474| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:411)
475| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:190)
476| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:163)
477| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:120)
478| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
479| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:402)
480| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:444)
481| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:632)
482| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
483| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
484| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:345)
485| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
486| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
487| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
488| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:54)
489| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
490| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:760)
491| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1150)
492| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.lang.flow.FlowState.invoke(FlowState.java:501)
493| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.lang.flow.FlowState.step(FlowState.java:534)
494| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:668)
495| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:267)
496| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:236)
497| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
498| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:402)
499| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:444)
500| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:632)
501| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
502| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
503| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:345)
504| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
505| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
506| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
507| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:54)
508| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
509| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:760)
510| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:411)
511| INFO | jvm 1 | 2020/02/10 16:52:20 | at java.lang.reflect.Method.invoke(Method.java:498)
512| INFO | jvm 1 | 2020/02/10 16:52:20 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
513| INFO | jvm 1 | 2020/02/10 16:52:20 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
514| INFO | jvm 1 | 2020/02/10 16:52:20 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
515| INFO | jvm 1 | 2020/02/10 16:52:20 | at pub.monitor.integrationProcessLogging.createStepInstance(integrationProcessLogging.java:831)
516| INFO | jvm 1 | 2020/02/10 16:52:20 | at pub.monitor.integrationProcessLogging.log(integrationProcessLogging.java:119)
517| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.audit.impl.AuditRuntime.publishAudit(AuditRuntime.java:158)
518| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.audit.impl.AuditRuntime.publishAudit(AuditRuntime.java:177)
519| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.app.audit.impl.AuditRuntime.createRecord(AuditRuntime.java:251)
520| INFO | jvm 1 | 2020/02/10 16:52:20 | at com.wm.util.BasisRuntimeException.<init>(BasisRuntimeException.java:53)
521| INFO | jvm 1 | 2020/02/10 16:52:20 | com.wm.util.BasisException: [BAA.0000.0062] not found in "com.wm.app.prt.audit.schema.ProcessStepRecordType".

Holger_von_Thomsen · February 10, 2020, 6:30pm

Hi Diego,

WmPRT can usually be downloaded and installation as an addition to IntegrationServer, its name should be either “Process Runtime” or “Process Engine” in Installer.

You might want to disconnect the Process Engine and Process audit function in IS Admin UI from their JDBC Pools when you are currently not using Process Model Development on your IS.

Please note that using Process Model Development together with Local Service Development you require a local external database where to store the data into, the embedded database is only supporting the ISInternal function beside very few others, which does not include TN and Process Engine/Process Audit.

See Installation Guide for further informations.

Regards,
Holger

rmg · February 10, 2020, 7:43pm

Hi Diego,

Yes continuing to the above for WmPRT note, if you have or foresee any of your packages dependent on this PRT package then you should consider installing it and configure the pools as required for making to enable of WmPRT package without any loading errors (avoiding partial).

HTH,
RMG

Diego_Vescovi · February 11, 2020, 3:22pm

Thank you for your feedback, i followed your instructions and since this morning I’m digging everywhere but can’t find a way to get nor the package WmPRT itself, neither the Process Runtime or Process Engine in softwareAG installer.
I downloaded the installer once again hoping in a different result but any time I try to install new packages in the installation directory, all the checkboxes are greyed out so I can’t pick any option (as it is supposed to be, having everything installed), but anyway I really don’t see anything related or possibly related to Process Runtime or Process Engine.
I really can’t figure this out.

Thanks again.
You can find, attached to my post, what i’m actually viewing in the installer.

Plus, i’ve noticed that every time i try to interact with a process instance from MWS it pops out this exception


SOAPException( Client: [ISS.0088.9134] Exception occurred while processing the body of the message )

and looking into the forum, i noticed that this should always be related to a problem with the transport due to missing WmPRT package, this is so weird.

Holger_von_Thomsen · February 11, 2020, 4:15pm

Hi Diego,

the SOAP-Exception indicates that there is the Monitor package missing on your IS.

This is a different error than the missing package for the Process Runtime.

As you cannot see these packages in the installer this means, that your account or company is not licensed to use them.
Contact your license manager as well as the Sales Team from SAG to get this fixed.

Regards,
Holger

rmg · February 11, 2020, 6:49pm

Yes you need the WmMonitor package that generally standalone or pre-installs With Task and Process Engine install component list and you should also see the “webMethods Monitor” tree. If you don’t see this then check with your SAG support against your license file and they might be able to point you in the right direction.

How ever I do see in the screen shots under Integration Server tree - Monitor 10.3 (Installed) → Check if this some thing related to the above (WmMonitor) package already installed and configuration to it is pending though?

HTH,
RMG

Holger_von_Thomsen · February 11, 2020, 7:11pm

Hi Diego,

these packages should be listed at the end of your list as independent entries as “webMethods Monitor” and “webMethods Process Engine”.

You will have to configure the WmMonitor package after the installation to point to the MWS instance.
Additionally this one point why the Passwords for the User Administrator in IS and MWS should be the same as this is used for SAML Assetion-based Single-Sign-On. The Monitor package looks up the permissions for the users running in the MWS User Storage.
Therefore make sure that you have configured Central Users Management in IS correctly.

See Monitor Users Guide and IS Administrators Guide for further informations.

Regards,
Holger