RESTful Edit Management Interface for Oracle WebLogic Server

Modify This Webservice Timestamp

post

/management/weblogic/{version}/edit/webserviceSecurities/{name}/webserviceTimestamp

Modify this webservice timestamp.

Request

Supported Media Types

application/json

Path Parameters

name(required): string

The name property of the instance in the collection.
version(required): string

The version of the WebLogic REST interface.

Header Parameters

X-Requested-By(required): string

The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.

Must contain the modified webservice timestamp model.

Root Schema : Webservice Timestamp

Type: object

Show Source

clockSkew: integer(int64)

Minimum Value: 0

Default Value: 60000

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.
clockSynchronized: boolean

Default Value: true

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.
dynamicallyCreated: boolean

Read Only: true

Default Value: false

Return whether the MBean was created dynamically or is persisted to config.xml
id: integer(int64)

Read Only: true

Return the unique id of this MBean instance
maxProcessingDelay: integer(int64)

Default Value: -1

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.
name: string
Read Only: true
The user-specified name of this MBean instance.
This name is included as one of the key properties in the MBean's javax.management.ObjectName
Name=user-specified-name
Constraints
- legal null
notes: string

Optional information that you can include to describe this configuration.
WebLogic Server saves this note in the domain's configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the xml entity <. Carriage returns/line feeds are preserved.
Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.


            
            
            tags: 
            array  Items
            
            
                
                
Title: Items





















Return all tags on this Configuration MBean


                
            
            
            
            
            type: 
            string
            
                
                


Read Only: true























Returns the type of the MBean.
Constraints
unharvestable




                
            
            
            
            
            validityPeriod: 
            integer(int32)
            
                
                




Minimum Value: 1















Default Value: 60







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.


        {
    "type":"object",
    "properties":{
        "clockSkew":{
            "default":"60000",
            "minimum":"0",
            "type":"integer",
            "format":"int64",
            "description":"<p>If clocks are synchronized, this attribute describes the accuracy of the synchronization between two clocks: the client and the server.</p><p>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. </p>"
        },
        "clockSynchronized":{
            "default":true,
            "type":"boolean",
            "description":"<p>Specifies whether the Web Service assumes synchronized clocks.</p><p>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.</p><p>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).</p><p>The default value of this attribute is true.</p>"
        },
        "dynamicallyCreated":{
            "readOnly":true,
            "default":false,
            "type":"boolean",
            "description":"<p>Return whether the MBean was created dynamically or is persisted to config.xml</p>"
        },
        "id":{
            "readOnly":true,
            "type":"integer",
            "format":"int64",
            "description":"<p>Return the unique id of this MBean instance</p>"
        },
        "maxProcessingDelay":{
            "default":"-1",
            "type":"integer",
            "format":"int64",
            "description":"<p>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.</p><p>If the observed processing delay is greater than maxProcessingDelay plus clockSkew, then the message is  rejected as stale.</p><p>This attribute is specified in milliseconds.</p><p>Setting maxProcessingDelay to NO_MAX_PROCESSING_DELAY disables to enforcement of the freshness policy.</p>"
        },
        "name":{
            "readOnly":true,
            "x-weblogic-legalNull":true,
            "type":"string",
            "description":"<p>The user-specified name of this MBean instance.</p><p>This name is included as one of the key properties in the MBean's <code>javax.management.ObjectName</code></p><p><code>Name=<i>user-specified-name</i></code></p><p><h5>Constraints</h5></p><ul><li>legal null</li></ul>"
        },
        "notes":{
            "type":"string",
            "description":"<p>Optional information that you can include to describe this configuration.</p><p>WebLogic Server saves this note in the domain's configuration file (<code>config.xml</code>) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <code>&lt;</code>. Carriage returns/line feeds are preserved.</p><p>Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.</p>"
        },
        "tags":{
            "title":"Items",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"<p>Return all tags on this Configuration MBean</p>"
        },
        "type":{
            "readOnly":true,
            "x-weblogic-unharvestable":true,
            "type":"string",
            "description":"<p>Returns the type of the MBean.</p><p><h5>Constraints</h5></p><ul><li>unharvestable</li></ul>"
        },
        "validityPeriod":{
            "default":"60",
            "minimum":"1",
            "type":"integer",
            "format":"int32",
            "description":"<p>Represents the length of time the sender wants the outbound message to be valid. </p><p>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.</p>"
        }
    },
    "description":""
}



                
                
    Nested Schema : Items
    
      
      Type: array
    

    

    
    Title: Items
    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    
    Return all tags on this Configuration MBean
    

    

    

    

    
        Show Source
        
            
            
            Array of: 
                string
            
            
                
                





























                
            
            
            
        
        {
    "title":"Items",
    "type":"array",
    "items":{
        "type":"string",
        "description":""
    },
    "description":"<p>Return all tags on this Configuration MBean</p>"
}



                

                

                
                
                Security
                
                    
                        
                        
                        Admin: basic
                        
                        
                            


Type: basic



Description: A user in the Admin security role.

                        
                        
                        
                    
                
                
                
                
                Back to Top

                Response

                



                
                
                200 Response
                
                

                


                
                
                
                

				Back to Top