File size (Download)​

• Reference: What is the Significance of the MaxExternalResponseSize Parameter in the Rest.ini? (Doc ID 2949357.1)
• Link: Configuration -> General
• Setting: Maximum External REST Response Size
• Description: This configuration is there to restrict any external REST service response from exceeding the configured line

Timeout Settings​

The following settings are related to user session timeouts in the HTML and AIS server where the the recommendation is for the AIS timeout to be greater than the PD-HTML server timeout and the dedicated AIS-HTML server timeout should be greater than the AIS server timeout.

Timeout for AIS​

• Reference: AIS Session Token Life and Timeout Settings and How They Relate to HTML Timeout Settings (Doc ID 2522434.1)
• Link: AIS Instance -> View=Advanced -> Security Information.
• Settings:
  • SessionInactivityTimeoutMinutes
  • SessionTimeToLiveMinutes
• Description: There are two time out settings that are involved in an AIS session

Timeout for JAS (HTML Instance and AIS-HTML Dedicated instance)​

• Reference: AIS Session Token Life and Timeout Settings and How They Relate to HTML Timeout Settings (Doc ID 2522434.1)
• Link: HTML Instance -> View=Advanced -> Cache
• Settings:
  • UserSession
• Description: User Session cache timeout

Also, to be considered is the timeout setting within the HTML application server (in Weblogic this is found in the web.xml). See the following document for recommendations on increasing the timeout value in the application server. E1: JAS: Best Practices on Setting User Session Timeout Value for HTML Server ( JAS ) Instance Configured on Any Application Server (Doc ID 1488013.1)

UX One & Watchlists Performance​

• Reference: Question With the Architecture of the AIS Server in Relation to the HTML Servers (Doc ID 2239069.1)

• Link: HTML Instance -> View=Advanced -> Web Runtime

• Settings:

  • AIS Maximum Concurrent Calls

• Description: Control of how many AIS calls are processed at a time

• Link: AIS Instance -> View=Advanced -> Cache.

• Settings:

  • Read Cache Time to Live (Milliseconds)

• Description: How long responses are stored in cache

Orchestration Processing Performance Recommendations​

The primary load is on the HTML server. The AIS server is just a facilitator for the REST endpoints (nearly a pass through) to the HTML server where all of the forms and data queries are executed. So having a dedicated HTML server for AIS requests, or even a clustered set of HTML servers dedicated to AIS requests will provide the best sociability for AIS services/Orchestrations. (Don't use your "front-end" HTML server for AIS requests). Ensuring that both the AIS server and HTML server(s) are configured with the proper heap size is very important as well, for handling the load of many requests.

• Reference: Orchestration Processing Performance Recommendations (Doc ID 2587751.1)
• Add the argument for AIS instance under ServerStart -> Arguments to AIS and HTML instances to minimun and maximum of 4GB
• Settings:
  • -Xms4096m and -Xmx4096m

The URL for accessing our Demo platform for JD Edwards EnterpriseOne and Studio are as follows:

• EnterpriseOne: https://132.145.35.251:8080/jde/owhtml
• Studio: https://132.145.35.251:7077/studio
• Server Manager: https://132.145.35.251:8998/manage

Login Credentials​

Use the following credentials to access the instance:

# Login Credentials
User: demo
Password: nomana

Prerequisites​

Before starting, ensure you have the following:

• Oracle Cloud Account: An active subscription or free tier account with Oracle Cloud Infrastructure (OCI).

Steps to Deploy the JD Edwards Trial Edition​

1. Access the Oracle Cloud Marketplace​

1. Go to the Oracle Cloud Marketplace.
2. Search for JD Edwards EnterpriseOne Trial Edition.
3. Open the listing to view detailed information.

2. Deploy the Application​

1. Click the Get App button on the listing page.
2. Log in with your Oracle Cloud Single Sign-On credentials.
3. Accept the Oracle Cloud Marketplace Terms of Service.
4. Select your OCI compartment and click Launch Instance.

3. Configure the Instance​

1. Instance Details:
   • Enter a name for your instance.
   • Select the compartment where the instance will reside.

2. Compute Shape:
   • Choose a shape, such as VM.Standard2.4, that provides sufficient resources.

3. Networking:
   • Select an existing Virtual Cloud Network (VCN) and subnet or create a new one.
   • Assign a public IP address for external access.
4. SSH Keys:
   • Download SSH Key or upload your public SSH key to enable secure access to the instance.

4. Launch the Instance​

• Review all configuration settings.
• Click Create to launch the instance.

5. Access the JD Edwards Environment​

1. Once the instance is running, connect to it via SSH:

   ssh -i <path_to_private_key> opc@<instance_public_ip>
   

Follow the assistant to enter all informations related to the instance (port, password)

2. Open a web browser and navigate to the JD Edwards EnterpriseOne interface using the public IP address and port (default: 8080).

   Example URL:

   http://<instance_public_ip>:8080
   

3. Log in with the default credentials or any credentials provided during setup.

Additional Resources​

• JD Edwards EnterpriseOne Trial Edition - Oracle Cloud Marketplace
• Oracle Cloud Infrastructure Documentation

Next Steps​

After successfully deploying the trial instance, you can explore JD Edwards EnterpriseOne features such as:

• Configuring modules for your business needs.
• Testing integrations with other Oracle Cloud applications.
• Evaluating its scalability and performance in the cloud.

For further assistance, refer to the official documentation or consult Oracle support.

What's Included in the Site​

The provided MkDocs Material configuration is designed to support a comprehensive documentation site with the following features:

• Navigation:

  • Multi-level navigation with tabs and collapsible sections.
  • Support for documentation, guides, blog posts, API references, and release notes.

• Customization:

  • Custom logo and favicon.
  • Light and dark themes with a toggle switch.
  • Customizable color palettes to match your branding.

• Enhanced User Experience:

  • Instant navigation with prefetching for fast transitions.
  • Sticky top navigation for ease of access.
  • Copy button for code snippets to improve developer productivity.

• Plugins:

  • awesome-pages: Automatically organizes navigation based on folder structure.
  • minify: Optimizes site assets for faster loading.
  • blog: Supports structured and visually appealing blog posts.
  • search: Integrated full-text search for quick access to content.

• Content Types:

  • Documentation sections for getting started, installation guides, and tutorials.
  • Blog posts with structured navigation and metadata.

• Technical Enhancements:

  • Cookie consent settings to comply with privacy policies.
  • CSP (Content Security Policy) meta tag for enhanced security.
  • Custom CSS and JavaScript to further tailor the site's appearance and functionality.

Repository Features​

The repository includes:

1. A complete mkdocs.yml configuration with navigation, theme, and plugin settings.
2. A docs/ directory with pre-structured files and folders for easy customization.
3. Workflow configuration (.github/workflows/deploy.yml) to automate deployment to GitHub Pages.
4. Sample blog posts, API documentation, and guides to demonstrate how to structure content.
5. Custom assets for branding, including a logo and favicon.

By cloning this repository, you can start with a fully functional MkDocs Material site and focus on adding your content instead of setting up the structure.

Step 1: Prerequisites​

Before starting, ensure you have the following:

• Python 3.x installed (verify with python --version).

• pip installed (verify with pip --version).

• A GitHub repository to host your documentation.

• Git configured locally with a GitHub personal access token if needed.

Step 2: Install MkDocs Material​

1. Create a Virtual Environment (optional but recommended):

   python -m venv venv
   source venv/bin/activate # On Windows, use venv\Scripts\activate
   

2. Install MkDocs Material:

   pip install mkdocs-material
   

3. Verify Installation:

   mkdocs --version
   

Step 3: Create the MkDocs Project​

1. Create a New MkDocs Project:

   mkdocs new my-project
   cd my-project
   

2. Edit the mkdocs.yml File: Replace the default configuration with the following:

   site_name: Your Site Name
   site_url: Your Site URL
   
   theme:
     name: material
     logo: assets/your_logo.png
     favicon: assets/your_logo.png
     custom_dir: overrides
     palette:
       - media: "(prefers-color-scheme: light)"
         primary: blue grey
         accent: amber
         scheme: default
         toggle:
           icon: material/weather-night
           name: Switch to dark mode
       - media: "(prefers-color-scheme: dark)"
         primary: blue grey
         accent: amber
         scheme: slate
         toggle:
           icon: material/weather-sunny
           name: Switch to light mode   
     features:
       - content.code.copy     
       - navigation.instant
       - navigation.tabs
       - navigation.path
       - navigation.top
       - navigation.footer
       - header.autohide
   
   # example of navigation
   nav:
     - Home: index.md
     - Liberty:
         - Getting Started: liberty/getting-started.md
         - Installation:
           - Architecture: liberty/technical/architecture.md
           - Docker Installation Guide: liberty/technical/installation.md
           - Installation Tools Deployment Guide: liberty/technical/tools-deployment.md
           - Liberty Deployment Guide: liberty/technical/liberty-deployment.md
           - Create Linux Services: liberty/technical/linux-services.md
           - Enable SSL with Traefik: liberty/technical/post-ssl.md    
     - Blog:
       - blog/index.md
   
   plugins:
     - search
     - awesome-pages
     - minify
     - blog
   
   extra:
     social:
       - icon: fontawesome/brands/github
         link: your social link for github
       - icon: fontawesome/brands/linkedin
         link: your social link for linkedin          
     meta:
         - name: Content-Security-Policy
           value: frame-ancestors 'self' https://giscus.app;      
     consent:
       title: Cookie consent
       actions:
         - accept
         - manage
         - reject
       description: >- 
         We use cookies to recognize your repeated visits and preferences,
         as well as to measure the effectiveness of our documentation.
     markdown_extensions:
       - attr_list
       - pymdownx.highlight:
           anchor_linenums: true
           linenums: true
           line_spans: __span
           pygments_lang_class: true
       - pymdownx.inlinehilite
       - pymdownx.snippets
       - pymdownx.superfences
   extra_css:
     - css/custom.css
   extra_javascript:
     - js/extra.js  
   copyright: >
     Copyright © 2024 Nomana-IT –
     <a href="#__consent">Change cookie settings</a>
   

3. Add Your Documentation Files: Organize your files under the docs/ folder as per the navigation structure defined in the mkdocs.yml.

Step 4: Deploy to GitHub Pages​

1. Set Up GitHub Actions: Add the following configuration in .github/workflows/deploy.yml:

   name: ci 
   on:
     push:
       branches:
         - master 
         - main
   permissions:
     contents: write
   jobs:
     deploy:
       runs-on: ubuntu-latest
       steps:
         - uses: actions/checkout@v4
         - name: Configure Git Credentials
           run: |
             git config user.name github-actions[bot]
             git config user.email 41898282+github-actions[bot]@users.noreply.github.com
         - uses: actions/setup-python@v5
           with:
             python-version: 3.x
         - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV 
         - uses: actions/cache@v4
           with:
             key: mkdocs-material-${{ env.cache_id }}
             path: .cache
             restore-keys: |
               mkdocs-material-
         - run: pip install mkdocs-material mkdocs-awesome-pages-plugin mkdocs-minify-plugin
         - run: mkdocs gh-deploy --force
   

2. Push Your Changes: Commit and push your project to the main branch of your GitHub repository:

   git add .
   git commit -m "Initial documentation setup"
   git push origin main
   

3. Access Your Site: After GitHub Actions finish deploying, your site will be live at:

   https://<your-github-username>.github.io/<repository-name>/
   

Conclusion​

Your MkDocs Material documentation is now installed and deployed with GitHub Pages! This workflow ensures automated deployment and a professional look for your documentation site.

1. Gather locks for current session​

SELECT
  (select username || ' - ' || osuser from v$session where sid=a.sid) blocker,
  a.sid || ', ' || (select serial# from v$session where sid=a.sid) sid_serial,
 ' is blocking ',
  (select username || ' - ' || osuser from v$session where sid=b.sid) blockee,
  b.sid || ', ' || (select serial# from v$session where sid=b.sid) sid_serial
FROM 
  v$lock a, v$lock b
WHERE 
  a.block = 1
  AND b.request > 0
  AND a.id1 = b.id1
  AND a.id2 = b.id2;

1. Full size of the database​

SELECT  SUM(bytes/1024/1024/1024) FROM dba_segments 

2. Size by tablespace​

SELECT  OWNER, SUM(bytes/1024/1024/1024) FROM dba_segments 
GROUP BY owner
order BY owner;

3. Fragmented space for a schema​

SELECT 
  table_name,avg_row_len,round(((blocks*16/1024)),2)||'MB' "TOTAL_SIZE",
  round((num_rows*avg_row_len/1024/1024),2)||'Mb' "ACTUAL_SIZE",
  round(((blocks*16/1024)-(num_rows*avg_row_len/1024/1024)),2) ||'MB' "FRAGMENTED_SPACE",
  round((round(((blocks*16/1024)-(num_rows*avg_row_len/1024/1024)),2)/round(((blocks*16/1024)),2))*100,2) "percentage"
FROM 
  all_tables 
WHERE 
  owner='<OWNER>' 
  AND blocks>0;

1. List all profiles to retrieve the profile name​

SELECT * FROM DBA_SQL_PROFILES;

2. Create table with DBMS to export profile​

BEGIN
  DBMS_SQLTUNE.CREATE_STGTAB_SQLPROF (
    table_name  => 'TMP_SQL_PROFILES'
,   schema_name => 'SYSTEM'
);
END;

3. Export profile to the temporary table​

BEGIN
  DBMS_SQLTUNE.PACK_STGTAB_SQLPROF (
    profile_name         => 'SYS_SQLPROF_02701ab7b57c0000'
,   staging_table_name   => 'TMP_SQL_PROFILES'
,   staging_schema_owner => 'SYSTEM'
);
END;

Export/Import this table between both databases

4. Import profile from temporay table in the target database​

BEGIN
  DBMS_SQLTUNE.UNPACK_STGTAB_SQLPROF(
     replace            => true
,    staging_table_name => 'TMP_SQL_PROFILES'
);
END;

1. Gather statistics for a table​

BEGIN
 DBMS_STATS.GATHER_TABLE_STATS (ownname => '<OWNER>' , tabname => '<TABLE_NAME>',
  cascade => true, estimate_percent => 15,method_opt=>'for all indexed columns size 1', granularity => 'ALL', degree => 1);
END;

2. Gather statistics for a schema​

exec dbms_stats.gather_schema_stats( -
    ownname          => '<SCHEMA_NAME>', -
    options          => 'GATHER AUTO', -
    estimate_percent => dbms_stats.auto_sample_size, -
    method_opt       => 'for all columns size repeat', -
    degree           => 15 -
)