OpenAI Note: CloudBeaver is not affiliated with OpenAI. Integration is achieved through the public API. To utilize this feature, register with OpenAI and obtain a secret key. With the feature, you can automatically generating the correct SQL code. To activate the AI features in CloudBeaver, configure the API token: AI Smart Assistance Table of contents Understanding the AI integration in CloudBeaver Initial Service Navigate to -> AI Settings tab Choose an engine In the field, input your AI secret key. API token Save the changes. For instructions on utilizing the AI features, visit the . AI Smart completion

contentRoot: "web", driversLocation: "drivers", rootURI: "/", serviceURI: "/api/", // Webapp configuration file productConfiguration: "conf/product.conf", rootURI Web application URI prefix. by default / serviceURI Services API URI prefix (relative to rootURI). by default. /api/ productConfiguration Path to product (web interface) configuration file serverName: "CloudBeaver Server", rootURI: "${cb.prefix}", serviceURI: "/api/", expireSessionAfterPeriod: ${cb.expire-time}, } } Automatic server configuration Datasources

contentRoot: "web", driversLocation: "drivers", rootURI: "/", serviceURI: "/api/", // Webapp configuration file productConfiguration: "conf/product.conf", jar files rootURI Web application URI prefix. / by default serviceURI Services API URI prefix (relative to rootURI). /api/ by default. productConfiguration Path to product (web interface) configuration serverName: "CloudBeaver Server", rootURI: "${cb.prefix}", serviceURI: "/api/", expireSessionAfterPeriod: ${cb.expire-time}, } } CloudBeaver user guide 23.0 65/111

contentRoot: "web", driversLocation: "drivers", rootURI: "/", serviceURI: "/api/", // Webapp configuration file productConfiguration: "conf/product.conf", rootURI Web application URI prefix. by default / serviceURI Services API URI prefix (relative to rootURI). by default. /api/ productConfiguration Path to product (web interface) configuration file serverName: "CloudBeaver Server", rootURI: "${cb.prefix}", serviceURI: "/api/", expireSessionAfterPeriod: ${cb.expire-time}, } } CloudBeaver User Guide 23.1. Page

contentRoot: "web", driversLocation: "drivers", rootURI: "/", serviceURI: "/api/", // Webapp configuration file productConfiguration: "conf/product.conf", rootURI Web application URI prefix. by default / serviceURI Services API URI prefix (relative to rootURI). by default. /api/ productConfiguration Path to product (web interface) configuration file serverName: "CloudBeaver Server", rootURI: "${cb.prefix}", serviceURI: "/api/", expireSessionAfterPeriod: ${cb.expire-time}, } } Using environment variables CloudBeaver

source code is available for examination and improvement. The debugger provides the required server API for debugging PL/SQL procedures with: Breakpoint management; Step-by-step tracing; Variable acquisition debugged process, using PORT from step 3 provided by the initiator. The connection is established via API call . If the attach_to_port connection cannot be established, the message appears. Error rcv client creates a global breakpoint for the selected function, and then becomes blocked via the API call waiting for the server process. pldbg_wait_for_target PROXY receives the global control point

source code is available for examination and improvement. The debugger provides the required server API for debugging PL/SQL procedures with: Breakpoint management; Step-by-step tracing; Variable acquisition debugged process, using PORT from step 3 provided by the initiator. The connection is established via API call . If the attach_to_port connection cannot be established, the message appears. Error rcv client creates a global breakpoint for the selected function, and then becomes blocked via the API call waiting for the server process. pldbg_wait_for_target PROXY receives the global control point

source code is available for examination and improvement. The debugger provides the required server API for debugging PL/SQL procedures with: Breakpoint management; Step-by-step tracing; Variable acquisition debugged process, using PORT from step 3 provided by the initiator. The connection is established via API call . If the attach_to_port connection cannot be established, the message appears. Error rcv client creates a global breakpoint for the selected function, and then becomes blocked via the API call waiting for the server process. pldbg_wait_for_target PROXY receives the global control point

source code is available for examination and improvement. The debugger provides the required server API for debugging PL/SQL procedures with: Breakpoint management; Step-by-step tracing; Variable acquisition debugged process, using PORT from step 3 provided by the initiator. The connection is established via API call . If the attach_to_port connection cannot be established, the message appears. Error rcv client creates a global breakpoint for the selected function, and then becomes blocked via the API call waiting for the server process. pldbg_wait_for_target PROXY receives the global control point

source code is available for examination and improvement. The debugger provides the required server API for debugging PL/SQL procedures with: Breakpoint management; Step-by-step tracing; Variable acquisition debugged process, using PORT from step 3 provided by the initiator. The connection is established via API call . If the attach_to_port connection cannot be established, the message appears. Error rcv client creates a global breakpoint for the selected function, and then becomes blocked via the API call waiting for the server process. pldbg_wait_for_target PROXY receives the global control point