You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## 24.2.14
* [GAT-438] - github #19 Expose Severity attribute to main report
* [GAT-439] - Check App ID availability in sert.properties before starting #11
* [GAT-448] - Exclude File Browse item from Encrypted Items check #27
* [GAT-449] - Run authz on public pages should be ignored if authz scheme = must not be public user #28
* [GAT-457] - Doc: ora-22905 in exceptions API when referencing a table sql_macro #34
* [GAT-458] - Expose Severity attribute to main report #19
## 24.2.13
* [GAT-456] - error in eval_pkg causes pending exceptions to be marked stale
Because APEX-SERT is installed via liquibase in SQLCL, you cannot use the
5
+
SYS schema for installations.
6
+
The ACDC schema provides all the privileges necessary to install APEX-SERT.
7
+
You may name the schema as you wish, and we strongly recommend disabling teh account after installation.
8
+
9
+
[Script descriptions](#script-descriptions)
10
+
11
+
[Modifying ACDC roles and privileges](#modifying-acdc-roles-and-privileges)
12
+
13
+
[Too much info, just install the thing!](#installation)
14
+
15
+
## Script descriptions
16
+
17
+
The driver script for managing the ACDC schema is `create_acdc_schema.sql`. This script takes takes 3 arguments:
18
+
19
+
* Schema name
20
+
* Schema password
21
+
* Schema data tablespace name
22
+
23
+
Running the above script will automatically call the following children scipts (in this provided order):
24
+
25
+
*`schema_grants.sql`: Grants privileges to ACDC schema
26
+
*`schema_revokes.sql`: Revokes privileges from ACDC schema. Follows the same collection convention as `schema_grants.sql` (see below).
27
+
*`schema_additional_setup.sql`: Additional roles for ACDC; creation/management of revision history
28
+
29
+
## Modifying ACDC roles and privileges
30
+
The `schema_grants.sql` script contains a list of the roles and privileges that are granted to ACDC. To add or modify the roles/privileges provided to ACDC, simply add them to the appropriate collection.
31
+
32
+
The `schema_revokes.sql` script is run after the `schema_grants.sql` script. To avoid confusion, if a role/privilege is to be removed from the from the ACDC user, it should be removed from `schema_grants.sql` script and added to `schema_revokes.sql`
33
+
34
+
Below is a list of the collections used to specify the roles and privileges and how to modify them.
35
+
36
+
***NOTE***: Each collection is ordered by the role/privilege name so that it is easy for developer to identify and find what is already being granted to ACDC. Please continue to enforce this.
37
+
38
+
### l_roles
39
+
40
+
This is a collection of the roles that will be provided to ACDC. The collection is made of objects with the following attributes:
41
+
42
+
* Role name
43
+
* Can ACDC grant the role to other users
44
+
45
+
### l_tab_privs
46
+
47
+
This is a collection of the table privileges that will be provided to ACDC. The collection is made of objects with the following attributes:
48
+
49
+
* Object owner
50
+
* Object name
51
+
* Privilege type (read, select, insert, execute, etc.)
52
+
* Can ACDC grant the table privilege to other users
53
+
* Is the privilege for a directory object
54
+
55
+
### l_sys_privs
56
+
57
+
This is a collection of the system privileges that will be provided to ACDC. The collection is made of objects with the following attributes:
58
+
59
+
* System privilege name
60
+
* Can ACDC grant the system privilege to other users
61
+
62
+
## Installation
63
+
64
+
1. Unpack it
65
+
1. Connect to the target database as ADMIN (ADB) or SYS (PDB)
* The values of `<acdc password>` and `<acdc tablespace>` are only relevant for new installations, but the script expects them on every run. For systems where ACDC is already installed, you do not need to supply valid values for these parameters
71
+
* On ADB, the value for `<acdc tablespace>` should always be DATA (or data, we're not _that_ picky)
72
+
* Since you're using the packaged scripts, the value for ACDC_RELEASE will already be set, and the database will be updated accordingly.
Copy file name to clipboardExpand all lines: doc/install_guide.md
+25-15Lines changed: 25 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,20 +29,28 @@ Installing APEX-SERT is a simple process that is done entirely via a SQL script.
29
29
30
30
#### 2.1.1. Software Versions
31
31
32
-
#### 2.1.1.1 APEX
32
+
#### 2.1.1.1 Database
33
33
34
-
Minimum APEX version: 24.1
34
+
**Version:** 19.6+
35
35
36
-
APEX-SERT 24.1 is supported only on Oracle APEX 24.1 and higher. If you are using an APEX version prior to 24.1, you need to upgrade your instance to use SERT.
36
+
APEX-SERT makes use of SQL Macros for table expressions. This feature was backported to 19c in the 19.6 update.
37
+
38
+
SQL Macros for table expressions were made generally available in 21c
39
+
40
+
#### 2.1.1.2 APEX
41
+
42
+
Minimum APEX version: 24.2
43
+
44
+
APEX-SERT 24.2 is supported only on Oracle APEX 24.2 and higher. If you are using an APEX version prior to 24.2, you need to upgrade your instance to use APEX-SERT.
37
45
38
46
> [!NOTE]
39
-
>This version of APEX-SERT is a complete rewrite from the ground up. It can be installed independently of an existing SERT, but there is no migration of historical scans, nor of exceptions.
47
+
>This version of APEX-SERT is a complete rewrite from the ground up. It can be installed independently of an existing APEX-SERT, but there is no migration of historical scans, nor of exceptions.
40
48
41
-
#### 2.1.1.2 Requirements for AOP
49
+
#### 2.1.1.3 Requirements for AOP
42
50
43
51
to use the AOP report pages, you MUST have your own APEX Office Print Server.
44
52
45
-
#### 2.1.1.2 Requirements for DocGen
53
+
#### 2.1.1.4 Requirements for DocGen
46
54
47
55
APEX-SERT provides the capability to make use of DocGen, provided you have already setup and configured DocGen for your service.
48
56
@@ -62,7 +70,7 @@ In order to install APEX-SERT, you will need access to the following system reso
62
70
63
71
* Oracle SYS or ADMIN database account.
64
72
- SYS is used ONLY in non ADB installs, to create a privileged installer schema
65
-
* For Autonomous installs, use ADMIN
73
+
* For Autonomous installs, use ADMIN or create an [installer account](#221-acdc-installing-schema-creation-script)
66
74
* Oracle APEX instance administration account
67
75
* SQLCL 24.2 or higher
68
76
@@ -80,7 +88,7 @@ For AUTONOMOUS, use DATA as your tablespace
80
88
81
89
#### 2.2.1 ACDC installing schema creation script
82
90
83
-
Access the "acdc" setup scripts from the sert_latest.zip file, located in product/sert/pre-install/. refer to the [README.md](README.md) for details of installation
91
+
Access the "acdc" setup scripts from the sert_latest.zip file, located in product/sert/pre-install/acdc. refer to the [README.md](ACDC_README.md) for details of installation
84
92
85
93
As the `ADMIN` or `SYS` user, use the supplied script create_acdc_schema.sql using sqlcl.
86
94
@@ -110,7 +118,7 @@ If you wish to pre-specify the Application ID for the SERT application, and it's
110
118
111
119
Define your desired AOP server: You can simply define as localhost if you do not have or intend to use AOP.
The installation will create two schema in your database:
141
149
142
150
***SERT_CORE**
143
-
- Schema which holds all of the APEX-SERT database objects and metadata.
151
+
* Schema which holds all of the APEX-SERT database objects and metadata.
144
152
***SERT_PUB**
145
-
- Schema which will be used as the Parse As schema for the APEX-SERT APEX applications.
153
+
* Schema which will be used as the Parse As schema for the APEX-SERT APEX applications.
146
154
147
155
It also creates an APEX workspace called SERT (or the name you supplied in the sert.properties). This is where the APEX-SERT APEX applications will be installed. The SERT workspace will not contain any developer users or workspace administrators, as it is not necessary nor required that any APEX developer access this workspace.
148
156
@@ -157,10 +165,10 @@ It also creates an APEX workspace called SERT (or the name you supplied in the s
157
165
1. Locate and change directories to the sert_latest directory that was created in the last section.
158
166
1. Enter the following command and press enter:
159
167
160
-
`sql ACDC@<database>`
168
+
`sql ACDC@[database]`
161
169
162
-
you will be prompted for your schema password, and <database> is your database TNSNames entry. For ADB, use the LOW connection to avoid parallelisation
163
-
1. Depending on your environment, it may not be necessary to enter a value for `<database>`.
170
+
you will be prompted for your schema password, and [database] is your database TNSNames entry. For ADB, use the LOW connection to avoid parallelisation
171
+
1. Depending on your environment, it may not be necessary to enter a value for `[database]`.
164
172
1. From the SQL Plus prompt, enter the following and press enter:
165
173
166
174
`@install.sql`
@@ -173,6 +181,9 @@ The design of the builder extension menu means that we *cannot* have the extensi
173
181
174
182
This should be run as the "acdc" or equivalent user. (admin should work too in ADB)
175
183
184
+
> [!TIP]
185
+
> this is a useful block of code for a periodic job to automate subscription for new workspaces created after installation
186
+
176
187
```sql
177
188
BEGIN
178
189
for rec in
@@ -217,4 +228,3 @@ to do this manually for a single workspace:
217
228
<!--  -->
218
229
219
230
<imgsrc="./images/launch-sert.gif"alt="GIF of user launching SERT"width=50%height=50%>
0 commit comments