Service Names are not visible in MWS

Krishna_PB · February 14, 2016, 1:08pm

Hi,

Only few service names are not displaying in MWS after applying the latest fix, Please find the fix details below.

Only service names are missing, it’s blank. Other details are fine.

Application → Monitoring → Integration → Services

8.2.1.0.586
Build Date: 2015-11-12
Installed Fixes: MWS_8.2_SP1_Fix26

Any idea on this.

Krishna_PB · February 14, 2016, 2:38pm

This is happening only when i am tracing the code from SoftwareAg Developer. Any idea on this.

Mahesh_K_Sreenivas · February 14, 2016, 5:58pm

Add screen shots to assist you further.

MR_as173d · February 15, 2016, 9:40am

Please cross check whether its been logging in audit DB or not.

Thanks,

Krishna_PB · February 15, 2016, 10:03am

Please find attached the screen shot. Also Enabled the Audit option for “Always”.

Holger_von_Thomsen · February 15, 2016, 11:11am

Hi Krishna,

which Monitor Fixes are applied to IS and MWS?

Latest I know of are MON_8.2_SP1_Fix21 for Monitor on IS and MON_8.2_SP1_MWS_Fix17 for Monitor UI on MWS.

Regards,
Holger

Krishna_PB · February 15, 2016, 12:42pm

Hi Holger,

Please find the fix details below.

Fix info:

Monitor UI
Monitor MWS 8.2 SP1 Fix 17
My webMethods Server
MWS_8.2_SP1_Fix26
Broker Portal 8.2.3 Fix7
IS_8.2_SP2_Portal_Fix2

Krishna_PB · February 15, 2016, 12:44pm

Also i am seeing some duplicate items in the service list with same context id.
Please find the attached screen shot for your reference.

Holger_von_Thomsen · February 15, 2016, 3:19pm

Hi Krishna,

any messages in server.log or Error Log related to auditing?

Please share the Output of the WmRoot/updates.dsp for the IS Fixes.

The Overview for the MWS Fixes sounds quite up-to-date to me.

Any SCG-Fixes applied (esp. SCG_Audit)?

Regards,
Holger

Krishna_PB · February 15, 2016, 3:29pm

Please find the updated fix list as an attachment.

Also didn’t find any issues in server/error logs.
Updated Devleopment Fix List.txt (2.36 KB)

Holger_von_Thomsen · February 15, 2016, 4:04pm

Hi Krishna,

fix list looks ok so far.

There needs to be some thing weird, which is not currently in the logs.

Can enhance the Logging for “Monitor (Database Layer)” to Trace and try to log again these services (with and without the name being displayed)?
Eventually you missed to update the IS audit schema in the DB to the latest version.

:roll:

Regards,
Holger

Krishna_PB · February 15, 2016, 6:16pm

Thanks Holger.

I have enhanced the logging level. Will let you know if i found some thing.

What is the latest version for IS audit schema? Can you ping me the fix details as i didn’t see any thing in SUM.

Thanks for your support.

MR_as173d · February 15, 2016, 6:28pm

Krishna – Try to replicate the issue in some other environment so that we do understand issue with the fix levels or something else. If needed write to SAG support for assistance.

Thanks,

Krishna_PB · February 16, 2016, 9:12am

I will try to replicate but it’s very difficult to get the similar environment, there are lot of dependencies.
I found some thing that service details are not updating into the database as well,then it’s not with MWS problem, somewhere while sending the parameters to DB from IS.
I have set the service logger destination to File instead of DB, even in this case also same issue.
Any ideas/suggestions?

Thanks

MR_as173d · February 16, 2016, 10:06am

Krishna – Can you please share the snapshots of the service whose details are been auditing in DB and which are not been auditing. It’s very difficult to perform the role until we wear your shoe

Thanks,

Holger_von_Thomsen · February 16, 2016, 11:56am

Hi Krishna,

latest DB schema versions for 8.2.2 are as follows:


<Version productVersion="8.2.2.0">
                <DatabaseComponent componentName="ISCoreAudit" componentVersion="42"/>
                <DatabaseComponent componentName="ISInternal" componentVersion="41"/>
                <DatabaseComponent componentName="ProcessAudit" componentVersion="53"/>
                <DatabaseComponent componentName="DocumentHistory" componentVersion="10"/>
                <DatabaseComponent componentName="CrossReference" componentVersion="11"/>
                <DatabaseComponent componentName="ProcessEngine" componentVersion="63"/>
                <DatabaseComponent componentName="Staging" componentVersion="20"/>
                <DatabaseComponent componentName="Reporting" componentVersion="25"/>
                <DatabaseComponent componentName="OperationManagement" componentVersion="25"/>
                <DatabaseComponent componentName="DistributedLocking" componentVersion="20"/>               
                <DatabaseComponent componentName="Blaze" componentVersion="10"/>
                <DatabaseComponent componentName="MediatorEvents" componentVersion="10"/>
                <DatabaseComponent componentName="BusinessRules" componentVersion="10"/>
</Version>

You can look up the installed versions in the database schema in the table COMPONENT_VERSION or the view INSTALLED_COMPONENT.

In SUM you will only find the Fix for the Database Scripts.

The Schema versions can be found in the DatabaseConfigurator.

Regards,
Holger

Krishna_PB · February 16, 2016, 12:37pm

@Holger,

 I have already installed/updated the below schema in my environment.

```
 Installed Components      *
```

ANL 56 Analysis WEBMDATA,WEBMINDX
ARC 24 Archive null,null
BLZ 10 Blaze WEBMDATA,WEBMINDX
RUL 10 BusinessRules WEBMDATA,WEBMINDX
CCS 20 Central Configuration null,null
XRF 11 CrossReference null,null
DTP 25 Data Purge WEBMDATA,WEBMINDX
DBM 22 Database Management null,null
DSL 20 DistributedLocking null,null
IDR 10 DocumentHistory null,null
ISC 42 ISCoreAudit WEBMDATA,WEBMINDX
ISI 41 ISInternal WEBMDATA,WEBMINDX
MED 10 MediatorEvents WEBMDATA,WEBMINDX
OPM 25 Operation Management WEBMDATA,WEBMINDX
PRA 53 ProcessAudit WEBMDATA,WEBMINDX
PRE 63 ProcessEngine WEBMDATA,WEBMINDX
PTR 46 ProcessTracker WEBMDATA,WEBMINDX
PRP 25 Reporting WEBMDATA,WEBMINDX
PST 20 Staging WEBMDATA,WEBMINDX
TNS 39 TradingNetworks WEBMDATA,WEBMINDX
TNA 38 TradingNetworksArchive WEBMDATA,WEBMINDX

Krishna_PB · February 17, 2016, 12:10pm

I found the reason, issue with IS core fix, When i rollback the IS_core fix it’s working fine.

And also identified the PRT service # pub.prt.log:logActivityMessages ,that is causing this issue.

Any idea about this service. Whether it is deprecated in 8.2 SP2?

Holger_von_Thomsen · February 17, 2016, 12:29pm

Hi Krishna,

no, the service pub.prt.log:logActivityMessages is still a valid one.

You should check for PRT Fixes if this continues to cause problems.

As wM 8.2 is out of support you should consider upgrading to a recent 9.x version.

Regards,
Holger

Krishna_PB · February 17, 2016, 1:17pm

Thanks Holger.

When i rollback the PRT fixes, still it’s causing the same issue.
However I have raised the incident to SAG, Let them verify and come back.

Thanks.