O Oracle Application Express (APEX) é uma plataforma de desenvolvimento de aplicativos web low code, que permite aos desenvolvedores criar soluções empresariais de forma rápida e eficiente. Neste artigo, apresentaremos um guia passo a passo para a instalação e criação de um ambiente Oracle APEX utilizando o ORDS Standalone em uma máquina com Oracle Linux, conectando a um banco de dados Oracle Database 19c em outro servidor Oracle Linux.
Este guia pode ser utilizando para instalação do Oracle APEX, tanto em ambiente on premisse, quanto em ambiente cloud. Para este ambiente foram utilizadas as versões APEX 23.1 e ORDS 23.., com conexão ao um ambiente de Oracle Database 19c que está em um servidor separado do servidor de aplicação.
***Antes de começarmos é importante destacar que o modo Standalone possui recursos mínimos de gerenciamento quando comparado à maioria dos servidores de aplicativos Java e pode não ter recursos de gerenciamento adequados para uso de produção em alguns ambientes.***
O download do ORDS e do APEX podem ser realizados através dos links abaixo:
O primeiro passo é conectar no servidor de banco de dados e fazer o download o APEX. Neste exemplo, o download esta sendo executado no diretório /tmp.
[root@lamimdb01 ~]# cd /tmp [root@lamimdb01 tmp]# [root@lamimdb01 tmp]# wget https://download.oracle.com/otn_software/apex/apex_22.1.zip --2023-07-21 12:06:17-- https://download.oracle.com/otn_software/apex/apex_22.1.zip Resolving download.oracle.com (download.oracle.com)... 23.49.100.106 Connecting to download.oracle.com (download.oracle.com)|23.49.100.106|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 241018124 (230M) [application/zip] Saving to: ‘apex_22.1.zip’ 100%[===================================================================================================================================================>] 241,018,124 28.5MB/s in 8.9s 2023-07-21 12:06:27 (26.0 MB/s) - ‘apex_22.1.zip’ saved [241018124/241018124] [root@lamimdb01 tmp]#
Posteriormente, deve-se descompactar o arquivo baixado.
[root@lamimdb01 tmp]# [root@lamimdb01 tmp]# unzip apex_22.1.zip Archive: apex_22.1.zip inflating: META-INF/MANIFEST.MF inflating: META-INF/ORACLE_C.SF inflating: META-INF/ORACLE_C.RSA creating: apex/ inflating: apex/apxsilentins.sql ...
Agora que o arquivo já esta descompactado, vamos conectar no banco de dados ao qual será instalado o APEX, onde será criada uma tablespace para armazenar os objetos do APEX.
[oracle@lamimdb01 tmp]$ [oracle@lamimdb01 tmp]$ sqlplus SQL*Plus: Release 19.0.0.0.0 - Production on Fri Jul 21 12:12:56 2023 Version 19.19.0.0.0 Copyright (c) 1982, 2022, Oracle. All rights reserved. Enter user-name: / as sysdba Connected to: Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production Version 19.19.0.0.0 SQL> alter session set container=APEX01; Session altered. SQL> create tablespace APEX datafile size 100m autoextend on next 100m; Tablespace created. SQL>
Criada a tablespace APEX, que será utilizada para armazenar os objetos do APEX, podemos seguir com o processo de instalação, através da execução do script apexins.sql que está localizado em /tmp/apex, seguindo a sintaxe abaixo:
@apexins.sql tablespace_apex tablespace_files tablespace_temp images
tablespace_apex: nome do tablespace para o usuário APEX.
tablespace_files: nome do tablespace para os objetos do APEX.
tablespace_temp: nome do tablespace temporária.
images: diretório virtual para imagens do Oracle APEX. Para instalações usando EPG, usar /i/.
SQL> @apexins.sql APEX APEX TEMP /i/
...set_appun.sql
PL/SQL procedure successfully completed.
...set_ufrom_and_upgrade.sql
PL/SQL procedure successfully completed.
Session altered.
FOO3
------------------------------
install2023-07-21_13-48-54.log
SP2-0606: Cannot create SPOOL file "install2023-07-21_13-48-54.log"
. ORACLE
.
. Oracle APEX Installation.
..........................................----Trecho final do output----ok 3 - 18 actions passed, 0 actions failed | 0.12
Thank you for installing Oracle APEX 22.1.0
Oracle APEX is installed in the APEX_220100 schema.
The structure of the link to the Oracle APEX administration services is as follows:
http://host:port/ords/apex_admin
The structure of the link to the Oracle APEX development interface is as follows:
http://host:port/ords
timing for: Phase 3 (Switch)
Elapsed: 00:00:06.86
timing for: Complete Installation
Elapsed: 00:04:21.77
not spooling currently
Concluída a execução do script de criação do APEX o próximo passo é a execução do script pxchpwd.sql. Este script irá criar e atualizar a conta de administrador do APEX.
Basta seguir fornecendo as informações solicitadas em tela, informando o nome de usuário, senha e o endereço de email.
Neste exemplo usei o nome do usuário como APEXADM, deixaremos o ID o email em branco e fornecendo a senha para o usuário. A senha deve conter ao menos um caractere e uma letra maiúscula, neste exemplo, foi usada a senha pwdAPX2023!.
SQL> @apxchpwd.sql ...set_appun.sql ================================================================================ This script can be used to change the password of an Oracle APEX instance administrator. If the user does not yet exist, a user record will be created. ================================================================================ Enter the administrator's username [ADMIN] User "ADMIN" does not yet exist and will be created. Enter ADMIN's email [ADMIN] Enter ADMIN's password [] Created instance administrator ADMIN. SQL>
Após a criação da conta de administração do APEX, devemos alterar a senha e desbloquear a conta APEX_PUBLIC_USER que será usada na configuração do DAD (database access descriptor).
--alteração da senha SQL> ALTER USER APEX_PUBLIC_USER IDENTIFIED BY "pwdAPX2023!"; User altered. --debloqueio do usuário SQL> ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK; User altered. SQL>
Agora é necessário configurar os serviços do RESTfull que irá configurar o listener e definir a senha. Esse processo é feito através da execução do script apex_rest_config.sql.
[oracle@lamimdb01 apex]$
[oracle@lamimdb01 apex]$ sqlplus
SQL*Plus: Release 19.0.0.0.0 - Production on Sun Jul 23 09:52:36 2023
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
Enter user-name: / as sysdba
Connected to:
Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production
Version 19.19.0.0.0
SQL> alter session set container=APEX01;
Session altered.
SQL> @apex_rest_config.sql PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. Enter a password for the APEX_LISTENER user [] Enter a password for the APEX_REST_PUBLIC_USER user [] ...set_appun.sql ...setting session environment PL/SQL procedure successfully completed. Procedure created. Session altered. Call completed. Call completed. Session altered. Procedure dropped. ...create APEX_LISTENER and APEX_REST_PUBLIC_USER users PL/SQL procedure successfully completed. User altered. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. ...grants for APEX_LISTENER and ORDS_METADATA user PL/SQL procedure successfully completed. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Session altered. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Synonym created. Session altered. PL/SQL procedure successfully completed. PL/SQL procedure successfully completed.
Com isso, finalizamos as configurações no banco de dados.
***********************************************************************************
A próxima etapa que consiste em instalar e configurar o ORDS. Como pré requisito é necessário que o java esteja instalado na maquina.
Na maquina de aplicação, após baixar o ords, basta descompacta-lo no diretório desejado, neste caso usamos o caminho /ords
[root@srvapex01 conf]# mkdir /ords [root@srvapex01 conf]# cd /ords/ [root@srvapex01 ords]# wget https://download.oracle.com/otn_software/java/ords/ords-23.2.0.177.0931.zip --2023-07-21 20:15:33-- https://download.oracle.com/otn_software/java/ords/ords-23.2.0.177.0931.zip Resolving download.oracle.com (download.oracle.com)... 23.198.211.129 Connecting to download.oracle.com (download.oracle.com)|23.198.211.129|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 101343108 (97M) [application/zip] Saving to: ‘ords-23.2.0.177.0931.zip’ ords-23.2.0.177.0931.zip 100%[====================================================================================================>] 96.65M 76.3MB/s in 1.3s 2023-07-21 20:15:35 (76.3 MB/s) - ‘ords-23.2.0.177.0931.zip’ saved [101343108/101343108] [root@srvapex01 ords]# [root@srvapex01 ords]# unzip ords-23.2.0.177.0931.zip Archive: ords-23.2.0.177.0931.zip creating: bin/ creating: linux-support/ creating: linux-support/man/ creating: examples/ creating: examples/application-container/ creating: examples/db_auth/ ... inflating: examples/plugins/lib/ords-plugin-api-23.2.0.177.0931-javadoc.jar [root@srvapex01 ords]#
Descompactado o ORDS, será necessário criar um diretório chamado conf que será utilizado para posteriormente criarmos um arquivo de configuração e o params que será usado para os dados de acesso ao banco.
[root@srvapex01 ords]# pwd /ords [root@srvapex01 ords]# ls -ltr total 195964 drwxr-xr-x 4 root root 38 Mar 27 08:34 scripts -rw-r--r-- 1 root root 5744 Mar 27 08:34 FUTC.txt drwxr-xr-x 7 root root 93 Mar 27 08:34 examples drwxr-xr-x 3 root root 17 Jun 6 10:47 lib drwxr-xr-x 2 root root 28 Jun 6 10:47 icons -rw-r--r-- 1 root root 75492 Jun 25 12:07 index.html -rw-r--r-- 1 root root 99227549 Jun 26 09:45 ords.war -rw-r--r-- 1 root root 5744 Jun 26 09:46 license.txt drwxr-xr-x 3 root root 86 Jun 26 09:46 linux-support drwxr-xr-x 3 root root 21 Jun 26 09:46 docs drwxr-xr-x 2 root root 34 Jun 26 09:46 bin -rw-r--r-- 1 root root 101343108 Jun 30 10:46 ords-23.2.0.177.0931.zip [root@srvapex01 ords]# mkdir conf [root@srvapex01 ords]# mkdir params [root@srvapex01 ords]# ls -ltr total 195964 drwxr-xr-x 4 root root 38 Mar 27 08:34 scripts -rw-r--r-- 1 root root 5744 Mar 27 08:34 FUTC.txt drwxr-xr-x 7 root root 93 Mar 27 08:34 examples drwxr-xr-x 3 root root 17 Jun 6 10:47 lib drwxr-xr-x 2 root root 28 Jun 6 10:47 icons -rw-r--r-- 1 root root 75492 Jun 25 12:07 index.html -rw-r--r-- 1 root root 99227549 Jun 26 09:45 ords.war -rw-r--r-- 1 root root 5744 Jun 26 09:46 license.txt drwxr-xr-x 3 root root 86 Jun 26 09:46 linux-support drwxr-xr-x 3 root root 21 Jun 26 09:46 docs drwxr-xr-x 2 root root 34 Jun 26 09:46 bin -rw-r--r-- 1 root root 101343108 Jun 30 10:46 ords-23.2.0.177.0931.zip drwxr-xr-x 2 root root 6 Jul 21 20:25 conf drwxr-xr-x 2 root root 6 Jul 21 20:25 params [root@srvapex01 ords]#
Será necessário instalar e configurar o ORDS para isso é preciso exportar as variáveis do JAVA e do ORDS e executar o comando ords install, sendo necessário durante a instalação informar os dados de conexão com o banco de dados.
export PATH=$JAVA_HOME/bin:/ords/bin:$PATH
java -jar apex.war install
[root@srvapex01 ords]# export PATH=$JAVA_HOME/bin:/ords/bin:$PATH [root@srvapex01 ords]#ords --config /ords/config install 2023-07-22T20:06:37.258Z INFO Your configuration folder /ords is located in ORDS product folder. Oracle recommends to use a different configuration folder. ORDS: Release 23.2 Production on Sat Jul 22 20:06:37 2023 Copyright (c) 2010, 2023, Oracle. Configuration: /ords/config The configuration folder /ords/config does not contain any configuration files. Oracle REST Data Services - Interactive Install Enter a number to select the type of installation [1] Install or upgrade ORDS in the database only [2] Create or update a database pool and install/upgrade ORDS in the database [3] Create or update a database pool only Choose [2]: 2 Created folder /ords/config Enter a number to select the database connection type to use [1] Basic (host name, port, service name) [2] TNS (TNS alias, TNS directory) [3] Custom database URL Choose [1]: 1 Enter the database host name [localhost]: lamimdb01.sub06292358060.vcn01.oraclevcn.com Enter the database listen port [1521]: Enter the database service name [orcl]: apex01.sub06292358060.vcn01.oraclevcn.com Provide database user name with administrator privileges. Enter the administrator username: sys Enter the database password for SYS AS SYSDBA: Connecting to database user: SYS AS SYSDBA url: jdbc:oracle:thin:@//lamimdb01.sub06292358060.vcn01.oraclevcn.com:1521/apex01.sub06292358060.vcn01.oraclevcn.com Retrieving information. Enter the default tablespace for ORDS_METADATA and ORDS_PUBLIC_USER [SYSAUX]: APEX Enter the temporary tablespace for ORDS_METADATA and ORDS_PUBLIC_USER [TEMP]: Enter a number to select additional feature(s) to enable: [1] Database Actions (Enables all features) [2] REST Enabled SQL and Database API [3] REST Enabled SQL [4] Database API [5] None Choose [1]: Enter a number to configure and start ORDS in standalone mode [1] Configure and start ORDS in standalone mode [2] Skip Choose [1]: Enter a number to select the protocol [1] HTTP [2] HTTPS Choose [1]: Enter the HTTP port [8080]: Enter the APEX static resources location: The setting named: db.connectionType was set to: basic in configuration: default The setting named: db.hostname was set to: lamimdb01.sub06292358060.vcn01.oraclevcn.com in configuration: default The setting named: db.port was set to: 1521 in configuration: default The setting named: db.servicename was set to: apex01.sub06292358060.vcn01.oraclevcn.com in configuration: default The setting named: plsql.gateway.mode was set to: proxied in configuration: default The setting named: db.username was set to: ORDS_PUBLIC_USER in configuration: default The setting named: db.password was set to: ****** in configuration: default The setting named: feature.sdw was set to: true in configuration: default The global setting named: database.api.enabled was set to: true The setting named: restEnabledSql.active was set to: true in configuration: default The setting named: security.requestValidationFunction was set to: ords_util.authorize_plsql_gateway in configuration: default The global setting named: standalone.http.port was set to: 8080 The global setting named: standalone.context.path was set to: /ords The global setting named: standalone.doc.root was set to: /ords/config/global/doc_root 2023-07-23T13:08:09.867Z INFO Installing Oracle REST Data Services version 23.2.0.r1770931 in APEX01 ------------------------------------------------------------ Date : 23 Jul 2023 13:08:09 Release : Oracle REST Data Services 23.2.0.r1770931 Type : ORDS Install Database : Oracle Database 19c Standard Edition 2 DB Version : 19.19.0.0.0 ------------------------------------------------------------ Container Name: APEX01 Executing scripts for core ------------------------------------------------------------ [*** script: ords_prereq_env.sql] INFO: Checking prerequisites for Oracle REST Data Services PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. ... PL/SQL procedure successfully completed. Commit complete. 2023-07-22T20:08:35.827Z INFO Completed installation for Oracle REST Data Services version 23.2.0.r1770931. Elapsed time: 00:00:21.247 [*** Info: Completed installation for Oracle REST Data Services version 23.2.0.r1770931. Elapsed time: 00:00:21.247 ] ------------------------------------------------------------ Container Name: TST01_PDB1 ------------------------------------------------------------ [*** script: ords_configure_gateway.sql] Configured PL/SQL Gateway user APEX_PUBLIC_USER to be proxiable from ORDS_PUBLIC_USER PL/SQL procedure successfully completed. 2023-07-22T20:08:35.889Z INFO Completed configuring PL/SQL gateway user for Oracle REST Data Services version 23.2.0.r1770931. Elapsed time: 00:00:00.57 [*** Info: Completed configuring PL/SQL gateway user for Oracle REST Data Services version 23.2.0.r1770931. Elapsed time: 00:00:00.57 ] ......
db.connectionType=basic standalone.doc.root=/ords/config/global/doc_root 2023-07-23T13:08:26.443Z WARNING *** jdbc.MaxLimit in configuration |default|lo| is using a value of 20, this setting may not be sized adequately for a production environment *** 2023-07-23T13:08:26.443Z WARNING *** jdbc.InitialLimit in configuration |default|lo| is using a value of 3, this setting may not be sized adequately for a production environment *** 2023-07-23T13:08:32.737Z INFO Mapped local pools from /ords/config/databases: /ords/ => default => VALID 2023-07-23T13:08:32.831Z INFO Oracle REST Data Services initialized Oracle REST Data Services version : 23.2.0.r1770931 Oracle REST Data Services server info: jetty/10.0.15 Oracle REST Data Services java info: Java HotSpot(TM) 64-Bit Server VM 11.0.10+8-LTS-162
No processo a acima a sessão ficará "presa" para executar o serviço. Acessando o endereço do servidor de aplicação na porta 8080 (definida acima), é possível ver os serviços do ORDS.
Porém se acessarmos o APEX, teremos o erro relacionado aos arquivos do APEX não foram carregados.
Para corrigir o erro acima, basta baixar o arquio arquivo images do diretório apex do servidor de banco de dados, para o servidor de aplicação no diretório /i (definido na instalação do APEX) e conceder permissão total. Ou podemos simplesmente baixar o arquivo novamente, direto no servidor de aplicação que é a opção que estarei utilizando.
[root@srvapex01 ~]# mkdir /apex [root@srvapex01 ~]# cd /apex [root@srvapex01 apex]# wget https://download.oracle.com/otn_software/apex/apex_22.1.zip --2023-07-23 13:17:21-- https://download.oracle.com/otn_software/apex/apex_22.1.zip Resolving download.oracle.com (download.oracle.com)... 96.7.220.89 Connecting to download.oracle.com (download.oracle.com)|96.7.220.89|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 241018124 (230M) [application/zip] Saving to: ‘apex_22.1.zip’ apex_22.1.zip 100%[====================================================================================================>] 229.85M 64.4MB/s in 3.5s 2023-07-23 13:17:25 (65.0 MB/s) - ‘apex_22.1.zip’ saved [241018124/241018124] [root@srvapex01 apex]# [root@srvapex01 apex]# [root@srvapex01 apex]# [root@srvapex01 apex]# [root@srvapex01 apex]# unzip apex_22.1.zip Archive: apex_22.1.zip inflating: META-INF/MANIFEST.MF inflating: META-INF/ORACLE_C.SF inflating: META-INF/ORACLE_C.RSA creating: apex/ inflating: apex/apxsilentins.sql inflating: apex/apxpatch_nocdb.sql inflating: apex/apxdevrm_cdb.sql inflating: apex/coreins3.sql ...... inflating: apex/utilities/apxpart.sql inflating: apex/utilities/reset_image_prefix.sql inflating: apex/utilities/readme.txt inflating: apex/utilities/apxrekey.sql inflating: apex/apexins_cdb.sql [root@srvapex01 apex]# cd apex/ [root@srvapex01 apex]# ls apexins1.sql apexins_nocdb.sql appins.sql apxdvins_cdb.sql apxpatch.sql apxrtins1.sql apxrtins.sql coreins4.sql images apexins2.sql apexins.sql apxappcon.sql apxdvins_nocdb.sql apxremov1.sql apxrtins2.sql apxsilentins.sql coreins5.sql LICENSE.txt apexins3.sql apex_rest_config_cdb.sql apxchpwd.sql apxdvins.sql apxremov2.sql apxrtins3.sql builder coreins.sql load_trans.sql apexins_adb.sql apex_rest_config_core.sql apxdevrm_cdb.sql apxdwngrd.sql apxremov_cdb.sql apxrtins_cdb.sql core dbcsconf.sql utilities apexins_cdb.sql apex_rest_config_nocdb.sql apxdevrm_nocdb.sql apxpatch_cdb.sql apxremov_nocdb.sql apxrtins_cdb_upg.sql coreins2.sql dbcsins.sql apexins_cdb_upg.sql apex_rest_config.sql apxdevrm.sql apxpatch_nocdb.sql apxremov.sql apxrtins_nocdb.sql coreins3.sql devins.sql [root@srvapex01 apex]# mv images /i [root@srvapex01 apex]# chmod 777 /i [root@srvapex01 apex]#
Copiadas as imagens e ajustada a permissão, será necessário configurar o standalone.static.path do ords para o caminha /i (diretório que criamos com as imagens).
export PATH=$JAVA_HOME/bin:/ords/bin:$PATH
ords --config /ords/config config set standalone.static.path /i
[root@srvapex01 ords]#export PATH=$JAVA_HOME/bin:/ords/bin:$PATH [root@srvapex01 ords]# ords --config /ords/config config set standalone.static.path /i 2023-07-23T13:19:02.143Z INFO Your configuration folder /ords/config is located in ORDS product folder. Oracle recommends to use a different configuration folder. ORDS: Release 23.2 Production on Sun Jul 23 13:19:02 2023 Copyright (c) 2010, 2023, Oracle. Configuration: /ords/config/ The global setting named: standalone.static.path was set to: /i [root@srvapex01 ords]#
Concluídos os ajustes, basta iniciar o serviço Standalone do ORDS e acessar novamente a aplicação. O ideal é que seja criado um script de start e stop para gerenciar o processo de inicialização do ORDS e também inclui-lo no startup automático da máquina, uma vez que executando diretamente o comando abaixo a sessão fica presa enquanto o serviço estiver ativo.
[root@srvapex01 ords]# ords --config /ords/config serve 2023-07-23T13:19:21.994Z INFO Your configuration folder /ords/config is located in ORDS product folder. Oracle recommends to use a different configuration folder. ORDS: Release 23.2 Production on Sun Jul 23 13:19:22 2023 Copyright (c) 2010, 2023, Oracle. Configuration: /ords/config/ 2023-07-23T13:19:22.188Z INFO HTTP and HTTP/2 cleartext listening on host: 0.0.0.0 port: 8080 2023-07-23T13:19:22.207Z INFO Disabling document root because the specified folder does not exist: /ords/config/global/doc_root 2023-07-23T13:19:22.208Z INFO Default forwarding from / to contextRoot configured. 2023-07-23T13:19:25.014Z INFO Configuration properties for: |default|lo| db.servicename=apex01.sub06292358060.vcn01.oraclevcn.com awt.toolkit=sun.awt.X11.XToolkit java.specification.version=11 conf.use.wallet=true sun.cpu.isalist= sun.jnu.encoding=UTF-8 user.region=US java.class.path=/ords/ords.war java.vm.vendor=Oracle Corporation sun.arch.data.model=64 standalone.static.path=/i nashorn.args=--no-deprecation-warning java.vendor.url=https://openjdk.java.net/ resource.templates.enabled=false user.timezone=UTC db.port=1521 java.vm.specification.version=11 os.name=Linux sun.java.launcher=SUN_STANDARD user.country=US sun.boot.library.path=/usr/java/jdk-11.0.10/lib sun.java.command=/ords/ords.war --config /ords/config serve jdk.debug=release sun.cpu.endian=little user.home=/root oracle.dbtools.launcher.executable.jar.path=/ords/ords.war user.language=en java.specification.vendor=Oracle Corporation java.version.date=2021-01-19 database.api.enabled=true java.home=/usr/java/jdk-11.0.10 db.username=ORDS_PUBLIC_USER file.separator=/ java.vm.compressedOopsMode=Zero based line.separator= restEnabledSql.active=true java.specification.name=Java Platform API Specification java.vm.specification.vendor=Oracle Corporation java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment feature.sdw=true java.awt.headless=true standalone.context.path=/ords db.hostname=lamimdb01.sub06292358060.vcn01.oraclevcn.com db.password=****** sun.management.compiler=HotSpot 64-Bit Tiered Compilers security.requestValidationFunction=ords_util.authorize_plsql_gateway java.runtime.version=11.0.10+8-LTS-162 user.name=root path.separator=: standalone.http.port=8080 os.version=5.15.0-102.110.5.1.el8uek.x86_64 java.runtime.name=Java(TM) SE Runtime Environment file.encoding=UTF-8 plsql.gateway.mode=proxied java.vm.name=Java HotSpot(TM) 64-Bit Server VM java.vendor.version=18.9 standalone.doc.root=/ords/config/global/doc_root java.vendor.url.bug=https://bugreport.java.com/bugreport/ java.io.tmpdir=/tmp oracle.dbtools.cmdline.ShellCommand=ords java.version=11.0.10 user.dir=/ords os.arch=amd64 java.vm.specification.name=Java Virtual Machine Specification java.awt.printerjob=sun.print.PSPrinterJob oracle.dbtools.cmdline.home=/ords sun.os.patch.level=unknown java.library.path=/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib java.vendor=Oracle Corporation java.vm.info=mixed mode java.vm.version=11.0.10+8-LTS-162 sun.io.unicode.encoding=UnicodeLittle db.connectionType=basic java.class.version=55.0 2023-07-23T13:19:25.014Z WARNING *** jdbc.MaxLimit in configuration |default|lo| is using a value of 20, this setting may not be sized adequately for a production environment *** 2023-07-23T13:19:25.015Z WARNING *** jdbc.InitialLimit in configuration |default|lo| is using a value of 3, this setting may not be sized adequately for a production environment *** 2023-07-23T13:19:30.685Z INFO Mapped local pools from /ords/config/databases: /ords/ => default => VALID 2023-07-23T13:19:30.785Z INFO Oracle REST Data Services initialized Oracle REST Data Services version : 23.2.0.r1770931 Oracle REST Data Services server info: jetty/10.0.15 Oracle REST Data Services java info: Java HotSpot(TM) 64-Bit Server VM 11.0.10+8-LTS-162
Agora ao acessar o endereço do APEX que o mesmo esta abrindo corretamente.
https://docs.oracle.com/en/database/oracle/apex/23.1/htmig/installing-and-configuring-apex-and-ords.html#GUID-8EE981AD-B1F9-46C2-BB5A-C9FE60CCD4AA
Comentários
Postar um comentário