Adapter configuration (PUT)

Sets the user configuration of a specific adapter.

Description

This transaction can run synchronously or asynchronously. If the transaction is processed asynchronously, the REST service returns before the transaction is completed. In this case, you can query the transaction result later by using the transaction REST service.

Roles

Users in the following roles are authorized to perform this operation:

mfpadmin
mfpdeployer
mfpoperator

Method

PUT

Path

/management-apis/2.0/runtimes/runtime-name/adapters/adapter-name/config

Example

https://www.example.com/mfpadmin/management-apis/2.0/runtimes/myruntime/adapters/myadapter/config?async=false&locale=de_DE

Path Parameters

runtime-name: The name of the runtime. This is the context root of the runtime web application, without the leading slash.
adapter-name: The name of the adapter.

Query Parameters

Query parameters are optional.

async: Whether the transaction is processed synchronously or asynchronously. The allowed values are true and false. The default mode is synchronous processing.
locale: The locale used for error messages.

Consumes

application/json, application/xml, text/xml

Produces

application/json, application/xml, text/xml

Payload

JSON Example

{
  "adapter" : "myAdapter",
  "connectivity" : {
    "http" : {
      "connectionTimeoutInMilliseconds" : 30000,
      "cookiePolicy" : "BEST_MATCH",
      "dtdvalidationEnabled" : false,
      "maxConcurrentConnectionsPerNode" : 49,
      "maxRedirects" : 11,
      "port" : 444,
      "protocol" : "http",
      "socketTimeoutInMilliseconds" : 30002
    }
  },
   "properties" : {
  }
}

XML Example

<?xml version="1.0" encoding="UTF-8"?>
<adapterconfig adapter="myAdapter">
  <connectivity>
    <http
      connectionTimeoutInMilliseconds="30000"
      cookiePolicy="BEST_MATCH"
      dtdvalidationEnabled="false"
      maxConcurrentConnectionsPerNode="49"
      maxRedirects="11"
      port="444"
      protocol="http"
      socketTimeoutInMilliseconds="30002"/>
  </connectivity>
  <properties database="test-db"/>
</adapterconfig>

Payload Properties

The payload has the following properties:

adapter: The name of the adapter.
connectivity: The connectivity details
properties: The properties of the adapter, mainly for Java adaers

The connectivity has the following properties:

http: The HTTP connection details

The httpdetails has the following properties:

connectionTimeoutInMilliseconds: The connection timeout value in milliseconds
cookiePolicy: The cookie policy to be used
dtdvalidationEnabled: Whether DTD validation is enabled for syntax and structure of the XML DTD
maxConcurrentConnectionsPerNode: The maximum number of concurrent connections allowed per node
maxRedirects: The maximum number of redirections allowed
port: The port used for the connection
protocol: The HTTP protocol used for connection
socketTimeoutInMilliseconds: The timeout value for socket

The properties has the following properties:

database: The name of the datbase to connect to.

Response

The user configuration of the specified adapter.

JSON Example

{
  "ok" : false,
  "productVersion" : "8.0",
  "transaction" : {
    "appServerId" : "Tomcat",
    "description" : {
      "name" : "myname",
      "type" : "mytype",
    },
    "errors" : [
      {
        "details" : "An internal error occured.",
      },
      ...
    ],
    "id" : 1,
    "project" : {
      "name" : "myproject",
    },
    "status" : "FAILURE",
    "timeCreated" : "2014-04-13T00:18:36.979Z",
    "timeUpdated" : "2014-04-14T00:18:36.979Z",
    "type" : "SET_APPLICATION_ENV_VERSION_ACCESS_RULE",
    "userName" : "demouser",
  },
}

XML Example

<?xml version="1.0" encoding="UTF-8"?>
<set-adapterconfig-result
  ok="false"
  productVersion="8.0">
  <transaction
    appServerId="Tomcat"
    id="1"
    status="FAILURE"
    timeCreated="2014-04-13T00:18:36.979Z"
    timeUpdated="2014-04-14T00:18:36.979Z"
    type="SET_APPLICATION_ENV_VERSION_ACCESS_RULE"
    userName="demouser">
    <description
      name="myname"
      type="mytype"/>
    <errors>
      <error details="An internal error occured."/>
      ...
    </errors>
    <project name="myproject"/>
  </transaction>
</set-adapterconfig-result>

Response Properties

The response has the following properties:

ok: Whether the transaction was successful.
productVersion: The exact product version.
transaction: The details of the transaction.

The transaction has the following properties:

appServerId: The id of the web application server.
description: The details of the application.
errors: The errors occurred during the transaction.
id: The id of the transaction.
project: The current project.
status: The state of the transaction: PENDING, PREPARING, COMMITTING, REJECTING, SUCCESS, FAILURE, CANCELED. Synchronous transactions can have the state SUCCESS and FAILURE. Asynchronous transactions can also have the other states.
timeCreated: The date in ISO 8601 format when the adapter was created.
timeUpdated: The date in ISO 8601 format when the adapter was updated.
type: The type of the transaction, here always SET_APPLICATION_ENV_VERSION_ACCESS_RULE.
userName: The user that initiated the transaction.

The description has the following properties:

contentNames: The optional names of the contained artifacts if multiple artifacts were deployed at once.
filename: The optional file name of the artifact.
name: The name of the artifact.
type: The type of the artifact.

The error has the following properties:

details: The main error message.

The project has the following properties:

name: The name of the project, which is the context root of the runtime.

Errors

400

The payload is invalid.

403

The user is not authorized to call this service.

404

The corresponding runtime or the adapter is not found.

500

An internal error occurred.