Oracle Audio Technologies 12.2 manual Upgrading a Co-deployed Environment

Page 60

Upgrading a Co-deployed Environment

Upgrading a Co-deployed Environment

When upgrading to the Plan Release 12.2 and Place Release 12.2 on an existing co-deployed environment, the installation may abort because of the incompatible components.

The following example (Example 6–1) displays an error message that lists the incompatible components (Alert 1.3.1 and Suite 1.5.0).

Example 6–1 Incompatible Components Error

ERROR: The following components are not compatible:

ERROR: Alerts 1.3.1 and Suite 1.5.0

In case the installation aborts because of the incompatible components, use the "-P" argument in the install.sh for the first product upgrade. This ensures that the first product upgrade completes successfully (incompatible components get reported as warnings).

When you run the next product Release 12.2 upgrade, the latest compatible versions of the components are retained, and the warnings get resolved. For the second upgrade, you can run the upgrade without the "-P" argument.

For more information on the "-P" argument and the install.sh syntax, see install.sh in the chapter Installing Place.

Setting Up a Foreign JMS Server on WebLogic Server

In case you have set up a Plan-Place co-deployed environment over clusters, you must set up the Foreign JMS Server capability in WebLogic so that the stores information is synchronized and accessible through both the applications.

To set up a foreign JMS Server:

1.As an administrator, log on to the Weblogic Server console.

2.Create a JMS connection factory.

3.Once created, target, and deploy the connection factory on the Plan cluster. The JNDI name should be the same as the "connection-factory-jndi-name" value given in the "weblogic-ejb-jar" for the "StoreSetChangeHandler" MDB.

For example,

Name: CommonConnectionFactory

JNDI Name: CommonConnectionFactory

4.Configure a new Foreign JMS Server.

5.Once created, target, and deploy the Foreign JMS server on the Place cluster.

For example,

Name: NotificationJMSServer

JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory

JNDI Connection URL: provide plan app URL (eg. t3://dev-app-l07:7090).

6.Create a Foreign JMS connection factory. Mention the local and remote JNDI names as given for CommonConnectionfactory.

For example,

Name: RemoteConnectionfactory

6-6Oracle® Retail Place Installation Guide

Page 59 Page 61
Image 60
Page 59 Page 61
Contents Oracle Retail Place Page Page Page Contents Installing Place Files and Directory Structure Viii Preface Supplemental Documentation on MetaLinkConvention Meaning BoldfaceOverview Overview of PlacePlace Enterprise Components Client System Tier Database Server Tier Roadmap for Implementing Place Roadmap for Implementing PlaceTask Description Planning Your Installation Overview of the Planning ProcessPlanning Your Environment Supported Configurations Managed Server ConfigurationPlanning for Optimal Place Performance Network RequirementsDatabase Requirements Application Server RequirementsWebLogic Application Server Oracle Database RequirementsClient System Requirements Client System EnvironmentSoftware Requirements Setting Up the Database Installing the DatabaseCreating the Default Tablespaces Creating the Default Data User AccountBusiness Database Tablespaces Tablespace DescriptionCreating the Database Links 4Oracle Retail Place Installation Guide Setting Up the Application Server Installing the WebLogic ServerSetting Up a WebLogic Domain Steps to Set Up a WebLogic DomainStep Window Database Jdbc Options Window Setting Up the WebLogic Startup Script Under WebLogic Configuration Startup Mode, click ProductionSetting Up the Maximum Message Size Servername and Portnumber DescriptionWhere 6Oracle Retail Place Installation Guide Installing Place Overview of the Installation ProcessAbout Password Security Management Installing Place Accessing the Installation SoftwareSetting Up Your Installation Properties File Installing Place in the Silent ModeInstall.sh Argument DescriptionInstalling Place Using the Graphical Oracle Installer Return ValueWelcome screen appears Place Installation Destination Screen Application Server Selections Screen Java Message Server Properties Screen Database Properties Screen Installation Progress screen appears Post-Installation Tasks Setting Up ADF LibrariesSetting Up Targets for the JMS Servers Loading Business Rules Loading User RolesLoading Seed Data Installing the Sample Dataset Install.properties Parameters Reference Installation Target DirectoriesCommand Shell Settings Installation Target DirectoriesApplication Server and Database Settings Connection Pools SettingsLast Session Properties Files Calc Engine User Setting WebLogic Application Server SettingsCalc Engine User Setting WebLogic Application Server SettingsOracle Database Settings Connection and Authentication SettingsConnection and Authentication Settings Oracle DB Configuration Database Authentication CredentialsDatabase Authentication Credentials for Audit Audit Database Properties10 Audit Database Properties Audit property for Creating the DatabasePlace Schema Properties 11 Place Schema PropertiesPlan Front End Database Properties 12 Plan Front End Database PropertiesELM Schema Properties 13 ELM Schema PropertiesSAU User for CE to access ELM and CommonDB Place-specific Suite Properties Cluster Properties14 Place-specific Suite Properties 15 Cluster PropertiesMicroStrategy Properties Cluster Properties16 Last Session Properties Files Troubleshooting Installation Issues Troubleshooting Installation IssuesInstallation Aborts Because of Incompatible Components 26Oracle Retail Place Installation Guide Installing Place Over Plan Setting Up the Plan InstallationSetting Up the Place Installation Setting Up the Place InstallationConfiguring Place Loading Business RulesLoading User Roles Loading Seed Data4Oracle Retail Place Installation Guide Reference to the Data Load Scripts Data Load Scripts for Place and PlanSetting Up a Foreign JMS Server on WebLogic Server Example 6-1 Incompatible Components ErrorUpgrading a Co-deployed Environment Setting Up a Foreign JMS Server on WebLogic Server 8Oracle Retail Place Installation Guide Place Installation Base folder ConfigFiles and Directory Structure Application Directory StructureInstallScripts LogsModules Spool TempModules Deployed On WebLogic Server Table A-2 Modules Deployed on WebLogic ServerModule Name Description EAR File Name and Location Index Index-1Index-2

12.2 specifications

Oracle Audio Technologies has established itself as a prominent name in high-end audio equipment, and their latest offering, the Oracle Audio Technologies 12.2, continues this tradition of excellence. This innovative component is designed to cater to audiophiles who demand the highest fidelity in their sound reproduction.

One of the main features of the Oracle 12.2 is its cutting-edge digital-to-analog conversion technology. This state-of-the-art DAC ensures that every detail of the audio signal is captured and reproduced with stunning clarity. The unit employs advanced algorithms that minimize distortion and maximize dynamic range, providing users with a listening experience that is both immersive and engaging.

Another significant aspect of the Oracle 12.2 is its modular design. This flexibility allows users to customize their setup based on their unique audio preferences and needs. Whether integrating it into an existing system or using it as a standalone device, the modular features can accommodate a range of configurations, making it suitable for various listening environments.

The Oracle 12.2 also boasts impressive connectivity options. With support for both wired and wireless streaming, audiophiles can connect effortlessly to a wide range of devices. The inclusion of Bluetooth and Wi-Fi ensures easy access to high-definition audio, while USB ports provide for direct connections to computers or music servers.

In terms of build quality, the Oracle 12.2 exemplifies luxury and durability. Its chassis is crafted from premium materials, designed not only for aesthetic appeal but also to reduce vibration and interference. This results in enhanced sound performance, ensuring that the audio remains true to the original recording.

The user interface of the Oracle 12.2 is intuitive and user-friendly, designed to enhance the listening experience without the complexity often associated with high-end audio components. A dedicated app allows for easy navigation and control, making it simple to access a vast library of music.

With its unparalleled audio fidelity, customizable design, and robust connectivity options, the Oracle Audio Technologies 12.2 stands out as a premier choice for discerning audiophiles. It captures the essence of what high-end audio should be: a seamless blend of technology, craftsmanship, and exceptional sound quality. Users can expect nothing short of an extraordinary auditory journey that elevates their listening pleasure to new heights.
Top Page Image Contents