Rapid Install automates the installation of Oracle Applications Release 12 and simplifies both standard and advanced installations. It installs required technology stack components like Oracle Database 10g, Oracle Application Server, Oracle Developer and configures them. Preparing for Rapid Install involves creating operating system accounts, setting up a stage directory to copy installation files to shorten installation time, and validating the environment meets requirements.
This module discusses completing the installation of Oracle Applications by reviewing required post-installation tasks such as configuring client software and passwords, implementing product and country-specific functionality, and tasks specific to the installation such as setting up printers or resizing the database. It also covers logging into Oracle Applications and understanding system administration and maintenance tasks.
This document summarizes key environment files, server processes, languages, and character sets used in Oracle Applications. The main environment file is <CONTEXT_NAME>.env which specifies directories, parameters and other settings. Other important files include adovars.env, adconfig.txt, and fndenv.env. Server processes are started and stopped using scripts like adcmctl.sh. Languages are supported through language-specific directories. Character sets must be compatible across database, application, and desktop tiers.
The document outlines the steps for performing a standard Oracle E-Business Suite installation and an express installation. A standard installation involves 26 steps to configure the system, database, applications nodes, and perform the installation. An express installation provides a simplified single-user setup with default configurations in 6 steps.
This document discusses advanced configuration options for Oracle Applications, including using a shared application tier file system, load balancing options, and network design features. A shared file system allows all application tier nodes to access the same files, simplifying maintenance. Load balancing can distribute technology layers across machines for performance or resilience. Network topology, latency, links, and wireless connectivity all impact system design.
This module discusses several utilities for reporting and gathering information about an Oracle Applications system. It covers running the AD Configuration utility to report installation details, using AD File Identification to check file versions, and generating the AD Job Timing Report to analyze tasks run in parallel and identify long-running scripts. The AD Job Timing Report provides insights for reducing system downtime during maintenance.
Oracle E-Business Suite is an integrated suite of applications for e-business consisting of financials, manufacturing, CRM, HRMS and supply chain modules. It uses a Oracle database and file system to store applications and data. The suite has HTML and forms interfaces and uses concurrent processing. It is installed using the Rapid Install component which automates installation of required technology stack components like the Oracle database.
This document provides an overview of Oracle Applications AD Utilities, including:
- Identifying the AD utilities and their functions
- Using command line arguments and flags to configure the utilities
- Running utilities in parallel and viewing log files
- Understanding features like prompts, versions, and logging
This module discusses tasks for generating application files using Oracle Applications AD Administration. It describes logging into AD Administration, verifying prerequisites, and reviewing the main menu options. The main tasks covered are generating message, form, report, and product jar files, which create binary files needed by Oracle Applications from definition files. The process for each task prompts for options like products and files to generate and runs generation in parallel processes.
This module discusses completing the installation of Oracle Applications by reviewing required post-installation tasks such as configuring client software and passwords, implementing product and country-specific functionality, and tasks specific to the installation such as setting up printers or resizing the database. It also covers logging into Oracle Applications and understanding system administration and maintenance tasks.
This document summarizes key environment files, server processes, languages, and character sets used in Oracle Applications. The main environment file is <CONTEXT_NAME>.env which specifies directories, parameters and other settings. Other important files include adovars.env, adconfig.txt, and fndenv.env. Server processes are started and stopped using scripts like adcmctl.sh. Languages are supported through language-specific directories. Character sets must be compatible across database, application, and desktop tiers.
The document outlines the steps for performing a standard Oracle E-Business Suite installation and an express installation. A standard installation involves 26 steps to configure the system, database, applications nodes, and perform the installation. An express installation provides a simplified single-user setup with default configurations in 6 steps.
This document discusses advanced configuration options for Oracle Applications, including using a shared application tier file system, load balancing options, and network design features. A shared file system allows all application tier nodes to access the same files, simplifying maintenance. Load balancing can distribute technology layers across machines for performance or resilience. Network topology, latency, links, and wireless connectivity all impact system design.
This module discusses several utilities for reporting and gathering information about an Oracle Applications system. It covers running the AD Configuration utility to report installation details, using AD File Identification to check file versions, and generating the AD Job Timing Report to analyze tasks run in parallel and identify long-running scripts. The AD Job Timing Report provides insights for reducing system downtime during maintenance.
Oracle E-Business Suite is an integrated suite of applications for e-business consisting of financials, manufacturing, CRM, HRMS and supply chain modules. It uses a Oracle database and file system to store applications and data. The suite has HTML and forms interfaces and uses concurrent processing. It is installed using the Rapid Install component which automates installation of required technology stack components like the Oracle database.
This document provides an overview of Oracle Applications AD Utilities, including:
- Identifying the AD utilities and their functions
- Using command line arguments and flags to configure the utilities
- Running utilities in parallel and viewing log files
- Understanding features like prompts, versions, and logging
This module discusses tasks for generating application files using Oracle Applications AD Administration. It describes logging into AD Administration, verifying prerequisites, and reviewing the main menu options. The main tasks covered are generating message, form, report, and product jar files, which create binary files needed by Oracle Applications from definition files. The process for each task prompts for options like products and files to generate and runs generation in parallel processes.
This document discusses various file system administration tasks in Oracle Applications using AD Administration. It covers relinking applications programs, copying files to destinations, converting character sets, maintaining snapshot information, and checking for missing files. The tasks are associated with different application tier services like Forms, Web, and Concurrent Processing servers. Relinking should be done after installing patches or new components.
This document discusses advanced cloning options in Oracle Applications including refreshing a cloned target system, cloning single-node and multi-node systems, adding nodes to an existing system, and reducing nodes on a multi-node system. The key steps are preparing the source system, copying it to the target, and configuring the target. Cloning a multi-node system involves performing the clone process on each individual node.
Rapid Clone is a utility that can be used to clone an Oracle Applications system. The cloning process involves preparing the source system, copying it to the target system, and then configuring the target system. Some finishing tasks like updating profile options and instance-specific settings may also need to be completed.
The document describes the directory structure and file system of Oracle Applications. It discusses the roles and contents of key directories like INST_TOP, APPL_TOP, COMMON_TOP and product directories. It also covers the Applications context file, Java files, and database directories.
AutoPatch automates patch application and makes the process easier. It compares file versions, backs up files, copies new files, and updates databases. AutoPatch checks that prerequisites are met, is platform and language aware, and records patch history for applied patches. Applying patches with AutoPatch involves extracting patch files and using the patch driver file to update files and databases.
This module discusses various utilities in Oracle Applications including AD Controller, AD Relink, and upgrading processes. AD Controller allows monitoring and managing worker processes, restarting failed jobs, and shutting down workers. AD Relink relinks executable programs when needed. The supported upgrade paths to Release 12 are also outlined.
AutoConfig is a tool that centralizes and simplifies Oracle Applications configuration management. It works with Oracle Applications Manager to edit the Applications context file, which contains all configuration parameters. AutoConfig then generates configuration files and updates profiles by reading templates and the Applications context. Running AutoConfig propagates changes to both the application and database tiers. Its logs and rollback files allow monitoring runs and restoring previous configurations.
Oracle Applications uses a multi-tier architecture with desktop, application, and database tiers. The application tier utilizes various components like Forms Services, Concurrent Processing Server, and the Oracle Applications Framework to power both forms-based and HTML-based applications. The technology layer provides common services for all Oracle Applications modules through components like the Oracle Application Object Library, Oracle Applications Utilities, and Oracle Workflow.
This document discusses various modes and options for running the AutoPatch utility in Oracle Applications, including:
- Test mode runs validation and version checking but does not make changes.
- Pre-install mode updates utilities but does not run SQL or load drivers.
- Non-interactive mode runs AutoPatch without prompts using a defaults file.
- Command line options control behaviors like running in test mode, specifying drivers and directories, and enabling parallelization.
This document provides instructions on running the AutoPatch utility to apply Oracle Applications patches. It discusses setup tasks to perform before running AutoPatch like backing up files and databases. It then outlines the steps to run AutoPatch, including responding to prompts, specifying options like the number of workers, and viewing messages and logs after completion. Troubleshooting tips are provided in case AutoPatch fails or a worker encounters an error.
The document discusses database maintenance tasks in Oracle Applications including validating the APPS schema, recreating grants and synonyms for APPS schemas, maintaining multilingual tables, and checking the DUAL table. It provides instructions on running each task and reasons for running them such as after an upgrade, patch, or export/import.
This document provides instructions on using AD Utilities to install off-cycle products and convert file character sets in Oracle Applications. It describes how to use AD Splicer to register off-cycle products, edit required control files, and complete post-splice steps. It also explains how to use the adncnv utility to convert individual file character sets between encodings.
This document discusses running Oracle AD Administration utilities in non-interactive mode and enabling/disabling maintenance mode. It describes creating a defaults file to specify parameters for non-interactive execution. Maintenance mode must be enabled before patching to improve performance and restrict user access, and is toggled using the AD Administration menu option. The module teaches how to run AD Administration without interaction, change the maintenance mode status, and discusses the benefits of these functions.
The OAM Timing Reports utility provides details about AutoPatch and AD Administration maintenance sessions, including elapsed time for phases, jobs, and sessions. It displays summary and timing information for parallel jobs and sessions. The In-Progress AD Utility report allows tracking the progress of a patching session in restricted OAM mode.
The document discusses various tasks for compiling and reloading database entities in Oracle Applications using AD Administration. It describes compiling APPS schemas, which involves compiling invalid objects in the APPS schema. It also describes compiling menu information after making changes to menus, and compiling flexfield data, which is not usually required as flexfields automatically compile on first use but can be done to validate referential integrity. The final task covered is reloading JAR files to the database if all Java classes were removed.
1) The document describes the process of performing a homogeneous system copy in SAP using an online/offline database backup.
2) The key steps are preparing the target system, restoring the backup to the target, creating a control file script on the source, modifying and running it on the target, and recovering the database on the target.
3) The recovery process differs depending on whether the source was using archive logging and whether archives are available to make the target current.
Configuration of sap net weaver for oracle grid infrastructure 11.2 with orac...Graciete Martins
This document provides guidance on configuring an SAP system to work with Oracle Real Application Clusters 11g Release 2 (RAC). It describes the steps needed when migrating an existing single-instance Oracle database to RAC or upgrading an existing Oracle RAC 10g system. Key preparations include ensuring the database files are on shared storage, installing the Oracle Grid Infrastructure software locally on each node, and setting up user accounts and privileges for the Oracle and SAP users. The document then outlines the detailed configuration steps for installing Oracle RAC 11g, upgrading an existing database, and configuring the database, listeners, services and SAP-specific settings to support a RAC-enabled SAP system.
Oracle Applications files are installed under various top-level directories like APPL_TOP, COMMON_TOP, and ORA_TOP. APPL_TOP contains environment files, administrative files, and product directories. Each product directory contains subdirectories for administration, binaries, forms, logs, and more. Load balancing can be configured for Oracle Applications servers using session persistent or non-session persistent load balancers, with options for Forms and JServ traffic. Network latency and wireless connections impact Oracle Applications and can benefit from load balancing architectures.
SAP HANA System Replication - Setup, Operations and HANA MonitoringLinh Nguyen
SAP HANA Distributed System Replication setup, operations and associated HANA Monitoring of Disaster Recovery (DR) scenario using OZSOFT HANA Management Pack for SCOM
Oracle applications r12.2, ebr, online patching means lot of work for devel...Ajith Narayanan
This document discusses the implications of Oracle Applications R12.2's architecture and online patching capabilities for developers. It begins with introducing the speaker and providing an overview of R12.2's dual application tier architecture. It then covers key concepts around Edition Based Redefinition (EBR) and the rules and steps required for online patching. The main implications for developers are that objects must be uniquely named at 29 bytes or less, references to editioned objects require special handling, and code must work across editions that can change without warning during patching. Extra steps are required for table, seed data, view, trigger and other changes to support editions. Close coordination is needed when multiple developers are working concurrently.
This is a modest initiative for providing help to people who really want to boost their skills in Oracle Apps DBA, with special stress to the Administration area. The main reason behind this initiative has been the problems which we had faced when we ventured out to try our hands at Oracle Apps DB Administration.
This document provides an overview of Oracle's Patch Wizard tool. It describes how to access Patch Wizard, set up preferences like defining a stage directory, define patch filters, submit and view Patch Wizard requests, and analyze results including patch impact analysis. Key steps include downloading the Patch Information Bundle, setting up custom filters to select relevant patches, submitting requests to get patch recommendations or analyze specific patches, and viewing the job status and results including prerequisite patches and file impacts.
This document discusses various file system administration tasks in Oracle Applications using AD Administration. It covers relinking applications programs, copying files to destinations, converting character sets, maintaining snapshot information, and checking for missing files. The tasks are associated with different application tier services like Forms, Web, and Concurrent Processing servers. Relinking should be done after installing patches or new components.
This document discusses advanced cloning options in Oracle Applications including refreshing a cloned target system, cloning single-node and multi-node systems, adding nodes to an existing system, and reducing nodes on a multi-node system. The key steps are preparing the source system, copying it to the target, and configuring the target. Cloning a multi-node system involves performing the clone process on each individual node.
Rapid Clone is a utility that can be used to clone an Oracle Applications system. The cloning process involves preparing the source system, copying it to the target system, and then configuring the target system. Some finishing tasks like updating profile options and instance-specific settings may also need to be completed.
The document describes the directory structure and file system of Oracle Applications. It discusses the roles and contents of key directories like INST_TOP, APPL_TOP, COMMON_TOP and product directories. It also covers the Applications context file, Java files, and database directories.
AutoPatch automates patch application and makes the process easier. It compares file versions, backs up files, copies new files, and updates databases. AutoPatch checks that prerequisites are met, is platform and language aware, and records patch history for applied patches. Applying patches with AutoPatch involves extracting patch files and using the patch driver file to update files and databases.
This module discusses various utilities in Oracle Applications including AD Controller, AD Relink, and upgrading processes. AD Controller allows monitoring and managing worker processes, restarting failed jobs, and shutting down workers. AD Relink relinks executable programs when needed. The supported upgrade paths to Release 12 are also outlined.
AutoConfig is a tool that centralizes and simplifies Oracle Applications configuration management. It works with Oracle Applications Manager to edit the Applications context file, which contains all configuration parameters. AutoConfig then generates configuration files and updates profiles by reading templates and the Applications context. Running AutoConfig propagates changes to both the application and database tiers. Its logs and rollback files allow monitoring runs and restoring previous configurations.
Oracle Applications uses a multi-tier architecture with desktop, application, and database tiers. The application tier utilizes various components like Forms Services, Concurrent Processing Server, and the Oracle Applications Framework to power both forms-based and HTML-based applications. The technology layer provides common services for all Oracle Applications modules through components like the Oracle Application Object Library, Oracle Applications Utilities, and Oracle Workflow.
This document discusses various modes and options for running the AutoPatch utility in Oracle Applications, including:
- Test mode runs validation and version checking but does not make changes.
- Pre-install mode updates utilities but does not run SQL or load drivers.
- Non-interactive mode runs AutoPatch without prompts using a defaults file.
- Command line options control behaviors like running in test mode, specifying drivers and directories, and enabling parallelization.
This document provides instructions on running the AutoPatch utility to apply Oracle Applications patches. It discusses setup tasks to perform before running AutoPatch like backing up files and databases. It then outlines the steps to run AutoPatch, including responding to prompts, specifying options like the number of workers, and viewing messages and logs after completion. Troubleshooting tips are provided in case AutoPatch fails or a worker encounters an error.
The document discusses database maintenance tasks in Oracle Applications including validating the APPS schema, recreating grants and synonyms for APPS schemas, maintaining multilingual tables, and checking the DUAL table. It provides instructions on running each task and reasons for running them such as after an upgrade, patch, or export/import.
This document provides instructions on using AD Utilities to install off-cycle products and convert file character sets in Oracle Applications. It describes how to use AD Splicer to register off-cycle products, edit required control files, and complete post-splice steps. It also explains how to use the adncnv utility to convert individual file character sets between encodings.
This document discusses running Oracle AD Administration utilities in non-interactive mode and enabling/disabling maintenance mode. It describes creating a defaults file to specify parameters for non-interactive execution. Maintenance mode must be enabled before patching to improve performance and restrict user access, and is toggled using the AD Administration menu option. The module teaches how to run AD Administration without interaction, change the maintenance mode status, and discusses the benefits of these functions.
The OAM Timing Reports utility provides details about AutoPatch and AD Administration maintenance sessions, including elapsed time for phases, jobs, and sessions. It displays summary and timing information for parallel jobs and sessions. The In-Progress AD Utility report allows tracking the progress of a patching session in restricted OAM mode.
The document discusses various tasks for compiling and reloading database entities in Oracle Applications using AD Administration. It describes compiling APPS schemas, which involves compiling invalid objects in the APPS schema. It also describes compiling menu information after making changes to menus, and compiling flexfield data, which is not usually required as flexfields automatically compile on first use but can be done to validate referential integrity. The final task covered is reloading JAR files to the database if all Java classes were removed.
1) The document describes the process of performing a homogeneous system copy in SAP using an online/offline database backup.
2) The key steps are preparing the target system, restoring the backup to the target, creating a control file script on the source, modifying and running it on the target, and recovering the database on the target.
3) The recovery process differs depending on whether the source was using archive logging and whether archives are available to make the target current.
Configuration of sap net weaver for oracle grid infrastructure 11.2 with orac...Graciete Martins
This document provides guidance on configuring an SAP system to work with Oracle Real Application Clusters 11g Release 2 (RAC). It describes the steps needed when migrating an existing single-instance Oracle database to RAC or upgrading an existing Oracle RAC 10g system. Key preparations include ensuring the database files are on shared storage, installing the Oracle Grid Infrastructure software locally on each node, and setting up user accounts and privileges for the Oracle and SAP users. The document then outlines the detailed configuration steps for installing Oracle RAC 11g, upgrading an existing database, and configuring the database, listeners, services and SAP-specific settings to support a RAC-enabled SAP system.
Oracle Applications files are installed under various top-level directories like APPL_TOP, COMMON_TOP, and ORA_TOP. APPL_TOP contains environment files, administrative files, and product directories. Each product directory contains subdirectories for administration, binaries, forms, logs, and more. Load balancing can be configured for Oracle Applications servers using session persistent or non-session persistent load balancers, with options for Forms and JServ traffic. Network latency and wireless connections impact Oracle Applications and can benefit from load balancing architectures.
SAP HANA System Replication - Setup, Operations and HANA MonitoringLinh Nguyen
SAP HANA Distributed System Replication setup, operations and associated HANA Monitoring of Disaster Recovery (DR) scenario using OZSOFT HANA Management Pack for SCOM
Oracle applications r12.2, ebr, online patching means lot of work for devel...Ajith Narayanan
This document discusses the implications of Oracle Applications R12.2's architecture and online patching capabilities for developers. It begins with introducing the speaker and providing an overview of R12.2's dual application tier architecture. It then covers key concepts around Edition Based Redefinition (EBR) and the rules and steps required for online patching. The main implications for developers are that objects must be uniquely named at 29 bytes or less, references to editioned objects require special handling, and code must work across editions that can change without warning during patching. Extra steps are required for table, seed data, view, trigger and other changes to support editions. Close coordination is needed when multiple developers are working concurrently.
This is a modest initiative for providing help to people who really want to boost their skills in Oracle Apps DBA, with special stress to the Administration area. The main reason behind this initiative has been the problems which we had faced when we ventured out to try our hands at Oracle Apps DB Administration.
This document provides an overview of Oracle's Patch Wizard tool. It describes how to access Patch Wizard, set up preferences like defining a stage directory, define patch filters, submit and view Patch Wizard requests, and analyze results including patch impact analysis. Key steps include downloading the Patch Information Bundle, setting up custom filters to select relevant patches, submitting requests to get patch recommendations or analyze specific patches, and viewing the job status and results including prerequisite patches and file impacts.
The document provides an overview of License Manager, which is used to register products, country-specific functionalities, and languages. It describes accessing License Manager and the various registration options for registering the Oracle E-Business Suite, component applications, individual products, additional functionalities, and languages. It also discusses the License Manager reports that are available.
The document discusses Oracle's Applied Patches feature which allows users to view information about patches that have been applied to an Oracle system. It stores details like the patch number, files changed, and whether the patch was successfully applied. Users can search for applied patch and file history information using simple and advanced search pages. There are also several reports that provide more details on patches, files copied, bug fixes, and timing information for applied patches. The mode used to apply patches via AutoPatch (normal, test, pre-install) determines how patch information is recorded and uploaded to the database.
OOW15 - Online Patching with Oracle E-Business Suite 12.2vasuballa
The Online Patching feature of Oracle E-Business Suite 12.2 will reduce your Oracle E-Business Suite patching downtime to however long it takes to bounce your application server. This Oracle development session details how online patching works, with special attention given to what is happening at the database object level, where patches are applied to an Oracle E-Business Suite environment that is still running. Come learn about the operational and system management implications for minimizing maintenance downtime when applying Oracle E-Business Suite patches with this new technology, and the related impact on customizations you might have built on top of Oracle E-Business Suite.
Developer & Fusion Middleware 2 _ Scott Robertson _ SOA, Portals and Enterpri...InSync2011
The document discusses an Employee Self Service (ESS) application created using Oracle SOA, portals, and JD Edwards for the construction company Thiess. ESS allows employees to maintain their personal details stored in JDE and integrates with a third party payroll system. Key points:
1) ESS was initially a Java web application later converted to portlets for use in a portal. This conversion caused some functionality issues.
2) ESS integrates with an external payroll system using file-based FTP integration for importing/exporting employee data and payments.
3) Testing the integration was difficult due to lack of real-time web services from the third party and performance issues when importing large amounts of
The Oracle Applications database contains various objects like tables, views, indexes, and sequences across multiple schemas. Key schemas include APPS for common objects and product-specific schemas. Oracle database features such as query optimization, partitioning, and Real Application Clusters are used. Scripts in the database ORACLE_HOME directory are used to start and stop database processes.
Obia11.1.1.10.1 installation and configuration on Unix platformSheikh Zakirulla
The document describes the steps for installing Oracle BI Applications (OBIA) 11.1.1.10.1 including:
1. Installing prerequisite software like the Oracle database, Java, and other Oracle BI components.
2. Running the Repository Creation Utility to create schemas.
3. Installing and configuring OBIA, applying patches, and configuring the installation.
4. Creating connections in Oracle Data Integrator for the master repository and work repositories.
The document provides an overview of best practices for planning, implementing, operating and monitoring an Oracle Real Application Clusters (RAC) environment on Linux. It discusses hardware and software considerations, installation procedures, database creation, application deployment, operational practices like backup/recovery, and performance monitoring and tuning strategies. The presentation also covers migrating the RAC environment to production.
This document provides instructions for installing Oracle Applications R12 (12.1.3) on Linux (64-bit). It describes downloading and unzipping the installation files, performing pre-install tasks like configuring disk space, installing required RPMs and setting kernel parameters, and running the ./rapidwiz installation script. It also covers post-installation tasks like setting environment variables and default passwords. Upgrading an existing EBS 12.1.3 installation is also addressed.
This document outlines the steps to install and configure Oracle Business Intelligence 10g and integrate it with Oracle E-Business Suite 11i. It includes pre-install tasks like applying required patches, creating an inventory directory and running rootpre.sh. The main steps are running the installer to create an Oracle home, configure ports, provide mail server details and set the ias_admin password. Post-installation, it describes copying the DBC file from E-Business to BI, changing the server name in httpd.conf and setting ownership of the DBC file. TNS entries are also created to connect BI to the E-Business database.
This guide describes how to quickly install Oracle Database Client on 32-bit Windows, including requirements for hardware, software, and creating an Oracle Home user, as well as instructions for using Oracle Universal Installer to perform the installation and next steps after installation is complete.
This document provides an overview and instructions for installing Weblogic Server 12c. It outlines the installation process, including preparing for installation by determining prerequisites, temporary disk space requirements, and user privileges. The document also describes different installation modes like GUI, console, and silent modes and post-installation tasks like creating a Weblogic domain.
This document provides instructions for quickly installing Oracle Database 12c Release 1 on Windows x64 systems:
- It describes configuring the system to meet hardware and software requirements, installing the Oracle Database software, and validating a successful installation.
- The typical installation will require a minimum of 2GB RAM, 10GB disk space, and supported versions of Windows and compilers.
- The installation creates several OS groups like ORA_DBA and ORA_ASMADMIN to manage privileges and provides options for specifying an Oracle Home user.
1. The document provides installation instructions for Oracle Database Client 12c Release 1 (12.1) on Microsoft Windows x64 systems.
2. It describes the hardware and software requirements, default share configuration requirement, and the process for installing the Oracle Database Client software using Oracle Universal Installer.
3. The installation types covered are Instant Client, Administrator, Runtime, and Custom. Guidelines are provided for a default installation into a new Oracle home directory.
This document provides step-by-step instructions for installing DSpace on Windows. It covers downloading and installing prerequisite software like Java, Apache Maven, Apache Ant, Apache Tomcat, and PostgreSQL. It then guides the user through configuring DSpace, building the DSpace installation package using Maven, and deploying DSpace on Tomcat. The 10 steps include setting environment variables, creating a PostgreSQL database, editing DSpace configuration files, running Maven and Ant commands, and starting Tomcat to access the installed DSpace instance.
This document provides instructions for quickly installing Oracle Database Client 12c Release 1 (12.1) on Linux x86-64 systems. It describes the installation types, requirements for the Linux operating system, and steps for installing Oracle software including configuring servers, creating required users and groups, mounting the product disc, and installing Oracle Database Client.
This document provides instructions for quickly installing Oracle Database Client 12c on Oracle Solaris on SPARC (64-bit) systems. It reviews requirements such as verifying the operating system packages and patches, configuring users and directories, and describes the installation process which includes mounting the product disc and running the Oracle Universal Installer. It also provides additional resources for more detailed installation instructions.
Introduction to-release-11i-part-1-of-2-installation3771Mlx Le
The document provides an overview of Oracle Applications Release 11i, including its architecture, components, installation considerations, and environment management best practices. It discusses the move to a true three-tier architecture with forms, Java, and Apache components. It also outlines the software and hardware sizing recommendations for servers and desktops to optimally run Release 11i.
This document provides instructions for installing Oracle Database Client 12c on IBM AIX on POWER Systems (64-bit). It describes reviewing information, logging in as root, configuring servers, checking requirements and installing Oracle software. Operating system requirements include supported versions of AIX 6.1, 7.1 and 7.2, required filesets and APAR fixes. Additional drivers, software and requirements for connectivity, messaging and programming environments are also listed.
The document provides instructions for quickly installing Oracle Database Client 12c Release 1 (12.1) on HP-UX Itanium systems. It describes logging in as the root user, configuring servers by checking hardware requirements and installing required patches. It also reviews security practices and checks software requirements before installing the Oracle Database Client.
This document provides instructions for installing Oracle Database Client 12c on Oracle Solaris on x86-64 systems. It describes reviewing requirements, configuring the system, installing necessary packages and patches, and performing the installation. Key steps include verifying the operating system release and packages, configuring sufficient disk space, memory and swap space, and installing required drivers before installing the Oracle Database Client software.
1. The document provides procedures for backing up a production server, including cloning the production server to create a backup server and daily and monthly backup procedures.
2. Key steps in cloning the production server include shutting down databases and applications, copying files to the backup server, and running scripts to configure the database and applications.
3. Daily backups involve making copies of updated database files from the production server to the backup server and reconfiguring the database. Monthly backups also update applications if any patches were applied.
The document outlines best practices for routinely backing up a production server to ensure data is not lost by maintaining a cloned backup server and regularly updating databases and applications.
This document provides instructions on installing and configuring the LAMP stack on Linux. It discusses downloading and installing Linux, Apache, MySQL, and PHP. It explains how to partition disks for installation, set up virtual hosts, and configure Apache's configuration files and ports. The key steps are downloading Linux distributions, burning ISO images, partitioning disks, selecting packages during installation, configuring Apache's files, ports, and virtual hosts.
This document provides instructions for installing Oracle Database Client 12c Release 1 (12.1) on IBM: Linux on System z. It describes the requirements including supported operating system distributions, packages, hardware requirements and instructions for installing Oracle software. Key requirements include a minimum of 256MB RAM, 400MB free disk space in /tmp, supported distributions of Red Hat Enterprise Linux 5/6 or SUSE Linux Enterprise Server 11, and required packages specific to each distribution. The document provides detailed steps for logging in as root, configuring servers, and installing Oracle Database Client.
What’s New in Oracle E-Business Suite R12.2 for Database Administrators?vasuballa
This document provides an overview of new features in Oracle E-Business Suite R12.2 for database administrators. It discusses changes to the file system layout, new online patching capabilities using Edition-Based Redefinition, and changes to cloning procedures. The presentation also covers WebLogic architecture updates, simplified installation processes including support for Oracle RAC and ASM, and other miscellaneous changes.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
Physiology and chemistry of skin and pigmentation, hairs, scalp, lips and nail, Cleansing cream, Lotions, Face powders, Face packs, Lipsticks, Bath products, soaps and baby product,
Preparation and standardization of the following : Tonic, Bleaches, Dentifrices and Mouth washes & Tooth Pastes, Cosmetics for Nails.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
Main Java[All of the Base Concepts}.docxadhitya5119
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
How to Add Chatter in the odoo 17 ERP ModuleCeline George
In Odoo, the chatter is like a chat tool that helps you work together on records. You can leave notes and track things, making it easier to talk with your team and partners. Inside chatter, all communication history, activity, and changes will be displayed.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
Introduction to AI for Nonprofits with Tapp NetworkTechSoup
Dive into the world of AI! Experts Jon Hill and Tareq Monaur will guide you through AI's role in enhancing nonprofit websites and basic marketing strategies, making it easy to understand and apply.
5. Rapid Install Database File System Applications Technology Stack Rapid Install Oracle Application Server 10.1.2 ORACLE_HOME Oracle Application Server 10.1.3 ORACLE_HOME
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22. Set Up Stage Directory oraDB/Diskn RDBMS - Disk n oraAS/Diskn Tools - Disk n oraAppDB/Diskn Databases - Disk n APPL_TOP - Disk n Start Here - Disk 1 Disks labeled... startCD/Disk1 oraApps/Diskn Are copied to this directory...
35. Running Rapid Install Database File System Applications Technology Stack Rapid Install Oracle Forms Oracle10 g Web Server [Other Components]
36.
37.
38.
39.
40.
41.
42.
Editor's Notes
Schedule: Timing Topic 40 minutes Lecture 30 minutes Practice 70 minutes Total
<Course name> <Lesson number> -
<Course name> <Lesson number> - Overview This module discusses Rapid Install and its key role in the installation of Oracle Applications Release 12.
<Course name> <Lesson number> - Rapid Install With Rapid Install, you can perform the following tasks: Install a new, fully configured Oracle Applications system, including the latest certified technology stack, patches, and other updates available at the time of release Lay down the file system and configure server processes for an upgraded system Install a new database node or Applications node technology stack
<Course name> <Lesson number> - Rapid Install Rapid Install lays down each of the components shown in this slide: Oracle database, including all necessary database files Applications technology stack, which includes two different Oracle Application Server (OracleAS) 10g releases, installed in separate ORACLE_HOMEs. This strategy enables Oracle Applications to take advantage of the latest technologies, and is described further on the following slides. Oracle Applications file system, including new Instance Top ($INST_TOP)
Technology Stack Components A multi-node installation of Release 11i required each application tier to maintain its own file system, consisting of the APPL_TOP file system (APPL_TOP, COMMON_TOP, and a few related directories) and the application tier technology stack file system (8.0.6 ORACLE_HOME and iAS ORACLE_HOME). Later, the Release 11.5.10.2 Rapid Install introduced support for a shared file system. In Release 12, Rapid Install will by default create a system that shares the application tier file system as well as the APPL_TOP and COMMON_TOP file systems. The application tier file system can therefore be shared across multiple application tier nodes (provided they are running the same operating system). Instructor Note: Strictly speaking, the operating systems of nodes sharing a file system must be binary compatible rather than necessarily identical. However, it is recommended that all relevant nodes do use identical operating systems (including versions).
Oracle Developer 10 g The Applications node technology stack includes Oracle Developer 10g, which includes : Oracle Forms Oracle Reports (only for use with Concurrent Processing, not a stand-alone server) The Developer products are installed in the Application Server 10.1.2 Oracle Home directory, which is sometimes also referred to as the Tools Oracle Home or C Oracle Home.
Oracle HTTP Server The Application Server 10.1.3 ORACLE_HOME directory is used for the Oracle HTTP Server. It is sometimes also referred to as the Web Oracle Home or Java ORACLE_HOME.
<Course name> <Lesson number> - Key Changes This slide summarizes the main changes to the Applications technology stack in Release 12. Instructor Note: T he move from Oracle JDeveloper 9i to 10g is significant for developers, in the context of Oracle Applications Framework.
<Course name> <Lesson number> - Release 12 Platforms It is essential to review the relevant platform-specific Installation Update Note prior to performing the installation. These are available on Oracle MetaLink as follows: Sun Solaris (SPARC) – Note 402312.1 Linux 32-bit – Note 402310.1 Linux 64-bit – Note 416305.1 Microsoft Windows – Note 402311.1 HP-UX (PA-RISC) – Note 402308.1 HP-UX (Itanium) – Note 402307.1 IBM AIX 5L – Note 402306.1
Software Requirements The utilities shown on the slide must be included in the PATH variable of the user account that is to run the Rapid Install wizard. X Display Server This display must always be accessible during runtime. Set it to an active and authorized X Windows display, pointing to a machine that is always available to the instance. For more details, see OracleMetaLink Note 153960.1, X Server Testing and Troubleshooting . Specific Requirements for Windows Release 12 has additional software requirements for Windows: Microsoft Visual C++ 8.0 (http://www.microsoft.com) gnu make (shareware) Version 3.81 (http://www.gnu.org). Obtainable via Oracle patch 5897842, which contains the source files and the pre-built executable file, gnumake.exe MKS Toolkit Version 9 (Patch 3) or higher (http://www.mks.com) Free software from Cygwin (http://www.cygwin.com) can be used instead of MKS Toolkit to provide the UNIX scripting commands needed for the AD utilities. However, Oracle recommends using the MKS Toolkit for all critical systems.
CPU Requirements Because there are different product combinations, different user profiles, and different configurations, there is no one sizing answer for all hardware platforms. Some hardware vendors have sizing worksheets that model the CPU and memory requirements of Oracle Applications on their hardware. The most reliable strategy to ensure that the hardware is sized appropriately is to install a test environment, and then set a benchmark with a configuration, product mix, and user load that simulates your own current and expected workloads. These &quot;actual“ conditions can help verify performance before you install your production-ready environment. If such a benchmark is not feasible, Oracle Consulting Services and your hardware vendor can help you find another Oracle Applications system running a product mix and user profile similar to yours.
Memory Requirements In carrying out the calculations on the slide, you should aim to allow for any expected growth in usage over the planned lifetime of this Applications system, although the increasing usage of Oracle Real Application Clusters and related technologies means that it is now easier to scale up a system by adding another machine.
Disk Space Requirements (File System) Rapid Install installs the file system and database files for all products, regardless of their licensed status. The size of the application tier file system objects is approximately 28 GB. This includes the OracleAS 10.1.2 ORACLE_HOME, OracleAS 10.1.3 ORACLE_HOME, COMMON_TOP, APPL_TOP, and INST_TOP. The disk size required for the database tier files is approximately 45 GB for a fresh install database and 133 GB for a Vision Demo database. Stage area: If you run Rapid Install from a stage area, you need at least 33 GB to accommodate the file system and database files in your stage area. Applications log and output files: Many Oracle Applications products generate log and output files during runtime. The disk space needed for log and output files varies with the number of users and usage, and depends on how frequently you purge these files. Log and output files are not automatically purged. It is advisable to determine a strategy for archiving and purging these files after the installation, and monitor the disk space they consume to determine how much space you may need in the future.
Disk Space Requirements (File System) Temporary directories and files: For installation time temporary disk space, Rapid Install uses the temporary directory defined by the TMPDIR variable (on UNIX) or TEMP and TMP variables (on Windows). You should ensure there is at least 500 MB of free temporary space when carrying out an installation. Oracle Applications also requires temporary runtime disk space. For example, each concurrent manager writes temporary parameter files and Oracle Forms writes temporary record buffers. Rapid Install sets the temporary directory to the value you supply on the derived settings screen. Rapid Install sets the temporary directory based on the value you supply on node-specific settings screens. Updates and patches: You need disk space for applying updates, patches, maintenance packs, family packs, and mini-packs, as well as backup copies of files that may be created when applying an update or patch. Other files: The total disk space estimate must account for the requirements of files other than those required by Oracle Applications directly. For example: Operating system software Online backups Custom Applications development files
Stage Area For a production database install, running Rapid Install from a stage area requires at least 33 GB to accommodate the file system and database files in the stage area.
Create Login Accounts (UNIX) Single-user installations: To install Oracle Applications in a single-user installation, create an oracle user account and log in as this user to run Rapid Install. Multi-user installations: To install in a multi-user installation, you can assign one user account to be the owner of the database node file system, and another to be the owner of the Applications node file system, by creating an oracle user account and an applmgr user account. The operating system user that owns the Oracle database Oracle Home and the Oracle Applications database is called the oracle user. The oracle user owns the database node technology stack (10g R2 ORACLE_HOME), and the database files. The operating system user that owns the Oracle Applications file system is called the applmgr user. The applmgr user owns the Applications node technology stack (APPL_TOP, COMMON_TOP, 10.1.2 ORACLE_HOME, and 10.1.3 ORACLE HOME). Log in as root to run Rapid Install, then specify the oracle user as the owner of the database ORACLE_HOME and the applmgr user as the owner of the APPL_TOP. The multi-account strategy helps to enhance security and auditability.
Create Login Accounts (Windows) On Windows platforms, the user who runs Rapid Install owns the file system for all components (both the database file system and the Oracle Applications file system). The Windows installation is equivalent to the UNIX single-user installation. Before you install Oracle Applications, ensure the user account for the installation (the install user) has full local administrative privileges and permission to print to either local or network printers. We recommend you create a new account (for example, oracle) on the domain level and make it a member of these groups: Administrators (local user) Domain Users (domain user) This account does not need to be a member of any other group, and must not be a member of the Guest group. Refer to Windows Help for information on creating accounts and assigning accounts to groups.
Set Up a Stage Directory For optimal performance, run Rapid Install from a stage area . You do this by running a Perl script that creates the install directory and copies the contents of the Release 12 software bundle to a designated location in the file system. The Rapid Install DVDs in the Release 12 software bundle are labeled: Start Here APPL_TOP RDBMS Tools Databases
Set Up a Stage Directory Follow these steps to set up a stage area installation: Log in as a user with enough privilege to mount (and unmount) DVDs, and to write to the chosen stage area. Insert the Start Here disk in the DVD-ROM drive. Mount the DVD (conditional, depending on platform) If your system runs on a UNIX platform, and if you do not use AutoMount, you must mount the Start Here disk now. Confirm you have perl 5.0053 installed and in your PATH. (Windows users: the perl shipped by MKS is not certified. Use ActivePerl, which you can download from http://perl.com.) On UNIX platforms, set the DISPLAY environment variable to an active and authorized display. Run the adautostg.pl script, following these examples and substituting your own paths and drive letters as applicable: UNIX: $ cd $ perl /mnt/dvdrom/Disk1/rapidwiz/adautostg.pl Windows: D:\\> perl d:\\mnt\\dvdrom\\Disk1\\rapidwiz\\adautostg.pl
Set Up a Stage Directory Follow these steps to set up a stage area installation: Set up the stage area directory. At the prompt for the stage directory, enter the name of the system top-level directory. The Rapid Install Stage12 directory will be created in this path. For example, if you enter /u01 as the top-level directory, the resulting directory path will be /u01/stage12. Indicate the components to be staged. The script prompts you for the components that you want to stage. For example, you can indicate that you want to stage only the database technology stack, only the APPL_TOP, and so on. The default is the first option listed, to stage all Oracle Applications components. Install the relevant DVDs, as prompted. A system message lists the files copied and their location in the stage area directory.
Set Up a Stage Directory The number of disks for each label may vary between platforms. Installation directories are case-sensitive, and are set up using the capitalization exactly as shown.
Set Up a Stage Directory The example in the slide shows a top level directory of Stage12, with subdirectories startCD, oraApps, oraDB, oraAS, and oraAppDB..
Run Rapid Install from the Disks Oracle does not recommend running Rapid Install from the DVDs, as the install will take longer. Instructor Note: Oracle does not recommend customers to run Rapid Install from the disks. It is much slower and requires the disks to be changed during the install process. This option should only be considered if a lack of disk space precludes the creation of a stage directory.
Using an Alias for the Host Machine If you want to use an alias (not the actual name of your host machine), you can use the -servername command line option when you start Rapid Install. Instructor Note: A DNS alias is a host name that points to another host name. Each node where you install Applications can have only one real name, but it can have more than one alias. Creating a DNS alias allows you to change the actual host name or IP address of the server machine without having to change the proxy settings for the clients that use the proxy.
How an Installation Works Rapid Install installs Oracle Applications products by providing a wizard for entering information specific to your installation. Once you supply the information required by the wizard, Rapid Install uses it to install the required Oracle technology stack, create the Oracle Applications file system, configure the services on the application tier, and install and configure the database. In a basic installation, all servers and services (database, Concurrent Processing, Forms, and Web) are installed on a single node (machine). This type of installation is generally used for smaller installations or for demonstration purposes. A more typical installation sets up any combination of servers you specify, on any number of nodes.
Using the Rapid Install Wizard The Rapid Install wizard consists of a series of screens where you enter the information Rapid Install needs to create your system. This slide outlines the type of information collected by the Rapid Install wizard.
Choosing an Installation Environment When you set up the instance, you can install a fresh database or a Vision Demonstration database.
Choosing an Installation Environment Rapid Install provides default names that suggest possible uses for the environment: they are production (PROD) and Vision Demonstration (VIS).
Registering Products and Country-Specific Functionalities You use the relevant Rapid Install wizard screens to register licensed products, character sets, and country-specific functionalities. During installation, Rapid Install installs all products and country-specific functionalities in the database and in the file system. Language installations require additional language DVDs.
Selecting NLS Settings A new Oracle Applications database installation uses American English (AMERICAN) as the base language with US7ASCII as the default character set and a default territory setting of AMERICA. You can select additional languages and modify the other settings on the Rapid Install wizard screens. Choosing additional languages may require choosing an alternative character set for the database and the APPL_TOP. Release 12 provides multilingual support for text parts of Oracle Applications, and for product data. Because it offers support for the Unicode (UTF8) character set, you can, if required, run a number of languages in a single instance. You choose the character set for both the database and the Applications products when you run Rapid Install. The Vision Demo database is set up for multiple-organization use, and installed with the UTF8 character set. The default character set for a production database is US7ASCII, The choice of character sets should be made carefully. It is possible to convert from some character sets to others at a later stage, but there are restrictions. For example, you can convert from US7ASCII to UTF8, but not from UTF8 to US7ASCII. The profile options for language and territory are configured at the site level when you run Rapid Install. The language you choose as the base language is used for the language profile. The default settings for date and number formats are derived from the territory profile setting.
Validating Configuration Parameters Once you have indicated the parameters for your installation, Rapid Install performs a series of system validation checks and notifies you of the results.
Running Rapid Install When you are sure the configuration parameters are correct, let Rapid Install complete the installation. When the process completes, you may need to perform additional finishing or implementation steps.
Restarting the Installation The configuration file, conf_<SID>.txt, plays an important role in restarts. It is stored in the operating system's temporary directory, and utilized if the user wishes to restart an install in which Rapid Install did not get as far as creating the database.
Configuration File The configuration file, conf_<SID>.txt, plays an important role in restarts. It is stored in the operating system's temporary directory, and utilized if the user wishes to restart an install in which Rapid Install did not get as far as creating the database. If you are installing in an environment where different machines are used to support the database and application tiers (as is typically the case), you run Rapid Install on each machine in turn, starting with the database machine. For example, if you have a machine for the database tier and two more for the application tier, you would run Rapid Install once on each machine, i.e. a total of three times. Instructor Note: The order in which Rapid Install is run on the application tier machines does not matter, but it cannot be run on more than one machine in an Applications system at once.
Rapid Install Log Files The default value for context_name is <SID>_<host_name> Instructor note: File names and locations are covered in the Architecture section of the course.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - Refer to Practice - Performing Preliminary Installation Tasks [LAB41EDY]