Split (1)

train · 94.6k rows

text stringlengths 65 20k
metadataMode=minimal&include Children=true to retrieve a minimal catalog describe with all children resources included.For an example, see Retrieving the Resource Catalog Describe .includeChildren true, false (default) Use to include all available children resources nested within a parent resource describe.You can append includeChildren=true on the describe request.For a resource catalog describe example, see Retrieving the Resource Catalog Describe .showAnnotations true, false (default) To include resource annotations in the catalog describe, you can append showAnnotations=true on the describe request.Note that annotations must be defined by the web application developer and may not be present on the resource.You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.
For an example, see Retrieving the Resource Catalog Describe .includeChildren true, false (default) Use to include all available children resources nested within a parent resource describe.You can append includeChildren=true on the describe request.For a resource catalog describe example, see Retrieving the Resource Catalog Describe .showAnnotations true, false (default) To include resource annotations in the catalog describe, you can append showAnnotations=true on the describe request.Note that annotations must be defined by the web application developer and may not be present on the resource.You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.
includeChildren true, false (default) Use to include all available children resources nested within a parent resource describe.You can append includeChildren=true on the describe request.For a resource catalog describe example, see Retrieving the Resource Catalog Describe .showAnnotations true, false (default) To include resource annotations in the catalog describe, you can append showAnnotations=true on the describe request.Note that annotations must be defined by the web application developer and may not be present on the resource.You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.
You can append includeChildren=true on the describe request.For a resource catalog describe example, see Retrieving the Resource Catalog Describe .showAnnotations true, false (default) To include resource annotations in the catalog describe, you can append showAnnotations=true on the describe request.Note that annotations must be defined by the web application developer and may not be present on the resource.You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.
For a resource catalog describe example, see Retrieving the Resource Catalog Describe .showAnnotations true, false (default) To include resource annotations in the catalog describe, you can append showAnnotations=true on the describe request.Note that annotations must be defined by the web application developer and may not be present on the resource.You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.
showAnnotations true, false (default) To include resource annotations in the catalog describe, you can append showAnnotations=true on the describe request.Note that annotations must be defined by the web application developer and may not be present on the resource.You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.
Note that annotations must be defined by the web application developer and may not be present on the resource.You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.
You cannot use this parameter with ?metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.
metadataMode=list .Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.
Query String Operators Supported by REST API Data Types The following table shows the REST API data types and the valid operators that may be used in query strings with the query ( q) parameter.Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.
Note that the operators BETWEEN, NOT BETWEEN, IN, NOT IN, and the wildcard character % are available only starting in REST API framework version 2.Appendix G GET Method Endpoints G-6Table G-4 Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator integer = (Equal to) .../Department?q=Deptno = 20 <> (Not equal to) .../Department?q=Deptno <> 20 < (Less than) .../Department?q=Deptno < 20 <= (Less than or equal to) .../Department?q=Deptno <= 20 > (Greater than) .../Department?q=Deptno > 30 >= (Greater than or equal to) .../Department?q=Deptno >= 30 BETWEEN (Between) .../Department?q=Deptno BETWEEN 10 AND 30 NOT BETWEEN (Not between) .../Department?q=Deptno NOT BETWEEN 10 and 30 IN (In) .../Department?q=Deptno IN (10, 30) NOT IN (Not in) .../Department?q=Deptno NOT IN (10, 30) IS NULL (Is null) .../Department?q=Deptno IS NULL NOT NULL (Not null) .../Department?q=Deptno NOT NULLAppendix G GET Method Endpoints G-7Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.
Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator number = (Equal to) .../Department?q=Salary = 3120.99 <> (Not equal to) .../Department?q=Salary <> 3120.99 < (Less than) .../Department?q=Salary < 3120.99 <= (Less than or equal to) .../Department?q=Salary <= 3120.99 > (Greater than) .../Department?q=Salary > 3120.99 >= (Greater than or equal to) .../Department?q=Salary >= 3120.99 BETWEEN (Between) .../Department?q=Salary BETWEEN 2000 AND 3120.99 NOT BETWEEN (Not between) .../Department?q=Salary NOT BETWEEN 2000 and 3120.99 IN (In) .../Department?q=Salary IN (800, 3120.99) NOT IN (Not in) .../Department?q=Salary NOT IN (800, 3120.99) IS NULL (Is null) .../Department?q=Salary IS NULL NOT NULL (Not null) .../Department?q=Salary NOT NULLAppendix G GET Method Endpoints G-8Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.
Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator string = (Equal to) .../Department?q=DeptName = SALES <> (Not equal to) .../Department?q=DeptName <> SALES LIKE (Like) .../Department?q=DeptName LIKE SA% .../Department?q=DeptName LIKE %ES .../Department?q=UPPER(DeptName) LIKE UPPER('%e%') NOT LIKE (Not like) .../Departments?q=UPPER(DeptName) NOT LIKE UPPER('%c%') IN (In) .../Departments?q=DeptName IN ('SALES', 'RESEARCH') NOT IN (Not in) .../Departments?q=DeptName NOT IN ('SALES', 'RESEARCH') IS NULL (Is null) .../Department?q=DeptName IS NULL IS NOT NULL (Is not null) .../Department?q=DeptName IS NOT NULL date = (Equal to) .../Employee?q=HireDate = 1999-01-01 <> (Not equal to) .../Employee?q=HireDate <> 1999-01-01 < (Less than) .../Employee?q=HireDate < 1999-01-01 <= (Less than or equal to) .../Employee?q=HireDate <= 1999-01-01 > (Greater than) .../Employee?q=HireDate > 1999-01-01 >= (Greater than or equal to) .../Employee?q=HireDate >= 1999-01-01 BETWEEN (Between) .../Employee?q=HireDate BETWEEN 1999-01-01 AND 2010-01-01 NOT BETWEEN (Not between) .../Employee?q=HireDate NOT BETWEEN 1999-01-01 AND 2010-01-01 IS NULL (Is null) .../Employee?q=HireDate IS NULL NOT NULL (Not null) .../Employee?q=HireDate NOT NULLAppendix G GET Method Endpoints G-9Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.
Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator time = (Equal to) .../Employee?q=HireTime = '08:30:40' <> (Not equal to) .../Employee?q=HireTime <> 08:30:40 < (Less than) .../Employee?q=HireTime < 08:30:40 <= (Less than or equal to) .../Employee?q=HireTime <= 08:30:40 > (Greater than) .../Employee?q=HireTime > 08:30:40 >= (Greater than or equal to) .../Employee?q=HireTime >= 08:30:40 BETWEEN (Between) .../Employee?q=HireTime BETWEEN 04:30:00 AND '08:30:40' NOT BETWEEN (Not between) .../Employee?q=HireTime NOT BETWEEN 04:30:00 AND '08:30:40' IS NULL (Is null) .../Employee?q=HireTime IS NULL NOT NULL (Not null) .../Employee?q=HireTime NOT NULLAppendix G GET Method Endpoints G-10Table G-4 (Cont.)Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.
Operators Supported by Data Types in Query (q) String Parameter REST API Data Type Supported Operator datetime Note: Both UTC and local datetime formats are supported.The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.
The value returned is determined by the time zone configured for the VM.= (Equal to) .../Employee?q=HireDateTime = '1999-01-01T08:30:40Z' <> (Not equal to) .../Employee?q=HireDateTime <> 1999-01-01T08:30:40Z < (Less than) .../Employee?q=HireDateTime < 1999-01-01T08:30:40Z <= (Less than or equal to) .../Employee?q=HireDateTime <= 1999-01-01T08:30:40Z > (Greater than) .../Employee?q=HireDateTime > 1999-01-01T08:30:40Z >= (Greater than or equal to) .../Employee?q=HireDateTime >= 1999-01-01T08:30:40Z BETWEEN (Between) .../Employee?q=HireDateTime BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z NOT BETWEEN (Not between) .../Employee?q=HireDateTime NOT BETWEEN 1999-01-01T08:30:40Z AND 1999-12-01T08:30:40Z IS NULL (Is null) .../Employee?q=HireDateTime IS NULL NOT NULL (Not null) .../Employee?q=HireDateTime NOT NULL boolean = true (true) .../Employees?q=Active = true = false (false) .../Employees?q=Active = false IS NULL (Is null) .../Employees?q=Active IS NULL NOT NULL (Not null) .../Employees?q=Active NOT NULL Media Types Supported Request None ResponseAppendix G GET Method Endpoints G-11application/vnd.oracle.adf.resourcecollection+json : When retrieving a resource collection.application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.
application/vnd.oracle.adf.resourceitem+json : When retrieving a resource item.application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.
application/vnd.oracle.adf.description+json : When describing a resource.Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.
Describe Topics Retrieving the Resource Catalog Describe Retrieving a Resource Describe Task Topics Fetching a Business Object Fetching a Business Object with a Subset of Items Fetching a Business Object Item Paging a Business Object Sorting a Business Object Fetching Data Only for a Business Object Filtering a Business Object with a Query Parameter Returning the Estimated Count of Business Object Items Checking for Data Consistency When Retrieving Business Object Items REST API Framework Version Topics Working with REST API Framework Versions POST Method Endpoints REST APIs support the following tasks using a POST method with the URL as shown.Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.
Create a resource item.<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.
<base_path> /{resourceCollectionPath } Create a parent resource item and create the nested child resource collection in one roundtrip.<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.
<base_path> /{resourceCollectionPath } Update or create a resource item resource item in an existing resource using the Upsert-Mode header.<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.
<base_path> /{resourceCollectionPath } Execute an a batch request.<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.
<base_path> /{version} Request Parameters none Media Types SupportedAppendix G POST Method Endpoints G-12Request application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
application/vnd.oracle.adf.batch+json : When executing a batch request.Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.
Response application/vnd.oracle.adf.resourceitem+json : When creating a resource item.application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.
application/vnd.oracle.adf.resourceitem+json : When updating or creating a resource item using Upsert.application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
application/vnd.oracle.adf.batch+json : When executing an batch request.Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
Task Topics Creating a Business Object Item Creating an Item of a Child Business Object Making Batch Requests PATCH Method Endpoints REST APIs support the following operation using a PATCH method with the URL as shown.Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.
Updating a resource item.<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.
<base_path> /{resourceItemPath } Request Parameters none Media Types Supported Request application/vnd.oracle.adf.resourceitem+json : The resource item to be updated.Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.
Response application/vnd.oracle.adf.resourceitem+json : The updated resource item.Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.
Tasks Topics Updating a Business Object Item DELETE Method Endpoints REST APIs support the following operation using a DELETE method with the URL as shown.Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.
Deleting a resource item.<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
<base_path> /{resourceItemPath } Request Parameters noneAppendix G PATCH Method Endpoints G-13Media Types Supported Request none Response none Task Topics Deleting a Business Object ItemAppendix G DELETE Method Endpoints G-14Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2 F22030-10 November 2023 Oracle Cloud Using the IBM MQ Series JMS Adapter with Oracle Integration Generation 2, F22030-10 Copyright 2019, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.
Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.
Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.
The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.
If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.
As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?
The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.
No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.
This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.
It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.
Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?
Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.
UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.
Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Understand the IBM MQ Series JMS Adapter IBM MQ Series JMS Adapter Capabilities 1-1 IBM MQ Series JMS Adapter Restrictions 1-1 What Application Version Is Supported?1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
1-2 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-2 2 Create an IBM MQ Series JMS Adapter Connection Prerequisites for Creating a Connection 2-1 Create a Connection 2-2 Configure Connection Properties 2-3 Configure Connection Security 2-3 Configure an Agent Group 2-4 Test the Connection 2-4 3 Add the IBM MQ Series JMS Adapter Connection to an Integration Basic Info Page 3-1 Configuration for Queue or Topic Page 3-2 Headers Page 3-3 Summary Page 3-3 4 Implement Common Patterns Using the IBM MQ Series JMS Adapter Put a Message in an Inbound Queue 4-1 iiiUse a Topic to Subscribe to a Message 4-2 5 Troubleshoot the IBM MQ Series JMS Adapter Troubleshoot Connection Errors 5-2 ivPreface This guide describes how to configure this adapter as a connection in an integration in Oracle Integration.Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
Note: The use of this adapter may differ depending on the features you have, or whether your instance was provisioned using Standard or Enterprise edition.These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.
These differences are noted throughout this guide.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.
Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This guide is intended for developers who want to use this adapter in integrations in Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?
Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.
Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.
Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.
Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .
As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and vpartners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.
We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.
Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.
Related Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Using the Oracle Mapper with Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.
italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.
monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Understand the IBM MQ Series JMS Adapter Review the following conceptual topics to learn about the IBM MQ Series JMS Adapter and how to use it as a connection in integrations in Oracle Integration.A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.
A typical workflow of adapter and integration tasks is also provided.Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.
Topics IBM MQ Series JMS Adapter Capabilities IBM MQ Series JMS Adapter Restrictions What Application Version Is Supported?Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.
Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration IBM MQ Series JMS Adapter Capabilities The IBM MQ Series JMS Adapter enables you to create an integration in Oracle Integration.The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.
The IBM MQ Series JMS Adapter provides the following support: Queue manager with or without Username Password Token authentication The Queue manager maintains the queues and ensures that the messages in the queues reach their destination.The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.
The queue manager also performs other functions associated with message queuing.Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?
Inbound and outbound operations Durable subscriptions for topics Headers (standard and custom) Message selector filtering for inbound queue operations Ability to dequeue messages when they are datagram message types.Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.
Only datagram message types are supported.See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .
See IBM MQ Series JMS Adapter Restrictions .The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.
The IBM MQ Series JMS Adapter is one of many predefined adapters included with Oracle Integration.You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.
You can configure the IBM MQ Series JMS Adapter as a trigger or invoke connection in an integration in Oracle Integration.IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.
IBM MQ Series JMS Adapter Restrictions Note the following IBM MQ Series JMS Adapter restrictions in Oracle Integration.The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.
The IBM MQ Series JMS Adapter can only be used with the on-premises connectivity agent.JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.
JSON payloads are not supported.Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.
Only datagram message types are supported.The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .
The following are not supported.SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.
SSL/TLS 1-1MQSeries cluster Request-reply patterns Note: There are overall service limits with Oracle Integration.A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?
A service limit is the quota or allowance set on a resource.See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.
See Service Limits.What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.
What Application Version Is Supported?For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.
For information about which application version is supported by this adapter, see the Connectivity Certification Matrix.See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .
See Connectivity Certification Matrix .Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .Go to Channels > Server Connection Channel > Extended and set Sharing Conversation to 0.
Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .Go to Channels > Server Connection Channel > Extended and set Sharing Conversation to 0.If you want the queue manager to be authenticated, configure support in the Connection authentication field under the Extended tab in MQ Explorer.
This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .Go to Channels > Server Connection Channel > Extended and set Sharing Conversation to 0.If you want the queue manager to be authenticated, configure support in the Connection authentication field under the Extended tab in MQ Explorer.If you use the IBM MQ Series JMS Adapter and do not want the connection to be authenticated, the (MQ Admin) user must provide a valid user ID in Queue Manager > Channels > Server Connection Channel > Properties > MCA .
Step Description More Information 1Access Oracle Integration.Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .Go to Channels > Server Connection Channel > Extended and set Sharing Conversation to 0.If you want the queue manager to be authenticated, configure support in the Connection authentication field under the Extended tab in MQ Explorer.If you use the IBM MQ Series JMS Adapter and do not want the connection to be authenticated, the (MQ Admin) user must provide a valid user ID in Queue Manager > Channels > Server Connection Channel > Properties > MCA .If this user is part of the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p "USERID" +inq However, if the user set in MCA does not belong to the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq +put ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p " USERID " +inq +get +dsp Replace USERID with the user ID and QM with the Queue Manager.
Go to https:// hostname :port_number /ic.2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .Go to Channels > Server Connection Channel > Extended and set Sharing Conversation to 0.If you want the queue manager to be authenticated, configure support in the Connection authentication field under the Extended tab in MQ Explorer.If you use the IBM MQ Series JMS Adapter and do not want the connection to be authenticated, the (MQ Admin) user must provide a valid user ID in Queue Manager > Channels > Server Connection Channel > Properties > MCA .If this user is part of the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p "USERID" +inq However, if the user set in MCA does not belong to the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq +put ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p " USERID " +inq +get +dsp Replace USERID with the user ID and QM with the Queue Manager.Create queues and topics in MQ Explorer that you want the IBM MQ Series JMS Adapter to process.
2Create the adapter connections for the applications you want to integrate.The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .Go to Channels > Server Connection Channel > Extended and set Sharing Conversation to 0.If you want the queue manager to be authenticated, configure support in the Connection authentication field under the Extended tab in MQ Explorer.If you use the IBM MQ Series JMS Adapter and do not want the connection to be authenticated, the (MQ Admin) user must provide a valid user ID in Queue Manager > Channels > Server Connection Channel > Properties > MCA .If this user is part of the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p "USERID" +inq However, if the user set in MCA does not belong to the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq +put ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p " USERID " +inq +get +dsp Replace USERID with the user ID and QM with the Queue Manager.Create queues and topics in MQ Explorer that you want the IBM MQ Series JMS Adapter to process.2-1To use topics, you must run the following command in the MQ_Install /bin/ directory to point to the location of the MQSC file: .runmqsc Queue_Manager < ../java/bin/MQJMS_PSQ.mqsc For example: cd /opt/mqm/bin .runmqsc ICS_QM < ../java/bin/MQJMS_PSQ.mqsc Install the connectivity agent in an on-premises environment.
The connections can be reused in multiple integrations and are typically created by the administrator.Create an IBM MQ Series JMS Adapter Connection 3Create the integration.When you do this, you add trigger (source) and invoke (target) connections to the integration.Create Integrations in Using Integrations in Oracle Integration Generation 2 and Add the IBM MQ Series JMS Adapter Connection to an Integration .4Map data between the trigger connection data structure and the invoke connection data structure.Map Data in Using Integrations in Oracle Integration Generation 2 5(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as gender codes or country codes).Manage Lookups in Using Integrations in Oracle Integration Generation 2 6Activate the integration.Activate Integrations in Using Integrations in Oracle Integration Generation 2Chapter 1 What Application Version Is Supported?1-2Step Description More Information 7Monitor the integration on the dashboard.Monitor Integrations in Using Integrations in Oracle Integration Generation 2 8Track payload fields in messages during runtime.Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 9Manage errors at the integration level, connection level, or specific integration instance level.Manage Errors in Using Integrations in Oracle Integration Generation 2Chapter 1 Workflow to Create and Add an IBM MQ Series JMS Adapter Connection to an Integration 1-32 Create an IBM MQ Series JMS Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.The following topics describe how to define connections.Topics Prerequisites for Creating a Connection Create a Connection Prerequisites for Creating a Connection You must satisfy the following prerequisites to create a connection with the IBM MQ Series JMS Adapter: Configure the MQ Series queue manager for communication in MQ Explorer: Go to Queue Manager > Properties > Communication and set Channel Auto Definition to Disabled .Go to Channels > Server Connection Channel > Extended and set Sharing Conversation to 0.If you want the queue manager to be authenticated, configure support in the Connection authentication field under the Extended tab in MQ Explorer.If you use the IBM MQ Series JMS Adapter and do not want the connection to be authenticated, the (MQ Admin) user must provide a valid user ID in Queue Manager > Channels > Server Connection Channel > Properties > MCA .If this user is part of the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p "USERID" +inq However, if the user set in MCA does not belong to the mqm group, the following profile must be set for the two queues of that Queue Manager: ./setmqaut -m QM -n "SYSTEM.ADMIN.COMMAND.QUEUE" -t q -p " USERID " +inq +put ./setmqaut -m QM -n "SYSTEM.DEFAULT.MODEL.QUEUE" -t q -p " USERID " +inq +get +dsp Replace USERID with the user ID and QM with the Queue Manager.Create queues and topics in MQ Explorer that you want the IBM MQ Series JMS Adapter to process.2-1To use topics, you must run the following command in the MQ_Install /bin/ directory to point to the location of the MQSC file: .runmqsc Queue_Manager < ../java/bin/MQJMS_PSQ.mqsc For example: cd /opt/mqm/bin .runmqsc ICS_QM < ../java/bin/MQJMS_PSQ.mqsc Install the connectivity agent in an on-premises environment.The agent enables communication between Oracle Integration and the JMS (MQ) Server.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.