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.

setClockSynchronized

void setClockSynchronized(boolean b)

Sets the value of the ClockSynchronized attribute.

Parameters:

b - synchronize clock or not

Default Value:

true

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.

Default Value:

true

setClockPrecision

void setClockPrecision(long clockPrecision)

Sets the value of the ClockPrecision attribute.

Default Value:

60000

Minimum Value:

1

getClockPrecision

long getClockPrecision()

DEPRECATED -- Use set/getClockSkew() -- If both ClockSkew and ClockPrecision are defined, then ClockSkew takes precedence and is used.

If clocks are synchronized, this attribute describes the accuracy of the synchronization.

Default Value:

60000

Minimum Value:

1

setClockSkew

void setClockSkew(long clockSkew)

Sets the value of the ClockSkew attribute.

Default Value:

60000

Minimum Value:

0

getClockSkew

long getClockSkew()

ClockSkew takes precedence over ClockPrecision if both are defined, as ClockPrecision has been DEPRECATED.

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 you're clocks are accurate to within 1 minute of each other, you would set your skew to 1 minute * 60 seconds * 1000 milliseconds or 60000.

Default Value:

60000

Minimum Value:

0

setLaxPrecision

void setLaxPrecision(boolean b)

Sets the value of the LaxPrecision attribute.

Default Value:

false

isLaxPrecision

boolean isLaxPrecision()

DEPRECATED.

Default Value:

false

setMaxProcessingDelay

void setMaxProcessingDelay(long maxProcessingDelay)

Sets the value of the maxProcessingDelay attribute.

Default Value:

-1

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.

Default Value:

-1

setValidityPeriod

void setValidityPeriod(int validityPeriod)

Sets the value of the ValidityPeriod attribute.

Parameters:

validityPeriod -

Default Value:

60

Minimum Value:

1

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.

Default Value:

60

Minimum Value:

1