WebserviceTimestampMBean (Java API Reference for Oracle WebLogic Server)

Class

Use

Tree

Help

Oracle Fusion Middleware
Java API Reference for Oracle WebLogic Server
12c (12.2.1)

Part Number E55141-01
P4 Change 1723563 on 2015/10/09

PREV CLASS NEXT CLASS

FRAMES NO FRAMES

SUMMARY: NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

weblogic.management.configuration
Interface WebserviceTimestampMBean

All Superinterfaces:: ConfigurationMBean, DescriptorBean, DynamicMBean, MBeanRegistration, NotificationBroadcaster, SettableBean, WebLogicMBean

public interface WebserviceTimestampMBean

extends ConfigurationMBean

Encapsulates the timestamp information that is associated with a Web Service security configuration.

Since:: 9.0.0.0

Field Summary

Fields inherited from interface weblogic.management.configuration.ConfigurationMBean
`DEFAULT_EMPTY_BYTE_ARRAY`

Method Summary
`abstract long`	`getClockSkew()` If clocks are synchronized, this attribute describes the accuracy of the synchronization between two clocks: the client and the server.
`abstract long`	`getMaxProcessingDelay()` Specifies the freshness policy for received messages: the Web Service observes the processing delay by subtracting the Created time in the Timestamp from the current time.
`abstract int`	`getValidityPeriod()` Represents the length of time the sender wants the outbound message to be valid.
`abstract boolean`	`isClockSynchronized()` Specifies whether the Web Service assumes synchronized clocks.
`abstract void`	`setClockSkew(long clockSkew)` Sets the value of the ClockSkew attribute.
`abstract void`	`setClockSynchronized(boolean b)` Sets the value of the ClockSynchronized attribute.
`abstract void`	`setMaxProcessingDelay(long maxProcessingDelay)` Sets the value of the maxProcessingDelay attribute.
`abstract void`	`setValidityPeriod(int validityPeriod)` Sets the value of the ValidityPeriod attribute.

Methods inherited from interface weblogic.management.configuration.ConfigurationMBean
`freezeCurrentValue, getId, getInheritedProperties, getName, getNotes, isDynamicallyCreated, isInherited, isSet, restoreDefaultValue, setComments, setDefaultedMBean, setName, setNotes, setPersistenceEnabled, unSet`

Methods inherited from interface weblogic.management.WebLogicMBean
`getMBeanInfo, getObjectName, getParent, getType, isCachingDisabled, isRegistered, setParent`

Methods inherited from interface javax.management.DynamicMBean
`getAttribute, getAttributes, invoke, setAttribute, setAttributes`

Methods inherited from interface javax.management.MBeanRegistration
`postDeregister, postRegister, preDeregister, preRegister`

Methods inherited from interface javax.management.NotificationBroadcaster
`addNotificationListener, getNotificationInfo, removeNotificationListener`

Methods inherited from interface weblogic.descriptor.DescriptorBean
`addPropertyChangeListener, createChildCopyIncludingObsolete, getParentBean, isEditable, removePropertyChangeListener`

Method Detail

setClockSynchronized

void setClockSynchronized(boolean b)

Sets the value of the ClockSynchronized attribute.

Parameters:: b - synchronize clock or not

isClockSynchronized

boolean isClockSynchronized()

Specifies whether the Web Service assumes synchronized clocks.

If the clockSynchronized attribute is false, the Web Service rejects all inbound messages with that contain expirations, because this is the only safe way to ensure that the message hasn't already expired. In this case, the Web Service also does not enforce a freshness policy.

If this attribute is set to true, then the Web Service enforces expirations on inbound messages to the best of its ability and enforces an optional freshness policy (via maxProcessingDelay).

The default value of this attribute is true.

setClockSkew

void setClockSkew(long clockSkew)

Sets the value of the ClockSkew attribute.

getClockSkew

long getClockSkew()

If clocks are synchronized, this attribute describes the accuracy of the synchronization between two clocks: the client and the server.

ClockSkew is expressed in milliseconds. Clock skew is enforced by rendering all times into milliseconds since a common time 0 and using these times for comparisons. For example, if your clocks are accurate to within 1 minute of each other, you would set your skew to 1 minute * 60 seconds * 1000 milliseconds or 60000.

setMaxProcessingDelay

void setMaxProcessingDelay(long maxProcessingDelay)

Sets the value of the maxProcessingDelay attribute.

getMaxProcessingDelay

long getMaxProcessingDelay()

Specifies the freshness policy for received messages: the Web Service observes the processing delay by subtracting the Created time in the Timestamp from the current time.

If the observed processing delay is greater than maxProcessingDelay plus clockSkew, then the message is rejected as stale.

This attribute is specified in milliseconds.

Setting maxProcessingDelay to NO_MAX_PROCESSING_DELAY disables to enforcement of the freshness policy.

setValidityPeriod

void setValidityPeriod(int validityPeriod)

Sets the value of the ValidityPeriod attribute.

Parameters:: validityPeriod -

getValidityPeriod

int getValidityPeriod()

Represents the length of time the sender wants the outbound message to be valid.

When the validityPeriod is positive, the TimestampHandler inserts an Expires element into the Timestamp header. The validityPeriod is expressed in seconds: the Expires time will be that many seconds ahead of the Timestamp's Created time.

Overview

Package