Applications
The Applications screen is the central registry of every application Nomasx-1 connects to. One line per application. Each row holds the identifier displayed across the rest of the product, the type of the source system, the database backend and the connection details (host, port, JDBC URL, user, password).
It is the first screen to populate when bringing a new source system in, and the last one to touch once everything else works.
At a glance
Goal of the view
Maintain the registry that every other screen references:
- Declare each source system. One row per application — ID, name, type (
JDE,SAP, custom…), database type (ORACLE,HANA,MSSQL,POSTGRES…), host. - Carry the connection details. Port, database, JDBC URL, user, password, direct-DB / DB-link flags are stored here, hidden from the default grid layout. The values are read by the Nomasx-1 scanners.
- Establish the application ID that flows through every other screen — the connection between user, role, conflict, licence and audit data.
Columns
| Column | Source | What it tells you |
|---|---|---|
| ID | APPS_ID — numeric identifier. | The application identifier referenced everywhere else in the product. |
| Name | APPS_NAME — friendly name. | Human-readable label. |
| Type | APPS_TYPE — source-system type. | JDE, SAP, custom… Used by the connector to know which catalog to read. |
| Database type | APPS_DBTYPE — backend type. | ORACLE, HANA, MSSQL, POSTGRES, … |
| Country | APPS_CTRY_ID — ISO country code. | Country tag on the connector. |
| Host | APPS_HOST — server. | Hostname / IP. |
| Port | APPS_PORT — port. Hidden. | Database port. |
| Database | APPS_DATABASE — schema / SID. Hidden. | DB-side identifier. |
| User / Password | APPS_USER, APPS_PASSWORD — credentials. Hidden. | Used by Nomasx-1 to read the source. |
| Direct DB / DB Link | APPS_DIRECTDB, APPS_DBLINK — flags. Hidden. | Indicates whether the connector goes through a DB link or directly. |
| JDBC | APPS_JDBC — JDBC URL. Hidden. | Connection string used when not via DB link. |
Audit columns APPS_AUDIT_USER, APPS_AUDIT_DATE are kept on the row.
Edit dialog
Click Add in the toolbar to create a new application, or double-click an existing row to edit. The dialog opens on the Application tab. The two read-only tabs Activity Log and Audit Trail are hidden on Add — they appear only when editing an existing row.
Tab 1 — Application
Identity of the application. ID is read-only when editing and required when adding. All four fields are mandatory.
| Field | What to enter |
|---|---|
| ID | Numeric identifier. Stays stable across the product — do not renumber after the application is in use. |
| Name | Friendly label that surfaces on every export. |
| Type | Source-system type: JDE, SAP, custom. Drives which connector reads the source. |
| Database type | Backend technology: ORACLE, HANA, MSSQL, POSTGRES, … |
Tab 2 — Connection
Where the source database lives and how Nomasx-1 reaches it.
| Field | What to enter |
|---|---|
| Host | Hostname or IP of the database server. |
| Port | Database port (1521 for Oracle, 1433 for MSSQL, …). |
| Database | Schema / SID / service name. |
| User | Read-only account Nomasx-1 uses to scan the source. |
| Password | Password for the account. Stored encrypted by Nomasx-1. |
Tab 3 — JD Edwards
Settings used only when the application is a JDE one. Fill in the schemas that locate the JDE security and master tables, then turn on the data sources to collect and set the retention for the Object Usage Tracking purge.
| Field | What to enter |
|---|---|
| JDE SY | Schema that holds the JDE System tables. |
| JDE DTA | Schema that holds the Business Data tables. |
| JDE CTL | Schema that holds the Control tables. |
| JDE SVM | Schema that holds the Server Map tables. |
| JDE CO | Schema that holds the Common tables. |
| JDE OL | Schema that holds the Object Librarian tables. |
| F00950 | Schema where the security workbench table is stored. |
| Standard Menu | Turn on to read the standard JDE menus during the scan. |
| E1 Pages | Turn on to collect E1 Pages. |
| E1 Composite | Turn on to collect composite pages. |
| Purge OUT | Turn on to let Nomasx-1 clean up old Object Usage Tracking rows automatically. |
| OUT Retention Days | Days of usage history to keep when the purge runs. |
Activating Object Usage Tracking records several thousand rows per day. After the data is aggregated by Nomasx-1, an automatic purge keeps the table healthy — turn on Purge OUT and pick a retention window that suits the audit needs.
The schema values come from the customer JDE installation — the JDE administrator is the right person to ask.
Tab 4 — LDAP
LDAP / Active Directory scope for the application. The values control which AD entries are pulled when the LDAP scan runs.
| Field | What to enter |
|---|---|
| LDAP Context | Base DN to start the search from (e.g. OU=Users,DC=corp,DC=local). |
| LDAP Filter | LDAP search filter restricting the entries pulled. |
| LDAP Exclude | Comma-separated list of entries to exclude from the scan. |
Tab 5 — Activity Log
Configures which database objects Nomasx-1 should monitor to feed the Applications → Activity log screen. Embedded grid of monitoring rules; one row per rule. Add a row to extend the surface, remove a row to narrow it. Hidden on Add — appears only after the application exists.
| Field | What to enter |
|---|---|
| Type | Kind of object the rule targets (e.g. TABLE, SCHEMA, OWNER). |
| Apps Type | Sub-class within the type — used by the connector to know how to query the rule's target. |
| Name | Name of the table, schema or owner the rule applies to. |
| Rule | Collection rule itself (column filter, include / exclude expression, retention…). |
Each row opens in its own dialog with the four fields above.
Tab 6 — Audit Trail
Configures the connection Nomasx-1 uses to read the Oracle archive logs for this application. Single form, one row per application. The values are read by the connector that pulls the audit data and feeds the Database → Audit Trail / Audit Lookup screens. Hidden on Add — appears only after the application exists.
| Field | What to enter |
|---|---|
| User | Database account that can read the archive log views. |
| Password | Password for that account. Stored encrypted. |
| Host | Hostname or IP of the database holding the archive logs. |
| Port | Database port (1521 on a standard Oracle install). |
| Database | Service name / SID of the database. |
| SCN | Starting System Change Number — where the next extraction resumes from. |
| Last | Read-only timestamp of the last successful extract. |
Context menu
Right-click a row to open the row menu. The shortcuts jump to the dedicated screens pre-filtered on the selected application.
| Action | Where it lands |
|---|---|
| JD Edwards | JDE-specific settings screen for the application. |
| LDAP | LDAP scope screen for the application. |
| Activity Log | Database → Activity Log filtered on the current application. |
Tips & best practices
- Application IDs should be stable. Once an application is referenced across roles, conflicts, licences and audit trail, renumbering the ID breaks the history.
- Pick a meaningful name. The application name surfaces on every export — short, recognisable labels make the deliverables easier to read.
- Keep the credentials current. A connector failing on credentials is the most common reason scans go stale.
- For non-JDE sources (
SAP, custom ERPs), make sure theTypevalue matches what the Nomasx-1 connectors expect — the scanners branch on it.