We did an upgrade from webMethods 6.0.1 to 6.5
We used in our previous version WmMonitor + custom dsp pages (based on WmMonitor dsp pages), so we had a custom WmMonitor.
When we are trying to see information with our custom WmMonitor pages, we have blank pages and no logs in server logs.
My question is : can we use ‘as is’ our WmMonitor pages (based on 6.0.1 version) or do we need to modify all to be with the new ‘Monitor’ which is My webMethods Portal’
- behind our WmMonitor pages, we have a modeler process.
- With my webMethods portal, we can see our processes, but we need to keep the ‘old’ monitoring due to our customization
Yes you may have to start using MWS portal (aka WmMonitor) to monitor your processess/workflows etc…
Also there should some migration document avail on the Advantage site moving old Monitor to MWS…check it out…
If not make sure your WmMonitor package is enabled in IS65??
I checked, and the WmMonitor package is enabled in IS65.
With MWS portal, I can see my processes, but I need to migrate my custom WmMonitor (because it is used by business users).
So my question are
- : do I need to re-write all ?
- Is it normal that the example I provided give a blank page ?
Is it normal that the example I provided give a blank page ?
Can you elaborate on this?? Is the example you are trying or custom you have already developed??
do I need to re-write all ?
–May be not…
For example, if I use the following url with webMethods 6.5
with d5b7af796354a96711a314230a8 which is an existing processID
I have a blank page
Thanks by advance
Do you see any errors in the logs?? It should work the same as in 601 with WmMonitor.could be a configuration tweak…Did you test the ProcessAudit jdbcpool and PRT tables with this PID??
I see no error in logs, it is my problem.
I didn’t perform test with this PID. Do you mean test directly with the developer and a particular flow service ?
Thanks again for your quick answer
Yes can you test that PID thru WmPRT services??
I did a comparison between the WmMonitor package in 6.0.1 and 6.5.
It missed all the dsp in the new WmMonitor. Do we need to copy the WmMonitor folder from 6.0.1 and copy to the 6.5 version ? Is the old version package will work with the new IS ?
Crosscheck the service level info vs both packs…WmMonitor services/pages should be in sync…give it a shot…and backup your WmMonitor65 package.
Once you have the dsp’s in place reload the WmMonitor package or restart IS.
I check the WmMonitor package version 6.5, and it lacks a lot of service in comparison with the version 6.0.1.
Example of service missing in WmMonitor : wm.monitor.process:queryProcessStatus
So, it doesn’t work.
I try to replace the WmMonitor package with the 6.0.1 version, but it doesn’t work neither.
The dsp pages can work if we don’t use a service missing !
Do you have any idea ? Do we need to rewrite all our Monitor by using myWebMethods Portal ?
Do we need to rewrite all our Monitor by using myWebMethods Portal ?–I dont think so…its matter of migration/configuration that might be missing…MWS is not mandatory unless you use Broker stuff then MWS comes into role…
Are you using Modeler/Designer(PRT/ProcessEngine in 6.5/7,x)/Workflow(TaskEngine) both??
Did you contact wM tech support??
We use Modeler + PRT
and WmMonitor custom packages for our monitoring.
We have a webMethods professionnal services consultant who comes on monday to help us