(Clearly, if the endpoints were non-abstract but had a fixed 1:1 relationship with a physical server, they could not be used on multiple environments.) These abstract endpoints have the same name for all clones, but are defined individually, each pointing to its own environment.ĭuring the clone phase (see Section 2.7), the clone tool also validates that the internal endpoints exist in /etc/hosts only. To keep this wiring intact on a new and different environment, the cloning tools rely on internal endpoint abstraction (abstract endpoints). This collection of configurations equals the "internal wiring." These details, along with system path information, metadata file names, and more, are used by the Provisioning Framework, and the Fusion Applications components themselves, to establish intercommunication.
When Fusion Applications is installed, the Provisioning Wizard collects information, such as: host names for Fusion Applications, Identity Management, and databases, port numbers, load balancer information, internal virtual hosts and ports, etc.
What exactly is meant by "internal wiring"? External endpoints for the destination (the user-accessed URLs) can be defined by the user and will be modified during the cloning process.ġ.1.1.1 Understanding Internal Wiring and Abstract Endpoints This keeps the internal wiring intact on the destination. Technically, this feat is accomplished using virtualized or abstract internal endpoints. Simultaneously, the destination environment must keep all the internal wiring intact, allowing the various Fusion Applications components communicate just as they did on the source. In more detail, cloning is the process of duplicating the Fusion Applications file system structure (comprised of servers, storage, and optional load balancer/reverse proxy) onto a fresh destination environment, while making the changes necessary to the software and server configurations to accommodate a new set of URLs for access by end users. Rewiring for new Fusion Applications external URLs The cloning tools also make the following necessary changes in the destination environment: In the simplest terms, the cloning solution involves creating master image copies of the Oracle Fusion Applications components, mounting them to a matching array of destination hardware, and running the cloning tools ( faclone.sh) to "rewire" the destination environment. # Enter all FA domains URL except CommonDomain seperated by comma - no comma in the end - no blank space anywhere Specify 'NONE' if this domain is not in use. # Enter the URL of all the domains of Oracle WebLogic Server domain in the form of t3://hostname:port. Specify 'NONE' if this domain is not in use.ĬOMMON_DOMAIN_DIR=/u01/oracle/fa/config/domains//CommonDomain # Enter Fusion Applications new jpsroot name # Enter the absolute path of the APPLTOP directory.
0 kommentar(er)
