|
Installing WLNG defaults to a development mode installation instead of production mode.
|
|
|
|
There is no OAM method to enable trace for Access Tier servers
|
|
|
|
Changing buffer size property for Trace service erases the trace files content.
|
|
|
|
If you make changes in WS-Security options using the Admin Console, the Console offers to let you store plan.xml in the directory of your choice. But WLS itself only looks for the plan.xml in the default location, so a file saved to other than the default location has no impact on WLS behavior. .
|
|
|
|
When SLAs are updated, only the server where the SLA is updated gets the current settings immediately. The budget service does not push budget configuration changes to slaves on update, so other Network Tier servers keep the old budget settings until the budget service polls for configuration changes.
|
|
|
CR326236/ CR328083/ CR328439/CR306501
|
In some cases of NT failover while running MMS, WAP Push with Delivery Notifications, or Terminal Location traffic, there may be a brief period during which throughput falls to zero and some messages are lost.
|
|
|
|
If you are using the backwards compatible version of the SMS traffic path with SMPP, and you have multiple plug-ins, each of which is set to different limits in the Node SLA, node policy enforcement will not work correctly.
Note: |
This communication service is no longer supported |
|
|
|
|
When there are multiple address fields in a StartCallNotification message, only the SIP URL in the first address field is checked for format.
|
|
|
|
Trying to stop CallNotification with an invalid correlator produces an SVC001 exception instead of the correct SVC002.
|
|
|
|
If an application calls StopSmsNotification with an invalid correlator, an incorrect error message is produced. An SVC0002 exception is thrown, but the variables field in the response message contains the value of the correlator, not the text "Correlator"
|
|
|
|
If an application calls EndCall with an incorrectly formatted identifier, an incorrect error message is produced. An SVC0001 exception is thrown, with error code SIP000003 instead of an SVC002.
|
|
|
|
If an application calls EndCall with an invalid identifier, no error message is produced. An SVC002 should be thrown.
|
|
|
|
If an application calls MakeCall with a charging part defined and the ThirdPartyCall plug-in for SIP has ChargingAllowed set to false, no error message is produced. A POL0008 exception should be thrown.
|
|
|
|
If an application calls StartCallDirectionNotification more than once for a single SIP address, an incorrect error message is produced. An SVC0001 exception is thrown with the error code CN-000001. The correct value would be an SVC0002 exception with a variable field that indicates the SIP address.
Note: |
The decision was that the current implementation is more useful for end user. Marked Works as Designed. |
|
|
|
|
Both SP and Global node SLA contracts are enforced even if the use period falls outside of specified start and end dates.
|
|
|
|
If there are overlapping <override> tags in the SLA, enforcement may choose either tag value.
|
|
|
|
Node/Global policy enforcement throws service exceptions instead of policy exceptions
|
|
|
|
In the Extension Toolkit the Turn On Plug-in Debug option cannot be selected.
|
|
|
|
There is no mechanism for unregistering interfaces for a ManagedPlugin instance. New objects that are registered are simply appended to the existing list.
|
|
|
|
The alarm page of the Management Console does not limit the number of alarms displayed. In a situation where many alarms are being emitted, this may cause significant lag times as the page is being rendered.
|
|
|
|
The management operation PolicyArrow symbolreloadServiceProviderXmlDriver does not reload the XSD for the Service Provider SLAs.
|
|
|
|
Management operation SLEEArrow symbolgetFreeDiskSpace does not return the correct value. A NumberFormatException Exception is thrown.
|
|
|
|
Application sessions expire one minute early. If LoginTicket Lifetime (session) check is enabled, the time-out value expires one minute earlier than expected.
|
|
|
|
In the SMPP plug-in for SMS, the methods getReceivedSms and getSmsDeliveryStatus produce events, but these are not described in the edr.xml file. This means that the event will not be classified, and will appear to listeners as "Unknown." As a result, it is impossible to have these events trigger CDRs.
|
|
|
|
Network Gatekeeper cannot process MMSes without attachments, as, for example, an MMS that is sent with a subject but no content. If a SOAP attachment is NULL, SVC0001 is thrown to the application and NullPointerExceptions are logged in Network Gatekeeper
|
|
|
|
If an application calls SendSms with no destination address specified, an incorrect error message is produced. An SVC0001 exception is thrown, but the variables field in the response message reads: "No plug-in available for type: interface com.bea.wlcp.wlng.px21.plugin.SendSmsPlugin".
|
|
|
|
Service Level Agreements fail to load if there are space characters prior to the <?xml> tag.
|
|
|
|
Alarms are not generated in certain circumstances: for Node/Global policy enforcement, when Node SLA limit for application-initiated traffic is reached
|
|
|
|
If you use the Eclipse plug-in to generate a communication serviceskeleton, the GUI does not give you the option of naming the Administration Server anything but AdminServer. Also using the plug-in GUI you cannot specify t3 as the protocol for the WLS administration URL.
|
|
|