Hi,

I’ve recently deployed some web services and I would like to know how to follow and persist their possible raised warnings/errors.

Do you use only the trace servers options accessing the IS admin console, do you use any specific component/product for that need, or did you choose to developp your own component that write data in a database ?

I’m sure ways to do are multiple, but I would be very interested to know your different way to do please.

Regards

Possible options:

— Writing to server.log (via debugLog) or any custom log file (via writeToFile) or sending email alerts for critical errors only
— Storing in DB and having a DSP/UI to show the errors/warnings as part of monitoring
— Writing into webMethods Audit DB (via Enable auditing properties in flow services)

As you wan to follow only specific warnings/errors raised by your webServices, better write them to a separate file which you can use for trouble-shooting or reports to check the count of message per error.

Thanks,

MR as173d, I’m would maybe more interested to write them into a DB… to have both the abbility to look for errors with some SQL… and better direct rapid access…

M@he$h, In your option #2 :
the DB would be an external one (my own schema I create myself), or an internal DB owned by webMethods ?
what do you mean by DSP ? (I only know the DSP in music (Digital Signal Processor) :? )
Do the UI you talking is a part of webMethods or do you suggest to create my own UI (or buy a third-party product) ?

In your option #3 : I’m going to test the Audit option :
so to read information, can you confirm me the UI will be MWS please ?

Regards

#2 – Use external DB tables. DSP is Dynamic server pages supported by wM but this has become old and now you can use CAF or Open CAF which comes with wM product suite.

If you are looking for third party tool you can use life ray (for eg.) or hire some UI developer who are good at HTML, BootStrap, JS and Ajax, JQuery

#3 – Check the services menu under monitoring in MWS

Thanks M@he$h.

In My DEV MyWebMethods: Navigate > Applications > Monitoring > Integration > Services
I see this error :

Connection error of the web service. Please verify the Integration Server parameters in Administration -> My webMethods -> system parameters
Details : java.rmi.RemoteException: HTTP error response: <h4>Access Denied</h4>

I read this link, and verified my CommandCentral Pool was correct (SAML well configured too) :

(In my preproduction and production MWS all is fine)

Am I missing something to correct this error ?

Regards

Hi Cedric,

is the monitor package configured to point to the MWS?

Is the IS configured under MWS → Adminisitration → My webMethods → Servers?

Is the password for Administrator identical on IS and MWS?

Is there a corresponding message in the IS server.log or error log?

Regards,
Holger

Hi Holger,

1- Yes
2- You mean in : MWS → Adminisitration → My webMethods → “” System parameters “” → Servers ?

I see a server but when I clik on the button “…”, I have this warning :
“No Integration server has been configured in the central configuration”
Please see the attached files

3- Yes
4- No corresponding message on the IS

Regards

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/d8345cc9aad70987bf7d320e4b7c372e4c29e386.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/d8345cc9aad70987bf7d320e4b7c372e4c29e386.jpeg 2x" data-dominant-color="CED1D0">

mws_img_servers3.JPG297×660 42.7 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/3af146363cdac0f5b0699a2cf38b083ae71cbabe_2_1035x208.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/3af146363cdac0f5b0699a2cf38b083ae71cbabe.jpeg 2x" data-dominant-color="D2DEE5">

mws_img_servers1.JPG1241×250 54.5 KB

Hi Cedric,

please see under Monitoring (Analyse) → Integration → Services for the Audit Data of services having “Audit Logging” enabled in Designer.

Please check your Monitor Administrators ACL on IS if there is an entry “system/My webMethods Administrators”.

Regard,
Holger

Hi Holger,

When I can’t go in Monitoring (Analyse) → Integration → Services,
I have the same error previous error

Connection error of the web service. Please verify the Integration Server parameters in Administration -> My webMethods -> system parameters 
java.rmi.RemoteException: HTTP error response: <h4>Access Denied</h4>

and Yes, the entry “system/My webMethods Administrators” is allowed for the ACL “Administrator ACL”.

Does the UM server has to be started ?

Regards

Hi Cedric,

you checked for the wrong ACL.

I was referring to “Monitor Administrators ACL”, not “Administrators ACL”.

Is the JDBC Pool for “Central Users” configured to use the same schema than the MWS used for Monitoring itself?

What happens when you try to test the connectivity form the system parametes → servers page?

This does not relate to UM Server.

Regards,
Holger

Oups,
After watching the correct one, yes in “Monitor Administrators ACL”, I have these ones allowed :
local\Administrators
local\MonitorAdministrators
system/My webMethods Administrators

In which menu of MWS do you verify the “Central Users” schema used for monitoring please ?

When I click on menu “My webMethods\system parameters\servers”, all is displayed without any error (please see the picture above).

Ok, for the UM, I just wanted to be sure

Regards

Hi Cedric,

this is in IS Admin UI under Settings → JDBC Pools

In MWS under Administration → My webMethods → Data Sources (DataSource default)

Both locations need to point to the same database and schema.

Regards,
Holger

Hi Holger,

I’ve verified, they point to the same schema :
jdbc:wm:oracle://localhost:1521;serviceName=ESB
and in MWS the defaut datasource is set.

(in DEV, the same machine is used for IS, MWS, and this DB schema)

I’ve tested the connection to the schema in IS and it works.

Regards

Reading the webMethods Monitor User guide, I see for CommandCentral that I have to add the following key/value pair in the IS extended settings :
watt.server.auth.samlResolver=http://mws-host:mws-port /services/SAML

Is it required ?

Regards

Hi Cedric,

yes, this is required as Monitor uses this to check the permissions in MWS.

Regards,
Holger

Holger,

I’m perplex since on our PREPROD environment, Auditing work well without this extended settings.

I can try to add it in the DEV environment, to see if the error persists but I’m surprised comparing the PREPROD.
for my services audited, I’ve took a look in the IS at Logs\Service, and the traces are present and fine (but still not any traces in MWS monitoring)

Regards

Hi Cedric,

please see IntegrationServer Administrators Guide, Chapter 18 (Authenticating Clients) for details.

There is a section about “Accessing Integration Server Data through My webMethods”.

Regards.
Holger

Hi,

Holger I’ve read the manual and configured all like in the instructions… I’m sadly noticing there is nothing to do
It does not work, I have the same issue :

2016-08-16 14:24:34 CEST (wsclient:FATAL)  [RID:40] - com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy: HTTP error response: <h4>Access Denied</h4>
java.rmi.RemoteException: HTTP error response: <h4>Access Denied</h4>

On my PREPROD and PROD environnment all is fine, but on the DEV one, the error still present.
The only difference I see is in DEV they (IS and MWS) are both in the same server.

Any last idea ?

Regards

Hi Cedric,

there must be a difference between DEV and PREPROD/PROD which is causing this.

Hosting the instances on one server or on different servers is not relevant here.

Do the installations have the same Fix-Levels (esp. IS_Portal might be of interest here)?

Regards,
Holger

Holger,

You’re right, it must exist a difference somewhere, but I did not find it.

Last week I’ve updated all environments with the same versions, so the MWSs have all the same :

Version: 9.8.0.4.196
Build Date: 2016-05-21
Correctifs installes : SBPPortal_9.8.0_Fix4,SBPRuntime_9.8.0_Fix4

Regards
Cedric

Hi Cedric,

can you check the acl*.cnf files of the IS instances if there are differences related to the ACL, esp. the Monitor Administrators ACL.

Regards,
Holger