Erstellt am23. Juni 2021

durchwordpressadmin

URL Adresse: https://books.clusterapps.com/books/deployments/page/oracle-xe-and-apex-on-centos-7

Oracle XE and APEX on CentOS 7

Downloading the software

The first thing to do is download the software from Oracle Technology Network:

Database Downloads – you will need the package for Linux x64 and the preinstall RPM package.
Developer Tools/Oracle REST Data Services/Downloads
Developer Tools/Application Express/Downloads

After the files have been downloaded, transfer them to the server.

Installation of RDBMS

After you checked them, to install the RDBMS, you need to install the preinstall RPM package first and then install the database software as following: 1

wget https://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/getPackage/oracle-database-preinstall-18c-1.0-1.el7.x86_64.rpm

yum install oracle-database-preinstall-18c* -y

yum install oracle-database-xe-18c* -y

yum install httpd tomcat  -y

The user oracle and the group oinstallare created during the package installation. A default user environment is created during the set up process. You can set a password for this user by invoking passwd oracle command. This user is the owner of the /opt/oracle directory where the Oracle Database is located and this must stay unchanged. 1

 chown oracle:oinstall /opt/oracle

When the packages are installed and the user is set up, you need to run the initial database configuration script and answer all of the questions. 1

/etc/init.d/oracle-xe-18c configure

After answering the questions it is going to take several minutes to initialize the database.

Setting up environment

Set up Oracle Database environment variables . 1

echo 'ORACLE_SID=XE' >> /etc/profile.d/oraenv.sh

echo 'ORAENV_ASK=NO' >> /etc/profile.d/oraenv.sh

echo '. /opt/oracle/product/18c/dbhomeXE/bin/oraenv -s' >> /etc/profile.d/oraenv.sh

. /etc/profile.d/oraenv.sh

Enable Oracle Database XE service for automatic startup: 1

systemctl enable oracle-xe-18c

Connecting to database

And we are ready to log into the database. 1

sqlplus /nolog

Check if everything is good. 1

-- connect to the database

sqlplus /nolog

-- change role

CONNECT SYS as SYSDBA

-- basic query to check everything came up right

select * from dual;

-- exit the database

exit

To make it easier to connect to the pluggable database, edit thetnsnames.ora file and add there a new connection descriptor 1

vim /opt/oracle/product/18c/dbhomeXE/network/admin/tnsnames.ora

Add the following after the standard XE record: 1

PDB1 =

  (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))

    (CONNECT_DATA =

      (SERVER = DEDICATED)

      (SERVICE_NAME = XEPDB1)

Installation of APEX

Change your directory back to /root, unzip the APEX archive and make the user oracle the owner of the directory. Considering we are installing the 19.2 version of APEX, it would look like this. 1

cd /root

mkdir -p /opt/oracle/apex

unzip apex_19.*.zip -d /opt/oracle

chown -R oracle:oinstall /opt/oracle/apex

Create an allow all ACL for APEX sql file in the APEX directory. This one is called apex_acl.sql. 1

BEGIN

  BEGIN

    dbms_network_acl_admin.drop_acl(acl => 'all-network-PUBLIC.xml');

  EXCEPTION

    WHEN OTHERS THEN

      NULL;

  END;

  dbms_network_acl_admin.create_acl(acl         => 'all-network-PUBLIC.xml',

                                    description => 'Allow all network traffic',

                                    principal   => 'PUBLIC',

                                    is_grant    => TRUE,

                                    privilege   => 'connect');

  dbms_network_acl_admin.add_privilege(acl       => 'all-network-PUBLIC.xml',

                                       principal => 'PUBLIC',

                                       is_grant  => TRUE,

                                       privilege => 'resolve');

  dbms_network_acl_admin.assign_acl(acl  => 'all-network-PUBLIC.xml',

                                    host => '*');

END;

sho err

COMMIT;

From the APEX directory connect to the pluggable database as sysdba and run the installation scripts. 1

cd /opt/oracle/apex

-- connect to the database

sqlplus /nolog

-- change role

CONN sys@pdb1 AS SYSDBA

-- run the script to install a full development environment

@apexins.sql SYSAUX SYSAUX TEMP /i/

 -- create an instance administrator user and set their password

@apxchpwd.sql

-- unlock APEX public user

ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK;

ALTER USER APEX_PUBLIC_USER IDENTIFIED BY "S0m3aw3s0m3Pw!";

-- configure REST Data Services

@apex_rest_config.sql

-- run the ACL setup

@apex_acl.sql

-- disconnect from the database

exit

Copy APEX static files to the web server directory. They will be used to serve static images from the proxy. 1

mkdir -p /var/www/apex/images

cp -a /opt/oracle/apex/images/. /var/www/apex/images

The Application Express installation is complete.

Installation of ORDS

The Oracle Rest Data Services (ORDS) installation consists of unzipping the downloaded archive, running the configuration command, and then deploying the ords.war file into the Tomcat webapps folder. 1

cd /root

mkdir -p /opt/oracle/ords

unzip ords-19.*.zip -d /opt/oracle/ords

Run the ORDS configuration command with the advanced mode to run the interactive installation process. 1

cd /opt/oracle/ords

java -jar ords.war install advanced

When prompted for ORDS configuration directory, enter config.
Then provide the connection info to your pluggable database XEPDB1

Follow the on screen instructions.

After the configuration is completed, the values are saved in opt/oracle/ords/config/ords/defaults.xml file. It can be modified there. See more at Oracle Docs.

The tomcat user (created as part of Tomcat install) must have read-write access to the ORDS configuration folder: 1

chown -R tomcat:tomcat /opt/oracle/ords/config

Deploy ORDS to Tomcat application server. Copy the ords.war into the Tomcat webapps directory for this 1

cp -a /opt/oracle/ords/ords.war /usr/share/tomcat/webapps/

Done with ORDS and Tomcat, on to Apache.

Configuration of Apache httpd to map ORDS

The last step is to configure Apache to map HTTP-requests to ORDS and therefore APEX engine.

For this, add a custom httpd configuration file. By default, every .conf file placed in the etc/httpd/conf.d/ directory is read by httpd as an additional configuration file to the main /etc/httpd/conf/httpd.conf config file.

Create the apex.conf file in the etc/httpd/conf.d/ directory with the contents as below: 1

# forward ORDS tomcat

<VirtualHost *:80>

    # uncomment the lines below if you plan to serve different domains

    # on this web server, don't forget to change the domain name

    # ServerName yourdomain.tld

    # ServerAlias www.yourdomain.tld

    # alias for APEX static files

    Alias "/i" "/var/www/apex/images/"

    # uncomment the line below if you want

    # to redirect traffic to ORDS from root path

    # RedirectMatch permanent "^/$" "/ords"

    # proxy ORDS requests to tomcat

    ProxyRequests off

    <Location "/ords">

        ProxyPass "ajp://localhost:8009/ords"

        ProxyPassReverse "ajp://localhost:8009/ords"

    </Location>

</VirtualHost>

Tell SELinux (Yes, that should be running) to allow Apache to communicate to tomcat. 1

setsebool httpd_can_network_connect on

Now you are ready to save the configuration file and restart the services. 1

systemctl restart httpd

systemctl restart tomcat

Open a few firewall ports. Yes, the the firewall should also be on. 1

firewall-cmd --permanent --add-service={http,https}

firewall-cmd --reload

And finally, access APEX from your web browser using a link like http://yourdomain.tld/ords (or http://yourdomain.tld in case you switched on force redirection), where yourdomain.tld is the domain name or the IP-address of your server.

Wie können wir helfen?