The Debug probe provides step-by-step debugging and state information about documents that flow through a service.
The Debug probe displays the contents of contexts and displays the value of the variables at each processing step of a processing rule. The Debug probe is very useful tool for trouble shoot the issues during the development phase of the service applications.
Usually, probe will be enabled only in development data power appliance.
It is not recommended to enable probe in higher environments but there are some scenarios where we need to debug the issue in higher environments in case of any issues.
Also, developers will not be provided write access to higher environments to enable probe. In this scenario, debug probe utility will help us to enable the probe.
But at least we should have one user write access for enabling probe.
Below are the steps to develop utility to enable probe data power:
- Create user called SOMAUSER for executing SOMA scripts and make sure this SOMAUSER has access to execute the scripts.
- Make sure SOMA interface is enabled from default domain.
3.Create DebugProbe_XMLMGR in any development domain.
4.Create DebugProbe_UserAgent and enter SOMAUSER and password under Basic-Auth Policy. Refer DebugProbe_UserAgent in DebugProbe_XMLMGR under User Agent configuration.
5.Create DebugProbe_HTTPFSH and make sure GET method is enabled.
6.Create SSL Proxy Profile: SOMA_SSL_PP
7.Create Crypto Profile: SOMA_SSL_CP and no need of Identification and Validation credentials.
8.Upload below files to File Management
Application modernization is a growing area of focus for enterprises. If you’re considering this path to cloud adoption, this guide explores considerations for the best approach – cloud native or legacy migration – and more.
a). SomaExecutionDetails.xml : This file has SOMA URL’s and SSL proxy profile details.
b). SOMAFns.xsl : This file has SOMA functions and it will invoke the SomaExecutionDetails.xml to execute the SOMA scripts.
c). GetDomainList.xsl : This file will invoke the SOMAFns.xsl and get the list of domains available in Data power. Create file in temporary:///domain_list.xml.
d). GenerateServiceList.xsl : This file will invoke the SOMAFns.xsl and get the list of services available all the domain. Create file with domain name in temporary:///DEV_list.xml ,default_list.xml
e). EnableProbeUI.xsl : This xsl will create UI to select domain and services to enable the probe by using domain_list.xml and DEV_list.xml ,default_list.xml etc.
f). DisableAllProbes.xsl : This xsl will invoke SOMAFns.xsl and domain_list.xml to disable all the probes.
9.Create Multi-Protocol Gateway : DebugProbe and refer previously created SOMA_SSL_CP, DebugProbe_XMLMGR and DebugProbe_HTTPFSH in MPGW
a) Create Matching Rules: enableprobe and disableprobe
b) Create Processing Rule: DebugProbe_EnableProbe as shown below
This processing rule will enable the probes for the services received in input.
c) Create Processing Rule: DebugProbe_DisableProbe as shown below
This processing rule is scheduled to disable all the probes based timing interval entered in Scheduled Processing Policy.
d) Configure DebugProbe_DisableProbe processing rule under Scheduled Processing Policy in XML manager.
11.Enter URL in browser.
a) Select the domain from drop down and click Submit button.
b) Select the services from drop down and click Submit button.
c) Will get below message once after successful enable probes.
MPGW: MPGW_TESTMQ: 2019-02-02T17:59:40-05:00OK
XMLFW: XMFW_Test: 2019-02-02T17:59:40-05:00OK
d) We can see in data power that probe is enabled for the services submitted in request.
Local files used for development: