Eai Data Manager Dm_http_read_success Always Returns Success (Doc ID 794563.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.1 [Release 7.3.1]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

-- Problem Statement:
Connecting to any working web server with the plugin_http library of the EAI Data Manager and
having that DM check for success always succeeds, because the DM is looking for "200" in the
return buffer, which always matches the return buffer when a timestamp is included (e.g. year
"2009").

-- Steps To Reproduce:
### Steps to Reproduce ###
1. Load pin_notify_plugin_http to the database, specifically, the line "1301 0
/event/customer/status".

2. Ensure that the "StatusUpdate" business event is configured in the payload of the EAI Java
Service (eai_js) configuration.

3. Install and start up a basic web server supported by BRM, e.g. Tomcat.

4. Configure the EAI DM pin.conf for loglevel 3, plugin_http and the URL of the running web server
above but with a known bad path within the web server, e.g. URL suffix "/brm_listener_not_here".
Set the *read_success flag to 1 as well.

5. Stop and restart services, including cm, dm_eai, and eai_js.

6. Send the following commands through testnap:

r << EOF 1
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 1 0
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service/admin_client 2 0
0 PIN_FLD_PROGRAM_NAME STR [0] "testnap"
0 PIN_FLD_STATUSES ARRAY [1]
1 PIN_FLD_STATUS ENUM [0] 10102
1 PIN_FLD_STATUS_FLAGS INT [0] 0
EOF
xop PCM_OP_CUST_SET_STATUS 0 1
r << EOF 1
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 1 0
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service/admin_client 2 0
0 PIN_FLD_PROGRAM_NAME STR [0] "testnap"
0 PIN_FLD_STATUSES ARRAY [1]
1 PIN_FLD_STATUS ENUM [0] 10100
1 PIN_FLD_STATUS_FLAGS INT [0] 0
EOF
xop PCM_OP_CUST_SET_STATUS 0 1

6. This should generate data in the dm_eai.pinlog similar to the pinlog attached to this SR,
showing the publish buffer and response buffer. In spite of the return code being 404, the DM
accepts the response as a success.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms