Oracle E-Business Suite migration might be homogeneous or heterogeneous, depending on the source operating system (OS) that you are migrating from. The heterogeneous migrations of Oracle E-Business Suite are those in which the Endian formats for the source and target OS differ.

Migration Approaches

Customers’ migration paths are depicted in the diagram below, based on the existing platform, tooling, and experiences offered to them.

Migrating Oracle E-Business Suite to the same OS

Oracle E-Business Suite migration using Rapid Clone and Smart Clone (homogeneous – same OS). Here is how to migrate using either scenario.

1. Migration using Rapid Clone:

If the source and target OS for Oracle E-Business Suite migration are the same, you can make use of the Oracle Rapid Clone tool to migrate their database to AWS.

2. Migration using Smart Clone:

The Oracle Application Management Pack for Oracle E-Business Suite also allows you to use the Oracle Smart Clone technique to automatically clone an Oracle E-Business Suite system. Smart Clone requires that the target Oracle E-Business Suite database be cloned and detected in Enterprise Manager as a requirement. Smart Clone uses the found target database as an input to configure a database target before cloning the source instance’s apps tier. It then applies it to the Oracle E-Business Suite system in question.

Migrating for Oracle E-Business Suite across OS (using the same Endian format)

For some clients, the source and target platforms may be little endian, but the operating systems may be different. Cloning programs like Rapid Clone and Smart Clone can’t be used in these situations. This would be referred to as a “platform” migration. You can still use Oracle database technologies like Oracle RMAN, Oracle Data Guard, and Oracle Transportable under these situations. Tablespaces are great for storage, but you’ll need to use the Rapid Install software to create a new application tier and configure it as a target.

Because the process is essentially one of copying database files and then utilizing Recovery Manager (RMAN) to convert data files, Transportable Database is the fastest approach to migrate data between two systems (using the RMAN convert database command). The source and target databases must, however, be of the same release and patch set version for the E-Business Suite Transportable Databases migration process to work.

Migrating Oracle E-Business Suite across platforms (different Endian formats)

Cross platform migration of Oracle E-Business Suite involves a two-step approach to migrate the database tier and the application tier. To migrate the application tier, you would have to use rapidwiz to create the techstack and copy certain APPL_TOP & COMMON_TOP directories. And also to generate and upload customer specific manifest files to My Oracle Support and apply the supplied patches.
For database migration, Transportable Tablespaces is an Oracle database feature that allows you to move large amounts of data from one database to another more quickly, regardless of the source or target OS. The Cross-Platform Transportable Tablespaces (XTTS) feature allows you to distribute data and migrate databases across platforms with different endian (byte-ordering) formats. This migration approach is best suited for very big databases when metadata is relatively modest in comparison to the data.

Benefits of hosting Oracle E-Business Suite on AWS?

Customers can gain all of the benefits of a mature cloud platform (such as cost savings, performance improvements, and higher availability) without making large upfront investments by migrating Oracle E-Business Suite to AWS. Oracle customers enjoy choice, flexibility, and cost management with over 200 AWS Cloud services.

Migration Considerations

1. Edge applications – AWS Application Discovery Service or TSO Logic, for example, can provide relevant information on applications and systems that interact with Oracle E-Business Suite. Examine the edge applications to see if they should be moved to the cloud initially or later. This will also assist you in calculating the impact of moving to Oracle E-Business Suite.

2. Current System Utilization – Check the current utilization of Oracle E-Business Suite application servers, database servers, and concurrent processing servers. Over the course of a few weeks, utilization must be monitored, noting peak periods for input/output (I/O) and database throughput capacity. This information can be obtained utilizing various monitoring systems currently in place inside your firm. Discovery tools like AWS Application Discovery Service or Migration Evaluator can provide data on current system use and suitable instance sizing on AWS as part of a migration effort.

3. Target instance types – To support the real-time and batch workloads, create a database instance for the I/O and throughput that you saw on-premises.

4. Downtime – After the migration and setup are complete, you must arrange for a downtime to cutover to the new production instance. You can utilize a variety of methods to reduce downtime, which are covered in the following sections.

5. Recovery Point Objective (RPO) /Recovery Time Objective (RTO) – As you shift to the cloud, you can strengthen your current service level agreements (SLAs). For high availability, AWS recommends running the Oracle E-Business Suite production system across multiple Availability Zones (AZs) inside the AWS Region (HA). Each Amazon Elastic Compute Cloud (Amazon EC2) instance in an Availability Zone provides 99.99 percent infrastructure availability. You can also have a multi-Regional disaster recovery setup based on your needs (DR).

6. RAC vs. non-RAC – You might be using Oracle Real Application Clusters to run your current production databases for Oracle E-Business Suite (Oracle RAC). While RAC improves availability and throughput, you can achieve a similar degree of performance and availability without RAC on AWS by leveraging appropriate AWS services and additional Oracle HA solutions like Oracle Data Guard. Consider the total CPU, memory, and throughput values from all RAC instances when sizing database nodes on AWS.

7. Homogeneous vs. heterogeneous migration – Oracle E-Business Suite migration can be homogeneous or heterogeneous, depending on the source operating system (OS) you’re migrating from. To determine your migration type, look at the table below. The heterogeneous migrations of Oracle E-Business Suite are those in which the Endian formats for the source and target OS differ. Heterogeneous migrations are more difficult since only a limited number of tools are available for migration, and comprehensive testing is required.

To learn more about these methods and to take your first step towards moving your E-Business Suite to AWS Cloud, reach out to us at sales@ibizsoftinc.com

Having your Oracle E-Business Suite on Oracle Cloud Infrastructure has a lot of advantages. To learn more about these visit our blog https://www.ibizsoftinc.com/blog/advantages-ebs-oci where we enlist all the different deployment options and their advantages of having your E-Business suite applications on OCI.

In this blog, we will discuss the methods used to move your existing on-premise Oracle E-Business Suite applications to OCI. We will be using what is called the “Lift and Shift” method to migrate from existing on-premise applications to OCI.

There are two ways of performing a lift and shift from on-premises:

• Traditional Lift and Shift
• Reduced Downtime Lift and Shift

Traditional Lift and Shift

You can back up your on-premises Oracle E-Business Suite installation to Oracle Cloud Infrastructure Object Storage and provision it to Oracle Cloud Infrastructure. Traditional lift and shift automations support an Oracle E-Business Suite Release 12.2.3 or later, or Release 12.1.3 installation (with Oracle Database 19c, 12.1.0.2, or 11.2.0.4) to Oracle Cloud Infrastructure and certified Oracle Database cloud services.

Now lets understand all the different activities involved in the traditional lift and shift method.

Verify Prerequisites for Traditional Lift and Shift

You must have all the prerequisites to create a backup with the Oracle E-Business Suite Cloud Backup Module as part of a traditional lift and shift procedure. These would include all the necessary patches, cloud membership details, connection details, etc.

Prepare the Source Oracle E-Business Suite Environment

In this step we would create the staging area where the on-premise backup of your existing database and application would be kept. We also need to ensure that the Oracle E-Business Suite Cloud Backup Module can connect to all the on-premises nodes.

Deploy Oracle E-Business Suite Cloud Manager

Here we would be deploying the Oracle E-Business Suite Cloud Manager Compute instance using an Oracle Cloud Infrastructure Marketplace image and configure Oracle E-Business Suite Cloud Manager.

Install the Oracle E-Business Suite Cloud Backup Module

After deploying Oracle E-Business Suite Cloud Manager, we will then install the Oracle E-Business Suite Cloud Backup Module on the Linux server that we have chosen to use as the backup module server, which can be located either on-premises or in OCI Compute. It can be one of the Oracle E-Business Suite nodes or another server that resides in your intranet.

Create an Advanced Configuration Parameters File (Optional)

Before running the Oracle E-Business Suite Cloud Backup Module, you can optionally create a file to specify advanced configuration parameters to address special situations. If you do not need to specify these parameters, you can skip this section.

Create a Backup with the E-Business Suite Cloud Backup Module

In this section, we will run the Oracle E-Business Suite Cloud Backup Module, EBSCloudBackup.pl, to create a backup of your source Oracle E-Business Suite environment on Oracle Cloud Infrastructure Backup Service. This module will backup our existing environment and transfer it to the Oracle Cloud Object Storage as desired. We can then use the Oracle E-Business Suite Cloud Manager to provision an environment on Oracle Cloud Infrastructure based on the backup we created.

Reduced Downtime Lift and Shift

In this method we will be making sure that our on-premise Oracle E-Business Suite environment is migrated to Oracle Cloud Infrastructure with minimum downtime for mission critical systems.

To learn more about these methods and to take your first step towards moving to Oracle Cloud Infrastructure, reach out to us at sales@ibizsoftinc.com.

With the advent of cloud technologies, all businesses have already started increasing their cloud footprint. Some workloads migrated swiftly and readily as businesses adopted cloud solutions, exhibiting the cloud’s flexibility and agility. However, this wasn’t the case for all workloads. Many businesses found it difficult to migrate essential business applications, which posed additional problems as well as stringent performance, security, and control requirements.

Your company is presumably already utilizing Oracle E-Business Suite for order management, procurement, manufacturing, logistics, and/or financials if you’re reading this. Your solution may have been tailored to your specific requirements and tightly connected with other apps to assist with day-to-day operations. As a result, a new software-as-a-service (SaaS) solution may not make sense to start from scratch, re-architect, and retrain workers. The strength of adopting an infrastructure as a service (IaaS) solution on OCI is the flexibility to accept everything you already do with your on-premise E-Business Suite. You have control over the performance, security, and business continuity plans with IaaS in OCI.

What is OCI?

OCI is a virtual data center that is hosted remotely and can supply virtual hardware in seconds. This implies that if you require a server, you can get one with a few clicks. If you need a storage volume, it’s available in seconds and can be connected to a Windows or Linux server with a few automatically generated commands. It comes with an uncluttered, transparent, and simple-to-use site, as well as cost analysis and budget reports that are simple to understand, and appealing cost-effective economics.

KEY BENEFITS OF ORACLE EBS ON OCI

• 38% lower TCO than on-premises deployments, 44% less than AWS
• Managing and reducing CAPEX, ensuring the data centers you maintain are efficient, while eliminating server hardware and taking advantage of cloud flexibility where possible.
• 30% increased performance, 2-10x faster reporting
• High availability with RTO < 4 hours and RPO < 4 hours
• Maximize your solution availability with Oracle, with Oracle RAC or Exadata in the cloud
• Rapid in-place technology refresh and patching
• Proactive monitoring of usage and costs
• Near instant scaling up or down – e.g., to handle business growth or workload bursts at month end
• Federated identity with your existing systems
• Security and compliance overhead for IaaS is Oracle’s responsibility, helping reduce audit length and cost
• Transform large, irregular CAPEX expenditures to predictable OPEX, pay as you go based on usage, and bring your own Oracle licenses to Oracle Cloud Infrastructure to leverage your existing investments, including monitoring, operational runbooks, skills, and workflow.

TCO Analysis

Aside from the advantages of being easier to transfer, administer, and scale, hosting E-Business Suite on Oracle Cloud Infrastructure is actually less expensive than running it on premises or in another cloud. E-Business Suite on Oracle Cloud Infrastructure can save you 38% compared to on-premises and 44% compared to another cloud.

ASSUMPTIONS

• 2,500 concurrent users
• 6 environments (2 production, 1 development, 1 testing, 1 staging, and 1 QA)
• OCI: 80 vCPUs per environment, 5TB database storage, 50 GB/vCPU storage, 1 Gbps FastConnect, Backups, 4TB data egress,
• Single node database, 25% cloud discount
• On-Premises: 12 physical servers, each with 28 cores, 128 GB RAM, and 13.5 TB storage
• AWS: Same details as OCI, reserved instances for prod environments, 7% EA disco

ORACLE E-BUSINESS SUITE ON ORACLE CLOUD INFRASTRUCTURE

Oracle E-Business Suite runs on Oracle Cloud for Infrastructure in the same way it does on premises in your data center today — the same applications you may have customized, purchased, and trained your staff on, but on a combination of Oracle’s Infrastructure as a Service (IaaS) and Database as a Service (DBaaS) offerings (DBaaS).
Oracle E-Business Suite deployment on Oracle Cloud Infrastructure choices include the following:
Infrastructure-as-a-Service: Oracle Cloud Infrastructure is a comprehensive set of cloud services on which enterprise applications can run. Oracle Cloud Infrastructure provides high-performance computation and storage capabilities in a customizable overlay virtual network that can be accessed securely from your on-premises network. OCI offers highly scalable, cost-effective compute power for hosting your Oracle E-Business Suite application tier and, optionally, database tier.
Infrastructure-as-a-Service + Database-as-a-Service: Oracle Cloud Platform is a complete, standards-based, fully integrated combination of Oracle and open source technologies that you may use to design, deploy, migrate, and manage a variety of cloud-based application workloads at a substantially lower operational cost. The OCI DB System or OCI Exadata DB System can be used to run your database tier, allowing you to rapidly and easily provide your desired database configuration.

THE NEXT STEP

Ibizsoft can assist you in developing a roadmap to modernize your ERP. Be it upgrading your E-Business suite environment to Release 12.2 or migrating your E-Business to the Cloud, with a proven track record Ibizsoft can help you to successfully deliver your business transformation. For more information reach out to us at sales@ibizsoftinc.com.

Create a new “CloverETL Project”

Double click on the “workspace.prm” file to add new parameters to the project

Add the following parameters  change the values as per the environment

#Additional Parameters

DEFAULT_LANGUAGE=en

ENDECA_SERVER_CONTEXT=endeca-server

ENDECA_SERVER_HOST=localhost

ENDECA_SERVER_PORT=7001

DATA_DOMAIN_NAME=FulfillDelay

MULTIASSIGN_DELIMITER=\u007F

Create a new graph, name it as “CreateDomain”

This will create the required data domain on the Weblogic server for the application, domain name will be read from the parameters file

Add two web service client components to the graph and name then as Delete Domain and Create Data Domain

Set the phase = 1 for the create data domain (right click -> set phase)

Double click on the Delete Domain component

In the WSDL URL enter: http://localhost:7001/endeca-server/ws/manage?wsdl

Click on the text box for Operation name and select “delete DataDomain”

In the Request Body Structure enter the following

<ns:deleteDataDomain xmlns:ns=”http://www.endeca.com/endeca-server/manage/1/0″>

<ns:name>${DATA_DOMAIN_NAME}</ns:name>

</ns:deleteDataDomain>

Similarly for create data domain, enter the same WSDL URL

Select Operation name as createData Domain

And in the request body paste the following

<ns:createDataDomain xmlns:ns=”http://www.endeca.com/endeca-server/manage/1/0″>

<ns:name>${DATA_DOMAIN_NAME}</ns:name>

<!–Optional:–>

<ns:ddProfileName>default</ns:ddProfileName>

<!–Optional:–>

<ns:enabled>true</ns:enabled>

</ns:createDataDomain>

Note: Please make sure the “<ns:enabled>true</ns:enabled>” has “true” value, by default this could be false.

Run the graph to create the data domain

Create a new graph for Load Data domain

Add two components

DB input table

And Bulk Add/Replace Records

Create a DB connection

In the “Outline” window under connections, add a new connection

Enter the appropriate  connection details and save

Double click on the DB Input table component

Select the DB connection

In the SQL Query enter the following

SELECT OOL.HEADER_ID,

OOL.LINE_ID,

TRUNC(OOL.FULFILLMENT_DATE)-TRUNC(PROMISE_DATE)  FUL_DELAY,

OOL.UNIT_SELLING_PRICE,

OOL.CREATION_DATE ORDERED_DATE,

OOL.REQUEST_DATE,

OOL.SCHEDULE_SHIP_DATE,

OOL.ACTUAL_SHIPMENT_DATE,

OOL.FULFILLMENT_DATE,

(select segment1

FROM MTL_SYSTEM_ITEMS_B MTL

WHERE MTL.INVENTORY_ITEM_ID = OOL.INVENTORY_ITEM_ID

AND MTL.ORGANIZATION_ID =204) PRODUCT,

(SELECT DESCRIPTION

FROM MTL_SYSTEM_ITEMS_B MTL

WHERE MTL.INVENTORY_ITEM_ID = OOL.INVENTORY_ITEM_ID

AND MTL.ORGANIZATION_ID =204) PRODUCT_DESCRIPTION,

(select party_name

FROM HZ_PARTIES HP

WHERE HP.PARTY_ID = (SELECT HC.PARTY_ID

FROM HZ_CUST_ACCOUNTS HC

WHERE HC.CUSt_ACCOUNT_ID = OOL.SOLD_to_ORG_ID)

) CUSTOMER,

(SELECT ood.ORGANIZATION_NAME

FROM ORG_ORGANIZATION_DEFINITIONS OOD

WHERE OOD.ORGANIZATION_ID = ool.sold_from_org_id) warehouse

FROM oe_order_lines_all ool

, wsh_delivery_Details wdd

, wsh_new_deliveries wnd

, wsh_delivery_assignments wda

WHERE 1=1

AND wdd.source_header_id = ool.header_id

AND wdd.source_line_id = ool.line_id

AND WDA.DELIVERY_DETAIL_ID = WDD.DELIVERY_DETAIL_ID

AND WDA.DELIVERY_ID = WND.DELIVERY_ID

AND TRUNC(PROMISE_DATE) != TRUNC(OOL.FULFILLMENT_DATE)

AND TO_CHAR(OOL.CREATION_DATE,’YYYY’) BETWEEN ’2003′ AND ’2013′

AND WDD.CURRENCY_CODE = ‘USD’

order by ool.line_id desc

Create an edge from DB Input table to the Bulk Add/Replace Records

Right click on the edge and select the existing meta data created (if not present, create a new metadata using the above query)

Double click on the Bulk Add/Replace Records component

In the Data Domain name enter “${DATA_DOMAIN_NAME}”

In Spec Attribute enter “HEADER_ID”

Save and run the graph to load the data into the application

In case you want to reset the data in the data domain to load new data, create a new graph to reset the data as shown below

Please note that this step is optional

Create a new graph and add the reset data domain component

Double click on the component

Enter the values for the host and domain name as appropriate

Save and run the graph for clearing the data in the data domain

Creating the Studio Application

Login as admin in the studio application

After login Navigate to control panel->Data sources

Create a new data source with the following connection string

{

“dataDomainName”: “FulfillDelay”,

“name”: “FulfillDelay”,

“port”: “7001″,

“server”: “localhost”

}

Create a new application and add the display components as shown below

Components for the left panel

1. Search box
2. BreadCrums
3. Guide Navigation (Rename it as Range filters)
4. Guide Navigation

Right Panel

1. Tabbed component container
2. Add three charts in the container panels
3. Results table

Configure the column names as below

Navigate to Application Settings->View Manager

In the base view, rename the columns as per requirment

Configure the Range filer Guide navigation

Choose which attributes to display and change the type of values to “Range Filters” for the attributes to display

In a similar manner modify the other components to arrive at the UI design as shown below

Create a PTO model as shown below and assign it to the appropriate sub inventory

This item will serve as Top level PTO model under which we will add the option classes and the components

Navigate to Inventory responsibility and open the Master item form

Enter the Item name and Description and save

To apply the template navigate to Tools->Copy from

Click apply and done

Save

Create an option class items for the various components as show below

Apply the PTO Option Class template

Similarly create the components for each of the Option classes

Create Items using the Finished Goods Template

Please make sure the all the PTO models, Option classes and finished goods are assigned to the appropriate inventory org do that they can be transacted

Also make sure the all the items are web published

Create Bill of materials

Navigate to the “Bill of Material” responsibility

Navigate to Bills->Bills to create the BOM structure

First Create the BOM structure for the Options classes

In the Order Management tab, make sure that the “Optional” flag has been checked so that these components appear as options in the Configurator model UI

Similarity create BOM Structure for the rest of the Option classes

Create the BOM structure for the main PTO model; add all the Options classes under the components section of the PTO model

Please note that you can add any other individual items which are bundled with the PTO model along with the Options classes, for e.g. the Software installation CD can be added along with the various option classes for component selection as shown below

Import the BOM model to the Configurator module

Navigate to “Oracle Configurator Administrator” responsibility

Run the “Populate Configuration Models” concurrent program

Enter the Organization and PTO top level BOM item name in the form and to fields

Run the program

Once the program completes, the BOM model will be accessible via the Configurator Developer UI

Click on structure to view the BOM Structure

Click on Edit to create non bom option nodes

Click on create on the top level PTO item to create nodes under it

Create an Option feature

Option feature node will be added to the structure, click on create to create values for option feature

Similarly create various Options and Option features as necessary

Create rules for BOM model component selection based on option features

Click on Rules tab and click on create as shown in the below screenshot

Create a Logic rule as shown below

Left operand is the option features and right operand is the bom components to be selected

Create rules for all option features as necessary

Create the UI

Click on the User Interface tab

Provide a name for the UI and Select a template

Model UI will be created, modify the page components as necessary

Click on Generate Logic and Test the model

Publishing the model to iStore

In the “Repository” tab click on Publications

Click on Create model publication

Select the model to publish

Select the UI name

Select the applications

Click on apply to create a publication

Navigate the Oracle Configurator Administrator

And run “Process a Single Publication”

Enter the appropriate publication id

Submit the concurrent program

Add the PTO model to iStore catalog

The configurable items should be available on iStore catalog page

Click configure to open the Configurator UI

Users can now configure the product and add the custom configuration to iStore shopping cart.

When a Business user registers we need to validate the serial number for the party and store the serial number in the customer account DFF segment

Steps:

1. Create DFF segment on customer account

Navigate to System Administrator->Application->Flexfield->Descriptive->Segments

Unfreeze the flex field definition and create a new segment for storing serial number

Save Freeze and compile flex field definition

Sample DFF on the customer account screen:

2. Query to validate serial number

Copy “ibeCRgpBusinessCreate.jsp” to “xx_ibeCRgpBusinessCreate.jsp” and customize “xx_ibeCRgpBusinessCreate.jsp” (Template STORE_REG_BUSINESS_CREATE_P) to add a validation using the following query

Also add a field to enter the Serial number on the Business user registration page

Query to be used:
SELECT DISTINCT HP.PARTY_NAME

,HP.PARTY_number

,CII.INSTANCE_ID

, CII.SERIAL_NUMBER

,msi.segment1

FROM APPS.CSI_ITEM_INSTANCES CII

,APPS.MTL_SYSTEM_ITEMS_B MSI

,APPS.HZ_PARTY_SITES PS

,apps.hz_parties hp

,apps.mtl_system_items_b bmsi

WHERE CII.INSTALL_LOCATION_ID IS NOT NULL

AND CII.INSTALL_LOCATION_ID = PS.PARTY_SITE_ID

and ps.party_id = hp.party_id

AND CII.INVENTORY_ITEM_ID   = MSI.INVENTORY_ITEM_ID

AND BMSI.INVENTORY_ITEM_ID                        = NVL (MSI.BASE_ITEM_ID, MSI.INVENTORY_ITEM_ID)

AND BMSI.ORGANIZATION_ID                          = MSI.ORGANIZATION_ID

AND CII.INSTANCE_STATUS_ID                       != 1

AND CII.SERIAL_NUMBER = ‘EM500007′ –Input Parameter

and hp.party_number = 1932 –Input Parameter;

Step 3: customize UI

In a similar manner customize the following pages as per the desired UI

ibeCRgdUserPasswd.jsp  — STORE_REG_USER_PASSWD_D

ibeCRgdRegContainer.jsp — STORE_REG_CONTAINER_D

ibeCRgdPersonInfoIncl.jsp — STORE_REG_PERSON_INCL_D

ibeCRgdBusinessCreate.jsp  — STORE_REG_BUSINESS_CREATE_D

ibeCCtdMenu.jsp

ibeCCtdCmnSctLayout.jsp

Sample UI

• Sun Java 6
• WebLogic Server
• ADF Runtime
• Oracle Endeca Information Discovery installation packages
  • Oracle Endeca Information Discovery Studio (3.0) for Microsoft Windows x64 (64-bit) and Tomcat
  • Oracle Endeca Information Discovery Provisioning Service (3.0) for Microsoft Windows x64 (64-bit)
  • Oracle Endeca Server (7.5.1.1) for Microsoft Windows x64 (64-bit)
  • Oracle Endeca Information Discovery Integrator (3.0.0.2) for Microsoft Windows x64 (64-bit)
  • Oracle Endeca Information Discovery Sample Application (3.0) for Microsoft Windows x64 (64-bit)

Installing the Sun Java JDK

When you install the Sun Java SDK, you must install it to a path that does not have any spaces.

To install the Sun Java SDK:

1. Double-click the JDK installer file that you downloaded (jdk-6u43-windows-x64.exe).

The welcome page of the JDK installation wizard is displayed.

2. On the welcome page, click Next.

3. On the Custom Setup page, because the default installation location (under Program Files) has a space, you must change it here. To change the JDK installation location:

(a) Click the Change button.

(b) In the Folder name field, remove the Program Files directory. This changes the location to:

C:\Java\jdk1.6.0_43\

(c) Click OK.

(d) On the Custom Setup page, verify that the installation location has been updated, then click

Next.

4. The Destination Folder page sets the location of the public JRE. Because this JRE is not used by Endeca Information Discovery, you can leave the default directory. Click Next.

The installation process begins.

5. When the installation is completed, click Finish.

Installing WebLogic Server and ADF Runtime

Once you have the JDK installed, you can install WebLogic Server and ADF Runtime.

Installing WebLogic Server

After downloading the installation packages and installing the JDK, you next install WebLogic Server. Note

that this procedure only installs the minimum WebLogic Server configuration needed for Oracle Endeca

Information Discovery.

To install WebLogic Server:

1. From a command prompt, navigate to the directory where you placed wls1036_generic.jar.

2. To launch the installer, issue the following command:

java -jar wls1036_generic.jar

The Welcome page of the installation wizard is displayed.

3. On the Welcome page, click Next.

4. On the Choose Middleware Home Directory page:

(a) Click the Create a new Middleware Home radio button.

(b) Accept the default location for the Middleware Home Directory.

(c) Click Next.

5. To bypass the Register for Security Updates page:

(a) Click Next without entering an email address.

(b) On the Email Address Not Specified dialog, click Yes.

(c) On the Are You Sure? dialog, click Yes.

(d) If the Connection failed dialog is displayed, check the I wish to remain uninformed of security

issues in my configuration or the machine has no Internet access checkbox, then click

Continue.

6. On the Choose Install Type page, click the Custom radio button, then click Next.

7. On the Choose Products and Components page, check the following products, then click Next:

• Core Application Server

• Administration Console

• Configuration Wizard and Upgrade Framework

• Evaluation Database

8. On the JDK Selection page, verify that the JDK you installed is selected. If it is, click Next.

If that version of the JDK is not selected:

(a) Under Local JDK, click the Browse button.

(b) Browse to and select the directory that contains the JDK (C:\Java\jdk1.6.0_43\).

The Local JDK section is updated to display the selected JDK with a checked box next to it.

(c) Click Next.

9. On the Choose Product Installation Directories page, accept the default installation directory, then

click Next.

10. If the Install Windows Service page is displayed, click the No radio button, then click Next.

11. If the Choose Shortcut Location page is displayed, click a radio button to select the location of the

Windows shortcut, then click Next.

12. On the Installation Summary page, verify that you are installing the correct products, then click Next.

13. On the Installation Complete page, uncheck the Run Quickstart checkbox, then click Done.

An Oracle WebLogic shortcut is created in the Start Menu.

Installing Oracle ADF Runtime

After you install WebLogic Server, you next install ADF Runtime 11.1.1.6, which contains the JRF needed by Oracle Endeca Server.

To install Oracle ADF Runtime:

1. Unpack the ADF zip package (m_appdev_generic_11.1.1.6.0_disk1_of1.zip).

The package contains:

• readme.htm file

• Disk1 directory

• Disk2 directory

2. From a command prompt, change to the Disk1 directory.

3. Run the installer:

setup.exe -jreLoc <jre_location>

<jre_location> is the full path to the location of the Sun Java 6 JRE (Java Runtime Environment) that you installed. The JRE is located in the JDK installation directory.

For example:

setup.exe -jreLoc c:\Java\jdk1.6.0_43\jre

The Welcome page of the ADF installation wizard is displayed.

4. On the Welcome page, read the information, then click Next.

5. On the Install Software Updates page, click the Skip Software Updates radio button, then click Next.

6. On the Prerequisite Checks page, wait until the installation process passes all the necessary checks.

If everything passes the checks, click Next.

7. On the Specify Installation Location page, verify that the Oracle Middleware Home directory is the

location where you installed WebLogic, then click Next.

8. On the Application Server page, click the WebLogic Server radio button, then click Next.

9. On the Installation Summary page, verify the installation details, then click Install.

10. On the Installation Progress page, when the installation process has completed, click Next.

11. On the Installation Complete page, to exit the installer, click Finish.

Two shortcuts are created in the Start Menu:

• Oracle Application Developer 11g

• Oracle Common Home 11g

Installing Oracle Endeca Server

For Endeca Server, you first install the application, then create a WebLogic domain for it.

Running the Oracle Endeca Server installer

Next, you install the Oracle Endeca Server package.

To install Oracle Endeca Server:

1. Unpack the Endeca Server zip file to a temporary directory.

The resulting endecaserver directory contains a Disk1 subdirectory.

2. From a command prompt, change to the Disk1 directory, then run the installer:

setup.exe -jreLoc <jre_location>

<jre_location> is the full path to the location of the Sun Java 6 JRE (Java Runtime Environment) that

you installed earlier.

For example:

setup.exe -jreLoc C:\Java\jdk1.6.0_43\jre

The installation wizard Welcome page is displayed.

3. On the Welcome page, read the information, then click Next.

4. On the Prerequisite Checks page, if everything passes the checks, click Next.

5. On the Specify Installation Location page:

(a) For the Oracle Middleware Home field, verify the name of the Oracle Middleware home directory.

(b) For the Oracle Home Directory field, accept the default Endeca Server home directory.

This is the root directory of the Endeca Server installation

(c) Click Next.

6. On the Select Deploy Mode page, uncheck the YES checkbox, then click Next.

7. On the Installation Summary page, verify the installation details, then click Install.

8. On the Installation Progress page, when the installation progress has completed, click Next.

9. On the Installation Complete page, to exit the installation wizard, click Finish.

When the installation finishes, the Endeca Server files and directories are written to the Oracle Home

Location.

Creating the WebLogic domain for Endeca Server

The Endeca Server installation includes a WebLogic domain template that you use to create the Endeca

Server WebLogic domain.

To create the WebLogic domain for Endeca Server:

1. From a command prompt, change to the directory that contains the Configuration Wizard start-up program:

C:\Oracle\Middleware\wlserver_10.3\common\bin

2. To start the Configuration Wizard, run the following command:

config.cmd

The Configuration Wizard Welcome page is displayed.

3. On the Welcome page, click the Create a new WebLogic domain radio button, then click Next.

4. On the Select Domain Source page, check the Oracle Endeca Server checkbox.

The Oracle JRF checkbox is then checked automatically. Click Next.

5. On the Specify Domain Name and Location page:

(a) Set the domain name to endeca_server_domain.

(b) Keep the default domain location.

(c) Click Next.

6. On the Configure Administrator User Name and Password page, to create the administrator

credentials for starting WebLogic Server:

(a) In the Name field, type the name for the new administrator user.

(b) In the User password field, type the user password.

The password must be at least eight alphanumeric characters long, and contain at least one

number or special character.

(c) In the Confirm user password field, retype the password.

(d) Optionally, in the Description field, type a description for the user account.

(e) Click Next.

7. On the Configure Server Start Mode and JDK page:

(a) Under WebLogic Domain Startup Mode, click the Production Mode radio button.

(b) Under JDK Selection, click the Available JDKs radio button.

(c) In the JDK list, click the Sun Java SDK that you installed. If the Sun Java JDK is not displayed,

click the Other JDK button, and then browse for the Sun Java JDK home:

C:\Java\jdk1.6.0_43\

(d) Click Next.

8. On the Select Optional Configuration page, do not select any optional configurations. Click Next.

9. On the Configuration Summary page, to create the domain, click Create.

On the Creating Domain page, the message “Domain Created Successfully!” signifies the end of the domain creation process.

10. To exit the Configuration Wizard, click Done.

Verifying the Endeca Server deployment

After installing the Endeca Server, you should verify that the Endeca Server application was correctly

deployed.

To verify the Endeca Server application deployment:

1. To start the Admin Server for the Endeca Server domain, run

C:\Oracle\Middleware\user_projects\domains\endeca_server_domain\startWebLogi

c.cmd.

Alternatively, from the Windows Start menu, select Oracle WebLogic>User

Projects>endeca_server_domain>Start Admin Server for Weblogic Server Domain.

2. When prompted, enter the administrator user name and password for the Endeca Server domain.

3. From a Web browser, go to the Administration Server console at

http://localhost:7001/console.

4. On the Administration Console login page, log in using the domain administrator user name and

password.

5. Under Domain Structure, in the endeca_server_domain tree, click Deployments.

6. In the Deployments table, check the oracle.endecaserver Web application (on the second page of

the list).

Its State should be “Active” and its Health should be “OK”.

Installing Integrator

Integrator is installed as a machine-wide installation on Windows.

This type of installation requires administrator permissions and is used because it is intended for a production

environment. To complete this installation, you need the Integrator package you downloaded from the Oracle

Software Delivery Cloud.

To install Integrator on a Windows client:

1. From the Integrator package, extract EID_3.0_Integrator_designer.exe.

This is the Integrator installer file.

2. To start the wizard, double-click the installer file.

The wizard verifies the contents of the installation package.

3. To begin the installation process, click Next.

4. On the Copyright and Legal page, click Next.

5. On the Destination Folder page, accept the default installation directory, then click Next.

You must install Integrator into an empty directory.

6. On the Completing the Setup Wizard page, click Next.

The wizard begins to install the Integrator files.

7. When the wizard confirms that you have successfully completed the installation, click Finish.

8. After installation, to start the program, double-click the Integrator shortcut icon.

Installing Studio

Download the Oracle Endeca Information Discovery Studio (3.0) for Microsoft Windows x64 (64-bit) and Tomcat and unzip it in a folder

Starting Studio

Before you can explore the sample application, you must start the Studio server and log in to Studio.

Important: The Studio Chart component requires Adobe Flash Player 10.x. If you do not already

have Flash Player installed on your machine, you will need to download it from

http://get.adobe.com/flashplayer and install it before using Studio.

Note: This procedure assumes you installed the Studio Tomcat bundle.

To start Studio:

1. To start the portal’s Tomcat instance, run endeca-portal\tomcat-6.0.36\bin\startup.bat.

A command window opens, displaying log messages for the server start-up process. This process

takes several minutes to complete. When the server is started, you will see a message similar to this:

org.apache.catalina.startup.Catalina start

INFO: Server startup in xxxxx ms

Version 3.0.0 • March 2013

Important: Do not close the Tomcat command window at any point while you are using

Studio.

2. Once the server is started, open a browser and go to http://localhost:8080.

The Studio login page opens in the browser window.

3. Log in to Studio using the default login and password:

Email Address: admin@oracle.com

Password: Welcome123

You are immediately prompted to change the password upon first use. The new password must

contain:

• At least 6 characters

Oracle® Endeca Information Discovery : Getting Started Guide

Provisioning the Getting Started Application 13

• At least one non-alphabetic character

Studio opens the Discovery Applications page: