This section describes how to configure Oracle Warehouse Builder on Linux platforms.
This section includes the following topics:
"Configuring Oracle Warehouse Builder on Linux Installed as Part of Oracle Database 11g Release 2"
"Configuring Oracle Warehouse Builder on Linux Installed as a Standalone Instance"
|
Note: The initial installation of Oracle Warehouse Builder must be made on the computer that hosts Oracle Warehouse Builder Repository. |
Oracle Warehouse Builder is part of every database installation on hosts running Oracle Database 11g Release 2.
After Oracle Database 11g Release 2 is installed, you only have to unlock two accounts: OWBSYS and OWBSYS_AUDIT.
There are no additional installation tasks. However, you must configure Oracle Workflow to use process flows.
To unlock OWBSYS and OWBSYS_AUDIT accounts:
At the command prompt, start SQL*Plus:
C:\> sqlplus
When prompted for user name, log in as a user with administrative privileges.
Enter user-name: sys as sysdba Enter password: password Connected to: Oracle Database 11g Enterprise Edition Release 11.2 - Production With the Partitioning, OLAP and Data Mining options
Unlock the OWBSYS user account, and set its new password:
SQL> alter user owbsys identified by password account unlock; User altered.
Unlock the OWBSYS_AUDIT user account, and set its new password:
SQL> alter user owbsys_audit identified by password account unlock; User altered.
This section contains the following topics:
To properly configure Oracle Warehouse Builder and its repository on a host that runs an earlier version of the database, such as Oracle Database 10g Release 2, you must:
Ensure that the database is fully installed and working; if it is not, see Oracle Database Installation Guide for Linux.
Note of the host name, the port, and Oracle service name of this database. The example here uses the following connection information: localhost:1521:orcl.
Ensure that you have user name and password for an account with SYSDBA privileges. The SYSDBA privilege has the necessary privileges for making changes to the basic configuration of Oracle Database, Oracle Warehouse Builder, and Oracle Warehouse Builder Repository.
To create an Oracle Warehouse Builder repository in your database, you must first create an OWBSYS schema, and then install repository objects within it. Oracle Warehouse Builder has command-level scripts to perform this task:
The clean_owbsys.sql script drops the contents of any existing OWBSYS schema installations, but leaves the schema otherwise intact.
The cat_owb.sql script checks if an OWBSYS schema exists, and creates it if necessary, and then installs the objects required by Oracle Warehouse Builder 11.2 repository.
The reset_owbcc_home.sql script ensures that Oracle Warehouse Builder uses the 11.2 version of the Control Center Service.
[Optional] The remote_owb_install.sql script, when executed on the server, ensures that a repository on a remote system can be installed; it sets the REMOTE_OWB_HOME variable for authentication by remote systems.
Starting with Oracle Warehouse Builder 11.1, the metadata repository is stored in the OWBSYS schema, inside a workspace. This contrasts with the terminology of Oracle Warehouse Builder 10.2, where a workspace corresponds to a repository.
Oracle Warehouse Builder repositories for version 11.2 and 11.1 cannot coexist on the same database; creating an 11.2 repository overwrites the contents of the 11.1 repository in the database. Oracle recommends that you back up the older Oracle Warehouse Builder repositories before installing the 11.2 repository or upgrading to the 11.2 repository.
To clean an existing Oracle Warehouse Builder Repository:
At the command prompt, start SQL*Plus:
C:\> sqlplus
When prompted for user name, log in as OWBSYS user.
Enter user-name: owbsys Enter password: password Connected to: Oracle Database 11g Enterprise Edition Release 11.2 - Production With the Partitioning, OLAP and Data Mining options
Stop Oracle Warehouse Builder Control Center service.
SQL> @OWB112/owb/rtp/sql/stop_service.sql
See "stop_service" for more information.
Connect as user with administrative privileges:
SQL> connect sys as sysdba Enter password: password
Run the clean_owbsys.sql script to drop all the objects in the existing OWBSYS schema:
SQL> @OWB112/owb/UnifiedRepos/clean_owbsys.sql
The process of creating (or refreshing) an OWBSYS schema generates the corresponding locked user account within the specified tablespace. In this example, the tablespace is USERS. When the script completes, you must unlock the account and set its password. The instructions in "Configuring Oracle Warehouse Builder on Linux Installed as Part of Oracle Database 11g Release 2" show how to unlock OWBSYS and OWBSYS_AUDIT accounts. The OWBSYS schema is populated only when you run the Repository Assistant for the first time and create the first workspace in the repository.
To set-up an OWBSYS schema with repository objects:
At the command prompt, start SQL*Plus:
C:\> sqlplus
When prompted for user name, log in as a user with administrative privileges.
Enter user-name: sys as sysdba Enter password: password Connected to: Oracle Database 11g Enterprise Edition Release 11.2 - Production With the Partitioning, OLAP and Data Mining options
Run the cat_owb.sql script to set up OWBSYS in a tablespace in your database. For example, this command sets up OWBSYS in the USERS tablespace:
SQL> @OWB112/owb/UnifiedRepos/cat_owb.sql USERS
If you are installing Oracle Warehouse Builder 11.2 on an older Oracle Database release, or if you integrating Oracle Warehouse Builder with Oracle Business Intelligence Standard Edition (Oracle Discoverer), you must run the reset_owbcc_home.sql script to ensure that the Control Center Service functions correctly.
To configure the Control Center service:
Confirm the correct Oracle home path, paying particular attention to capitalization. In this example, the path is OWB112.
The path entered in the next steps must be an exact match to the Oracle Warehouse Builder home directory, including letter case match.
At the command prompt, start SQL*Plus:
C:\> sqlplus
When prompted for user name, log in as a user with administrative privileges.
Enter user-name: sys as sysdba Enter password: password Connected to: Oracle Database 11g Enterprise Edition Release 11.2 - Production With the Partitioning, OLAP and Data Mining options
Run the reset_owbcc_home.sql script to force the Control Center Service to run from Oracle Warehouse Builder 11.2 installation:
SQL> @OWB112/owb/UnifiedRepos/reset_owbcc_home.sql OWB112
To unlock OWBSYS and OWBSYS_AUDIT accounts:
At the command prompt, start SQL*Plus:
C:\> sqlplus
When prompted for user name, log in as a user with administrative privileges.
Enter user-name: sys as sysdba Enter password: password Connected to: Oracle Database 11g Enterprise Edition Release 11.2 - Production With the Partitioning, OLAP and Data Mining options
Unlock the OWBSYS user account, and set its new password:
SQL> alter user owbsys identified by password account unlock; User altered.
Unlock the OWBSYS_AUDIT user account, and set its new password:
SQL> alter user owbsys_audit identified by password account unlock; User altered.
Using process flows requires that you configure Oracle Workflow for use with Oracle Warehouse Builder. See "Integrating with Oracle Workflow" for details on configuring Oracle Workflow.
You must create a database directory OWB_REMOTE_ADMIN that is accessed by remote installations, so they can read the server's OWB_HOME/owb/bin/admin directory.
At the command prompt, start SQL*Plus:
C:\> sqlplus
When prompted for user name, log in as a user with administrative privileges.
Enter user-name: sys as sysdba Enter password: password Connected to: Oracle Database 11g Enterprise Edition Release 11.2 - Production With the Partitioning, OLAP and Data Mining options
Set the OWB_REMOTE_HOME variable using script remote_owb_install.sql:
SQL> @OWB112/owb/UnifiedRepos/remote_owb_install.sql OWB_REMOTE_HOME
To use a repository, you must define an initial workspace, and the owner of that workspace. The following instructions use the Repository Assistant.
To create a workspace:
At the command prompt, navigate to the UNIX bin directory:
C:\> d OWB112/owb/bin/unix
C:\> pwd
OWB112/owb/bin/unix
Start the repository assistant.
C:\> ./reposinst.sh
On the Welcome screen of the Repository assistant, click Next.
On the Database Information screen, enter the connection information (Host Name, Port Number, and Oracle Service Name) for the repository database, and click Next.
On the Choose Operation screen, select Manage Warehouse Builder workspaces. Click Next.
On the Choose Workspace Operations screen, select Create a New Warehouse Builder workspace. Click Next.
On the New or Existing User screen, select Create a workspace with a new workspace owner. Click Next.
On the DBA Information screen, enter the User Name of a user with a CREATE USER privilege, and that user's Password.
Click Next.
In the Workspace Owner (New) screen, enter the following information:
Workspace Owner's User Name (wks_owner1)
Workspace Owner's Password
Workspace Owner's Password Confirmation
Workspace Name (wks1) (Workspace names cannot contain spaces)
Click Next.
In the OWBSYS Information screen, enter the OWBSYS Password. Click Next.
You need these credentials to seed the OWBSYS schema.
[Optional] For remote installations (when the schema is on a remote system), the system performs the verification of versions, and displays the message: "Found Oracle Warehouse Builder software with the compatible version installed locally on the database server with path REMOTE_OWB_HOME."
If the version is either incompatible or cannot be found, then the system displays the message: " Oracle Warehouse Builder software with the compatible version must be installed locally on the database server." If the compatible version is installed, then acquire the DBA user credentials and run the remote_owb_install.sql script from the system where Oracle Database is installed, as described in "Setting the Oracle Warehouse Builder Home for Remote Installations".
On the Select Tablespaces screen, enter the following information:
Tablespace for Data (USERS, or the name of the desired tablespace)
Tablespace for Indexes (USERS, or the name of the same tablespace)
Tablespace for Temporary Data (TEMP)
Tablespace for Snapshots (USERS, or the name of the same tablespace)
Click Next.
This step enables you to change the default tablespace details. Oracle Warehouse Builder Repository is stored in the OWBSYS schema, but you must identify what tablespaces are used to store OWBSYS and certain other objects, like snapshots. You may choose tablespaces other than USERS, depending on your storage management strategy.
On the Select Languages screen, select the Base Language from the menu.
[Optional] You may also select additional Display Languages from the list of Available languages on the left side, and move them to the list of Selected languages on the right side.
Click Next.
On the Workspace Users (Optional) screen, select the appropriate existing users from the Available list add them to the Selected list.
[Optional] Click Create New User to make new users who can access Oracle Warehouse Builder. This takes you to step 15.
Click Next. This takes you to step 17.
[Optional] In the Create New Database User screen, enter the following:
User Name (demo_user)
Password
Re-enter Password
Click OK.
DBA User Name (system) and DBA User Password are disabled fields and cannot be edited.
In the Workspace Users (Optional) screen, click Next.
On the Summary screen, click Finish.
After the Installation Result screen appears, click OK.
This section describes how to configure the Repository Browser environment within Oracle Warehouse Builder, and Control Center Agent for Oracle Application Server. Procedures for installing optional components are also described.
This section includes the following topics:
The Repository Browser connects to Oracle Warehouse Builder repositories and enables you to view metadata, run Web reports, perform lineage and impact analysis on your metadata, and audit run-time executions.
When you install Oracle Warehouse Builder from Oracle Universal Installer, the Repository Browser is also installed and runs in all the languages that you selected during installation.
To verify the installation, start the Repository Browser listener and then the Repository Browser. For information on how to use the Repository Browser, refer to Oracle Warehouse Builder Data Modeling, ETL, and Data Quality Guide.
By default, Repository Browser sessions time out after one hour of inactivity. To change, edit the web.xml file located at OWB_HOME\owb\j2ee\applications\owbb\WEB-INF by updating the session-config tag.
By default, the tag displays as follows:
<session-config> <session-timeout>60</session-timeout> </session-config>
The procedures in this section describe how to install and configure Control Center Agent to run in Oracle Application Server. This section includes the following topics:
"Configuring the Control Center Agent Web Service (jrt-web.war)"
"Installing Code Templates for Use from Control Center Agent"
This section describes how to modify the OC4J startup script.
To modify the OC4J startup script:
Ensure that you are in the application server configuration directory, AS_HOME/opmn/config. AS_HOME stands for the root home directory of the application server.
Alter the contents of the file as demonstrated in the following example, where bold font indicates the edits you must make.
Setting MaxPermSize parameter at 128M allocates enough PermGen space to OC4J to run the Control Center Agent.
The Python.path sets the path for the Python library files used by the Control Center Agent: jython_lib.zip and jython_owblib.jar. These two files are in the OWB_HOME/owb/lib/int directory.
The km_security_needed property determines if restrictions are applied to the types of operating system commands enabled by Oracle Warehouse Builder Code Template script that runs in the Control Center Agent. Setting it to true enforces restrictions.
To review the list of commands allowed by this security mechanism, check the file AS_HOME/j2ee/home/config/ct_permissions.properties (it can be specified in the jrt.xml configuration file), which is available after Control Center Agent successfully installs in the OC4J in Application Server.
<ias-component id="default_group">
<process-type id="home" module-id="OC4J" status="enabled">
<module-data>
<category id="start-parameters">
<data id="java-options" value="-server
-XX:MaxPermSize=128M
-ms512M -mx1024M
-XX:AppendRatio=3
-Dpython.path=/home/lib/jython_lib.zip:/home/lib/jython_owblib.jar
-Dkm_security_needed=true
...
</ias-component>
To set up the Control Center Agent server-side logging:
Ensure that you are in the OC4J server configuration directory, OC4J_HOME/j2ee/home/config/. OC4J_HOME stands for the root home directory of the OC4J.
Alter the contents of the file as demonstrated in the following example, where bold font indicates the edits you must make.
In the log handler section, the jrt-internal-log-handler is the handler used by Control Center Agent run-time logger to create log files.
In the logger section, you are creating the logger for Control Center Agent run-time auditing.
<!-- The log handler used by JRT run-time logger --> <log_handler name="jrt-internal-log-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory"> <property name="path" value="../log"/> <property name="maxFileSize" value="10485760"/> <property name="maxLogSize" value="104857600"/> <property name="encoding" value="UTF-8"/> </log_handler> ... <!-- The JRT run-time logger for run-time auditing --> <logger name="oracle.wh.jrt.server.audit" level="ALL" useParentHandlers="false"> <handler name="jrt-internal-log-handler"/> </logger>
To configure the audit data source:
Ensure that you are in the OC4J server configuration directory, OC4J_HOME/j2ee/home/config/. OC4J_HOME stands for the root home directory of the OC4J.
Define the audit data source as demonstrated in the following example, where bold font indicates the edits you must make.
<managed-data-source name="AuditDS" connection-pool-name="OWBSYS Audit Connection Pool" jndi-name="jdbc/AuditDS"/> <connection-pool name="Oracle Audit Connection Pool"> <connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="username" password="password" url="jdbc:oracle:thin:@//localhost:1521/ORCL"/> </connection-pool>
To configure Control Center Agent security roles:
In a Web browser, navigate to the Enterprise Manager home page.
Log in using the oc4jadmin credentials. You may be prompted to activate the oc4jadmin account. If prompted to activate the account:
Create a password for the oc4jadmin account to activate it. Enter the password you want to use. Confirm the password and click OK to activate the account.
On the Cluster Topology page, locate the link to the OC4J instance installed under the Application Server.
Click home (the OC4J instance).
This takes you to the home page of the OC4J instance.
On the OC4J home screen, click the Administration tab.
On the Administration Tasks screen, expand Security.
Click the task icon next to Security Providers.
On Security Providers screen, click Instance Level Security.
On Instance Level Security screen, click the Realms tab.
Under the Realms tab, in the default realm jazn.com, click the number in Roles column.
On the Roles screen, click Create.
On the Add Role screen, enter Name OWB_J2EE_EXECUTOR.
Click OK.
On the Add Role screen, enter Name OWB_J2EE_OPERATOR.
Click OK.
On the Add Role screen, enter Name OWB_J2EE_OPERATOR.
Under Assign Roles, in the list of Available Roles, select OWB_J2EE_EXECUTOR and oc4j-administrators, and move to the list of Selected Roles.
Click OK.
On the Add Role screen, enter Name OWB_J2EE_ADMINISTRATOR.
Under Assign Roles, in the list of Available Roles, select OWB_J2EE_OPERATOR and OWB_J2EE_EXECUTOR, and move to the list of Selected Roles.
Click OK.
Under the Realms tab, in the default realm jazn.com, click the number in Users column.
On the Users screen, click user oc4jadmin.
Under Assign Roles, in the list of Available Roles, select OWB_J2EE_ADMINISTRATOR and oc4j_app_administrators, and move to the list of Selected Roles.
Click Apply.
On the breadcrumb, click Instance Level Security.
Under the Realms tab, in the default realm jazn.com, click the number in Roles column.
Click Create.
On the Add Role screen, enter Name OWB_INTERNAL_USERS.
Click OK.
You must create two JMS queues, for JRT:owbQueue, and for JRT:owb_abortQueue.
To create JMS Queues:
On the breadcrumb, click OC4J:home.
On the OC4J:home screen, click the Administration tab.
Expand Services, and then expand Enterprise Messaging Service.
On JMS Destinations screen, click Create New.
On Add Destination screen, choose Destination Type Queue, enter Destination Name owbQueue, select Persistence In Memory Persistence Only, and enter JNDI Location jms/owbQueue.
Click OK.
On Add Destination screen, choose Destination Type Queue, enter Destination Name owb_abortQueue, select Persistence In Memory Persistence Only, and enter JNDI Location jms/owb_abortQueue.
Click OK.
To ensure that system commands such as linux ls, sh, and so on, can run normally in scripts within the Control Center Agent, the environment variable PATH must be hold the directory that contains the system commands.
To set the PATH environment variable:
On the breadcrumb, click OC4J:home.
On the OC4J:home screen, click the Administration tab.
Expand Administration Tasks, then expand Properties.
Click the task icon next to Server Properties.
On the Server Properties screen, scroll downwards to Environment Variables section.
Under Environment Variables, click Add Another Row.
Enter PATH in Name, and fill Value with directories that contain the system commands.
Click Apply.
To deploy the Control Center Agent to OC4J:
On the breadcrumb, click OC4J:home.
On the OC4J:home screen, click the Applications tab.
Click Deploy to begin deploying Control Center Agent.
On the Deploy: Select Archive screen, under Archive, select Archive is present on local host. Upload the archive to the server where Application Server Control is running.
Click Browse and locate the jrt.ear file in the OWB_HOME/owb/jrt/applications directory.
Under Deployment Plan, select Automatically create a new deployment plan.
Click Next.
While the upload is in progress, you see the Deploy: Uploading screen.
On the Deploy: Application Attributes screen, enter Application Name jrt, and Context Root jrt. Leave the other attributes at their default values.
Click Next.
On Deploy: Deployment Settings screen, leave all attributes at their default values, and click Deploy.
After the application is successfully deployed, a confirmation message displays.
On the Confirmation screen, click Return.
Under the Applications tab, expand All Applications, then expand default.
The new application CCA is up.
The Control Center Agent Web Service is deployed automatically with Control Center Agent. No additional setup is required.
To check that the Web Service is running:
On the breadcrumb, click OC4J:home.
On the OC4J:home screen, click the Web Services tab.
Under the Web Services tab, select JRTWebService and click Test Service.
On the Test Web Service: HttpSoap11 screen, under Discovered Web sites, select the http site and click Test Web Service.
The JRTWebService endpoint screen displays that the Web Service is running.
You can access the operations available from the Operation drop down box, fill in the required parameters, and then click Invoke to execute the operation.
[Optional] Alternatively, go to http://AS_hostname/jrt/webservice.
To use the Web Service with a secure Web site (available only to admin users):
Create or modify the secure-web-site.xml file in the config directory.
A sample secure-web-site.xml file is listed below.
The relevant code is in bold typeface.
Particularly, ensure that protocol is set to https, secure is set to true, and a secure http port is identified. Additionally, you must create a keystore file and add the ssl-config entry (you must use an absolute path for the key store file).
<?xml version="1.0" standalone="yes"?>
<web-site
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation=
"http://xmlns.oracle.com/oracleas/schema/web-site-10_0.xsd"
display-name="OC4J 10g (10.1.3) Secure Web Service"
schema-major-version="10"
schema-minor-version="0"
protocol="https"
port="4443"
secure="true"
>
<ssl-config keystore="directory_path/owb/jrtrun/config/serverkeystore.jks"
keystore-password="password"/>
<default_web_app application="default" name="defaultWebApp" />
<web-app application="system" name="dms0" root="/dmsoc4j" access-log="false"
load-on-startup="true" />
<web-app application="system" name="dms0" root="/dms0" access-log="false"
load-on-startup="true" />
<web-app application="system" name="JMXSoapAdapter-web" root="/JMXSoapAdapter" />
<web-app application="default" name="jmsrouter_web" root="/jmsrouter"
load-on-startup="true" />
<web-app application="javasso" name="javasso-web" root="/jsso"
load-on-startup="false" />
<web-app application="ascontrol" name="ascontrol" root="/em"
load-on-startup="true" ohs-routing="false"/>
<web-app application="jrt" name="jrtws" load-on-startup="true" root="/jrt" />
<!-- Access Log, where requests are logged to -->
<access-log path="../log/secure-web-access.log"
split="day" />
<!- Uncomment this to use ODL logging capabilities
<odl-access-log path="../log/secure-web-access" max-file-size="1000"
max-directory-size="10000" />
-->
</web-site>
After you create the secure-web-site.xml file, deploy it to jrtws.war, you may access the JRTWebService securely through https://hostname:4443/jrt/webservice.
To enable Audit Table logging, you must set up a connection pool, and then a managed data source before Control Center Agent deployment.
To configure the OWBSYS Audit Connection Pool:
On the breadcrumb, click OC4J:home.
On the OC4J:home screen, click the Administration tab.
Expand Services.
On the JDBC Resources screen, under Connection Pools, click Create.
On the Create Connection Pool - Application screen, under Application, select default.
Under Connection Pool Type, select New Connection Pool.
Click Continue.
On the Create Connection Pool screen, enter\W the Name OWBSYS Audit Connection Pool. Under URL, select JDBC URL, and enter the URL (in this example, jdbc:oracle:thin:@localhost:1521:ora111 is used for a local installation).
Under the Credential section, enter the User Name (in this example, owbsys_audit), and enter the Use Cleartext Password.
[Optional] On the Confirmation screen, test the availability of the connection. Click Test Connection.
On the Test Connection: "OWBSYS Audit Connection Pool" screen, click Test.
A confirmation screen appears.
|
Note: Application Server 10g is not case-sensitive when verifying Oracle Database credentials; it converts all letters to lowercase before attempting to connect to the database. Because Oracle Database Release 11g Release 1 and subsequent releases are case sensitive, create user credentials in lowercase when using for Audit Table logging to prevent theInvalid username/password error message. |
To deploy Control Center Agent to OC4J, you must also configure the data source for the audit table. This data source is required by Control Center Agent; if not configured, the Control Center Agent deployment fails.
To configure the audit table data source:
On the breadcrumb, click OC4J:home.
On the OC4J:home screen, click the Administration tab.
Expand Services.
On the JDBC Resources screen, under Data Sources, click Create.
On the Create Data Source - Application & Type screen:
Under Application, select Application default.
Click Continue.
On the Create Data Source - Managed Data Source screen,
If you do not require audit table logging, leave other parameters at their default values.
The following instructions demonstrate how to install JDBC drivers for OC4J.
To install the JDBC drivers for OC4J:
Obtain the *.jar file that contains the JDBC driver for your desired platform.
Stop the OC4J service.
Copy the JDBC driver file into the AS_HOME/j2ee/home/applib directory, where AS_HOME is the Application Server home.
Restart the OC4J service.
This section describes the files generated at run time. If you application name is other than jrt, it appears in these directory paths as app_name.
The Control Center Agent files include:
By default, ODL Job log files are located in the AS_HOME/j2ee/home/log/app_name directory.
Each job log resides in its own directory. For example, log file for job 10 is in AS_HOME/j2ee/home/log/app_name/job10/log.xml, and the metadata file for job 10 in AS_HOME/j2ee/home/log/app_name/job10/meta_data.txt.
You may choose to configure Control Center Agent to store the log files in other directories; ensure that Control Center Agent can access these log directories.
The Control Center Agent run-time log file app_name.log employs the ODL log file rotation mechanism. The current run-time log is always app_name.log, while older log files are app_name.log.N, where N is the round of log rotation). By default, this file is:
AS_HOME/j2ee/home/log/app_name.log
Control Center Agent uses a file to keep track of the current job ID in the system; be careful not to remove this file. This file can be in one of two possible locations:
When the Control Center Agent is installed as part of the larger Oracle Warehouse Builder installation, the file is at:
OWB_HOME/owb/jrt/application-deployments/jrt/counter/counter.info
When the Control Center Agent is installed on the Application Server, the file is at:
AS_HOME/j2ee/home/applications/application_name/counter/counter.info
Control Center Agent settings are persisted in the file jrt.xml. You may modify the settings in this file directly, and then restart Control Center Agent. Alternatively, you can modify these settings by changing the attributes of the "JRTAdministratorMBean" in Enterprise Manager. This file is:
AS_HOME/j2ee/home/applications/app_name/config/jrt.xml
The JRTAdministratorMBean enables you to dynamically change Control Center Agent settings without restarting the Control Center Agent.
To change Control Center Agent settings with the JRTAdministratorMBean
On the breadcrumb, click OC4J:home.
On the OC4J:home screen, click the Applications tab.
Expand All Applications, then expand default.
In the jrt row, click the task icon in column Application Defined MBeans.
On the Application MBeans screen, in the left-hand side navigation menu, select JRTAdministrator.
The right-hand side shows all the Attributes and Operations of JRTAdministrator MBean, under the corresponding tabs.
Change the attributes to desired values, then click Apply.
To use a code template, you must install any additional JDBC driver files that it requires to access heterogeneous systems on all the client computers and on the computer that hosts the Control Center Agent.
To install a Code Template:
Load the required JDBC drivers to the OWB_HOME/owb/lib/ext directory.
Import the code templates into any projects that uses them, in the design client.
Import the code template for the project. After it is imported, all users working on the project can use the code template.
When integrating with Oracle E-Business Suite (EBS), you must first import its metadata, and then design mappings for moving and transforming data. Specifically:
During the design phase, Oracle Warehouse Builder users must have access to metadata in the APPS schema.
During the execution phase, Oracle Warehouse Builder users must access the data in the APPS schema.
Because direct access to the APPS production schema may be limited and restricted, you may define a user on the EBS database for Oracle Warehouse Builder users to access only the relevant metadata and data.
To enable access to EBS data and metadata:
Create a user on the database that hosts the EBS. This user needs, at minimum, CONNECT and RESOURCE privileges.
Grant access to the relevant metadata by running the OWB_HOME\owb\cmi\ebs\owbebs.sql script.
This script grants access to the following tables in the APPS schema, which contain metadata for EBS tables, views, sequences, and keys:
The script also creates a synonym in the user schema for each of the preceding objects.
Enable a user to extract data from the EBS database.
You can create a new user, or grant the appropriate privileges to the same user you created earlier. For each object from which you want to enable data extraction, grant this user at least SELECT access.
Oracle Warehouse Builder users can now import the E-Business Suite metadata as described in the importing section of Oracle Warehouse Builder Data Modeling, ETL, and Data Quality Guide.
Oracle Warehouse Builder gives you the option to perform name and address cleansing on your data with the Name and Address operator. The Name and Address operator identifies and corrects errors and inconsistencies in name and address source data. The operator identifies inconsistencies by comparing input data to data libraries supplied by the third-party name and address cleansing software vendors. Purchase the data libraries directly from these vendors.
To install data libraries, refer to the installation instructions of the name and address cleansing software vendor of your choice. For the list of certified name and address cleansing software providers, refer to Oracle Technology Network at http://www.oracle.com/technetwork/developer-tools/warehouse/overview/index.html.
To integrate with third-party name and address data libraries:
Install Oracle Warehouse Builder as instructed in this guide.
Purchase data libraries from certified vendors listed on My Oracle Support at https://support.oracle.com.
Install and access the certified vendor's data libraries and Name and Address adapter following the vendor's instructions.
If you are installing in an Oracle Real Application Cluster environment, then you may be able to install the name and address adapter on many nodes to benefit from the parallelism and failover enabled by Oracle RAC architecture. Check with your vendor to see if your purchase license allows a multiple-node installation.
You are not required to install the data libraries on multiple nodes. However, if you install all data libraries on one node, then performance may suffer due to file access time latency. Follow the recommendations of your name and address cleansing software vendor.
Design a mapping using the Name and Address operator to cleanse name or address data. Refer to Oracle Warehouse Builder Data Modeling, ETL, and Data Quality Guide for information on designing mappings using the Name and Address operator.
If you plan to use Oracle Warehouse Builder process flows, then use Oracle Workflow to enable deployment as described in this section.
|
See Also: Oracle Warehouse Builder Data Modeling, ETL, and Data Quality Guide for more information about schedules. |
To enable integration with Oracle Workflow:
Stop all running OC4J instances.
Locate Oracle Workflow installation program, at OWB_HOME\owb\wf\install\wfinstall.*.
If you installed Oracle Warehouse Builder 11g on Oracle Database 10g Release 2, separately download the software for Oracle Workflow 2.6.4.
Start Oracle Workflow installation program.
On Windows, enter the following at the command prompt:
C:\> cd OWB112\owb\wf\install C:\OWB112\owb\wf\install> wfinstall.bat
On Linux, enter the following in the shell:
% cd OWB112/owb/wf/install % wfinstall.csh
If you use multiple Oracle databases, you must unset the environment variables related to Oracle, such as ORACLE_HOME, ORACLE_SID, ORACLE_PORT, and LD_LIBRARY_PATH.
Complete the Workflow Configuration Assistant using following values:
SYS Password: sys_password; use the SYS password for the database where installing Oracle Workflow.
TNS Connect Descriptor: hostname:port:service_name, where the values correspond to your database.
Because the assistant does not reference the tnsnames.ora file, do not use a net service name.
LDAP Parameters: this is optional; see Oracle Workflow documentation for details.
Mailer Parameters: this is optional; see Oracle Workflow documentation for details.
Tablespace: this is optional; you may change the tablespace.
Click Submit to start the Workflow configuration process.
The configuration process can take several minutes. Check OWB112/owb/wf/install/wf.log for messages to follow the progress of the configuration process.
When the process is complete, the Workflow Configuration Assistant displays a message of completion.
Install the Workflow Client [Optional].
The installation of Oracle Workflow client is optional because the Process Flow Editor in Oracle Warehouse Builder replaces its functionality. You may want to install Oracle Workflow client to view the deployed Oracle Warehouse Builder processes in Oracle Workflow.
On the computer that hosts Oracle Warehouse Builder client, install Oracle Workflow client from Oracle Workflow client CD.
When the Workflow instance is not on the same computer that hosts Oracle Warehouse Builder repository, you must create a proxy user.
Within the database hosting the repository, use SQL Plus to create a user and grant it the OWB_USER role as a default. It enables the remote Oracle Workflow instance to connect to the services provided by the Control Center.
Considerations for the OWB_USER Role
If you encounter a problem when trying to grant the OWB_USER role, then possibly OWB_USER exists in an earlier Oracle Warehouse Builder implementation. In this case, you must first rename the existing OWB_USER to something else before you can grant a user the OWB_USER role in the current release. In order to retain the properties for the renamed role, you must register it in the new installation of Release 11.2.
This section discusses the architecture and components of Oracle Warehouse Builder and provides installation and configuration procedures.
This section includes the following topics:
Depending on the business needs of your organization, you may be implementing different types of Oracle Warehouse Builder installations:
The primary installation of Oracle Warehouse Builder, which includes the installation and configuration of the main design repository.
Optional installations on client computers where developers and administrators run Oracle Warehouse Builder client software, which do not contain a repository.
Optional installations on hosts that run the Control Center Agent service, but do not contain a repository.
Optional installations on database server hosts, where ETL jobs run and where the repository stores only run-time data.
|
See Also:
|
This section describes some common installation configurations, and shows how the various components interact. The primary Oracle Warehouse Builder components include:
The Oracle Warehouse Builder Client (which includes the Design Center and the Control Center Manager)
Depending on your business needs, there are many possible installation configurations. The five most common topologies, that are illustrated in this section, are:
|
Note: In any of these topologies, it is typical to have multiple design clients. For example, each Oracle Warehouse Builder developer or administrator usually has a corresponding, installed Oracle Warehouse Builder client, also called a design client. |
When everything is running on the same computer, the database home for Oracle Database 11g Release 2 contains all the components needed to run Oracle Warehouse Builder, as illustrated in Figure 1-1.
Figure 1-1 Single Computer Topology for Oracle Database 11g Release 2
If separate computers are being used to run the client and to host the repository, then all computers must have Oracle Warehouse Builder software installed, as illustrated in Figure 1-2. For the database server installation, Oracle Database 11g Release 2 includes the necessary components. For the client, you must install the Oracle Warehouse Builder software from the standalone install.
Figure 1-2 Two Computer Topology; Separate Client and Database Server Installations
|
See Also: "Working with Oracle Warehouse Builder Standalone Install Package" for Oracle Warehouse Builder client installation procedures. |
If a database on a separate computer is being used to run mappings designed on another database, then all computers must have the Oracle Warehouse Builder software installed, as illustrated in Figure 1-3. For the database servers, the installation for Oracle Database 11g Release 2 includes the necessary components. For the client, you must install Oracle Warehouse Builder software from the standalone install.
You must prepare Oracle Warehouse Builder repository on all database server computers. As illustrated in Figure 1-3, one acts as the design repository (Server1). The additional servers where mappings run, each have their own repository (shown as Server2), which in this case functions as a run-time repository. The Control Center Service on the execution database server deploys and runs the code.
If Oracle Warehouse Builder client, the Control Center Service, and the repository run on different computers, then all these computers must have Oracle Warehouse Builder software installed, as illustrated in Figure 1-4. For the database server, the installation media for Oracle Database 11g Release 2 includes the necessary components. For the client, you must install Oracle Warehouse Builder software from the standalone install image. For the Control Center Service, you can use either type of installation. However, Oracle recommends that you use the standalone image because it installs only the components that Oracle Warehouse Builder requires.
Figure 1-4 Separate Client, Control Service Center, and Database Server Topology
|
See Also:
|
If separate computers are used to run client, the Control Center Agent service (CCA), and the repository, then all computers used to deploy or run Oracle Warehouse Builder code must have installed Oracle Warehouse Builder software, as illustrated in Figure 1-5. For the database server, the installation for Oracle Database 11g Release 2 includes the necessary components. For the client, you must install Oracle Warehouse Builder software from the standalone install image. For the Control Center Agent service, you can use either install. However, because the standalone image only installs Oracle Warehouse Builder-required components, Oracle recommends this option.
In some deployments, a Control Center Service is required on a host that does not have an Oracle Database installed. For example, if you use code template-based ETL mappings where part of the mapping executes on a non-Oracle database, then you can run a Control Center Agent on that non-Oracle database host. In such a case, you can install Oracle Warehouse Builder software on the non-Oracle database host.
Also note that:
On the non-Oracle database host, the only component of Oracle Warehouse Builder software that is used is the Control Center Agent. The rest of the software is present but not used.
The CCA may be located with Oracle Warehouse Builder client or Server1, in which case no additional installation would be necessary.
In Figure 1-5, the Map1 has three execution units (a, b, c). The first two are Load Code Templates (LCTs) and the other one is an Oracle Target Code Template.
Oracle Warehouse Builder provides the Check for Updates wizard within Design Center to simplify locating and downloading new resources for Oracle Warehouse Builder as follows:
Links to updated release notes, white papers, sample code, and other information resources.
New code templates, platform definitions and, drivers to extend Oracle Warehouse Builder for new sources and targets.
New experts, scripts, and other utilities that enhance Oracle Warehouse Builder or help address specific use cases.
Resources delivered through the Check for Updates wizard may consist of links to My Oracle Support, downloadable documents, or zip archives. Installation instructions are included for client-side and server-side components with each resource as needed.
|
See Also:
|
|
Note: Oracle Warehouse Builder Repository Assistant can be started fromOWB_HOME/owb/bin/unix/reposinst.sh on Linux or OWB_HOME\owb\bin\windows\reposinst.bat on Windows. |
Installation and Administration Guide
11g Release 2 (11.2)
E17130-05
September 2011
Oracle Warehouse Builder Installation and Administration Guide, 11g Release 2 (11.2)
E17130-05
Copyright © 2000, 2011, Oracle and/or its affiliates. All rights reserved.
Primary Author: Richa Agarwala
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
This program contains Batik version 1.6.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
For additional information about the terms and conditions, search for "Apache License" in Oracle Warehouse Builder online help.
This section contains the following topics:
This document is intended for all persons responsible for installing Oracle Warehouse Builder, including:
Data warehouse administrators
System administrators
Data warehouse and ETL developers
Other MIS professionals
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
For more information, see the following documents in the Oracle Database 11g Release 2 documentation set:
The following text conventions are used in this document:
| Convention | Meaning |
|---|---|
| boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
| italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |
6zUF鬴j뭸b雦+쩈j4
+-j <-NAU[j ~{kg*;6lګ2;ϿG,k gv&PlɚZ|1,첻 ,";8<@ Y1H'L7F8tQ?mXg\C
4Vcdmhlp/^[7 5]/<==Y㎛އ?$~/iwXw=F0aw"#>
.{쮏7_>w|N}#|8W<[|_?=w?c O>я7 o>}>zT3vD r &HF9@nu aFH:@ hk
JpU6ԡ}!ч ֡e C'L=`W:܅0n(̢ŧpJ-, O: |*Ї}EPa
Ua ]B * 4Lxf`ׅ:b<
!P!M7aA]mmPD$
U H .c581 ,F # AdL@"<8F0" )i_(-)XchNsx\ CƄLg9CBNGDyL ^M"#qenu @JW X^ͺ_UpSHU\u^W;P;F+wLk-YFѢ
M BrC"Rb} 0qhbBxp-gikζTy(^1]rܫ8Lejc96<` ax@7
H^Bt(ZAW\ϸ5Nq y %bwmF%CΏ^Q" YG:g<\ (@ XɾeIJ^qy&v$zkeYծI}O"xytrB D; qr+!Nΰ펈D,}H$d?]iρGEGB4Oxԧ^g]qîE/FJm9U~fnqjs!\&NlM( G D"O~c!(D+~.7]H|=pX:իu&A_=猴{ ?~>"8"w.k4BDBdb
CDDx0DAG{DCwp}GyW"tD~GqJ LW~w~~gu7
Go4'{W%" c9RNFzwȷGCxB%l'S8氅P^H
`0Pp l o
vPzc W>؇~n"8#?l@$AdOv` 怅Yxx[_cH
@
@Hɐ
X c8(#D
8|DuP]`Dȉ`X]8X|pH
p Xp@
| |` vP؏Ջ# E} \ G\u_ s̭_~xvݽ7[x_~^}ݿ ?xo_?0& @D0AdA 0B 'p /tB
7C?1DCOD1EWd[1FgF_1G wG aG!$H#M H%dI'J+2K-K/|2L1Ǵ(I tr2dI3wD8ۤN qN%O?c3G> OCG
/ zԯHi+tF%t ESOE)24PQ 5LMM4.YS[o%E`^
`EU V@M(rH dE`ttk]TeV\e5 z4Xp4_z'}w{^Y%m7bWS5VXb3VYfA haEA[i}=x#=-h\Qmo@ɵh`m蜇ye/DLh6ƥUi;
6l&lF;mfm߆;n离n;ool'p - `'x +<'Ǽ??=#"
⑂VCguF
ʜ5kg/
fwwoأ6(UE]LoW.]m'w,擝d6|/R {ߟKPYϭ{B(@mdw *L \4 Ђ+˶G \ ^7 Є'Da
UBЅ
@@8C뉐7lC D8D"шGDbD&6щOb8E*VъWbE.vыN D6Rьw+ط4эjG9u[JG8 9H x3!HE2RnG%16Mnrm#(=9H1~ EJ6r[+JO2$)e9F[r L2LGdlt۠yKcFle5yҚ7d$!ll' ,lw58Dr yauhQgOl L >FieZfrBoo
g@V)d8dtJf2g_fgTg{!ղvvZdKgioVEuOf,BrN8glhVe²{ByeĖjۆomq7jnn\QoTAnձ#%8nq k9o/Q8 8 hx֗qĈֆF,fnŅȉS Jxvt. @AvX0$vs"qG
V pP8MkuXsotHa`&(s!cs*s8'^rszSsytTg[yC$ Iv68. #zw 'w x3 yxu7AI}
HWzC)Xo\ ե_9[dIa/8iI,ɖovhiKQ ᒗ~{i ~]w()iIH%s !$~G#{v 0|o,ÙwƧ| {" q 5B! 1"y#
+w} ~J&}|A֏~{י&T(~ )I|02G' *e ߉aঢ়֙d2/7ٖ`)'h|{{Av Р'2Ȏ umB c,'^$;ts *ڏ r 5+2/*8dB|bs'wb6>#jA*+`DpT:I'H
-hse!e;h:5so3ukɖskvʧ;yj}*{99fB1 0 j=1 : [*W4J 68x*g~t_1Q-9w: i ZA:͢+ 'i2T36 # 4n2` Je'g)5ulja!l yoQub#3:"oaRr#22 NC1lq M# k$BIC/ʰz] SM\#)R%)Fj)1B(-{(;)}7
۪ +"+N(K{*Mˮ=i0,`p 3-@ v9F]-e?/dve,li*2)n¸蹸?Y+`RɍC#B/+6h@ HRq^ 'MaS{n-~{(۸K)C0"c.w/g%s22\
.֨j0m )khśw[rX5Nro3uG1r7N(7y5R
**31JD&8c rl&KnG_NM"llSZC3 E6AQk£cv |' kYQZ$B7c7[< #C㻳X9{;* Ga
vyO9,`:2:C\PŇ)FZ]͚:ZfŮybnHBf4fuq Y i@H/ب:{vtGƼ2\zkEW 5s Rǧ
0D}87)ablZXǞa&8|uuuYˮ*0zi_7&lp̅ax[b_#+aGǾ$قmZv %,2b Xv!<ZR϶h}(8QwoEl
Ĭͺ7 [8b"0 uKkRfWǐ*(,8-gb/=2gre-M7M
S#}+#q]l&<DBHѓw^ \˗%sZrsͭXxP"͕mmy~ 3Q,Y ]X*؇Y|ئذWyU
ŕMs ЩJِmٚʪ٦Mkj
al; ђ8 Jb}gƦ13g6m}w5
ܥ }7ݱ-A杚9 ]ٚL2ݾb~
NZ#34af ΈJD 1k ޘMI+A )k a%)=i`㩴
Fdq1QӼxba1~>~A.P&, h~SW %a^~. 8Y+˹g,ה; "}}A/ia~:+)6~rfZFNU(^q.n-`*ڡK=m .^./E" In hꖒ#ә氮ur؎>Rx֟n;ŗɸ6c4
P
qa
5[
$dTyWZ, <%W# ^ݬY+x|6.Yp.6///85g5$+>ؓxO ]2@,Č;_7AP!6q_݂>ϪN GA W?;lq zƆ
mtw
h` cf?{t
=P%\D
خ `JHzÒ(m__Lc^_* Px6IhHNu4 ha}Hf(ن ύ& hZwX KJmj c/(hߎПb2ɛ^y V$$Ȏ
> `
~P @
HQ >xPcb$hdI NJ\x2A/Y΄)p#Ĕ9iD9ʑm:ĩ2B$|y3ϊB:0dˌ W (ʚ2r%I5eY = PgNoΥ[]y_ P ( <@ W AZ OEBL2aÈ~ =G$9$
.p;ps+ K 7:k,z%É
mm ^2үgמy; ~{LC
:o9soL/+0#pB
0%
CÃ> :STqEH DAҐE sF YQD*rhH$rI&!4 % sj rKrB/sL24sK z駧zYx ! %|:Ǚ|8GͱWHt :A/>W~ٳ^@60u7 kcB'A9ĬyDa
UBF`" \`{ << }
D` 0Ba" @C
\ < =!C @0t " /dcя N*Q
f,CЅ.r+ ' d&5IN P!1:!x1kMz@&@8&* a$ lp
7,z3zqG I(# 5p!| =M
#xmde'չNvn#[_e
a0C^>O~ӟh@:PԠEhBP6ԡhD%:QVԢ-ަ4Qvԣ H6RԤ'EiJURԥ/iL=%7iNuS:D?jP:TըG5M7hӞ6թOjT%TVժWjVeRkX:֍nլgEkZՊ֮.dk\:Wծwk^*f!<E&V ),bb.v!mHb!KWnjlf5վ%GaEXdEdAȎv
mjekV-iukZڢַmlg w!Enr\v ɯH _E
x~6? JMiMaV~[b9酊P$^殈ɮA9 !4. :)vh`ZȔFuo1@քuD D<"Mc")Ijy<#199[69|%%AQRL)>Yn-'[b͕+yl
sӳ%0M!Fti;17v`;G܍/5.+f s&*<:yfe{f֙H@)?Y /Q )>+( 38 )r1͐@
4V[yL3)bؙƼ3O?b0BKI:^Ҕsj`Fr+"QX{Gţܕ2X
α1_e&UDUVI'Lmh!ЛqdKCe֑u]aV?<,b:Gm KcVgJvs^5RYEFֳSLE۰~[5@pڤv5dfGIӊ$#AR9 utZE@H~K&O PP`E l4ӮH#EqZ&J*@\
)Z
2DHc鯆 `l8#N@%8O@ 8CTpBPNaf
8e,U)kkTN,c (f1>~7_XED0 @1 0 )*YrLyʲ'^[dt`0'{BG'Umq
Z8=hBЇFthF7я64E =iJWҗt5iNwnsE=jRΥFuU]\KB)ҁW$sY:N7^u
j>HբH8Ԏ6n]mmC!
=nrmh rZ؆uPμ: o- ӽఛ/\Ƣ9A&nk/(>v "ryv.wSظ$ǹD\!5=s9:ĕ. t4
})NV+Dحήcgc0 m7zD =] MAvgս~o,8s.u4 o% @AGF-t_B6[_ #d S=82 #N3Ӎ8d_?6s?V]CF5)AY[\!#e6Ilz!^`.vk mXdf1tX`M Ճ Qr|UrwAo%Sw,ʛ n͉pW
\<嚓8m: 9s3[ ðiKlHQڐr:=5tC{o1('"atEX"hOcN1j!r(g+VD7ej(_ D"o#61 <ٴXi5IfO$ί}hsws] PL @ 98R%T/ b`L dȮC/йF//L_d< |OJЄAB8 QYeRY!##%#`QCCTa pQ *Kp/$&quAHU#nP
h!# x~8<@88&DxfH㥄LP8F%Tx:eX3f] \8+bH/g8 ᅢN@ nGtJvVA%Y4A08rb V'W\}WQ $HlX2[ZXGUQZ q XV!h\tňs ("V!WU u JrY0$xN,8F/ByY>xר$h AQI8ZG vqUUxØV؊X wBXVp[8l"["E)eRu)!p&n[oGsx G*( I b +(
@ !
Z
@x13QЁ@g2?1BG"H48HQY}u AuZ 9%;)\3y "\b)q!!q%`u)Ǔj?97yZy!5) !:^i(/ј5%s2)cAٙ'ÙAayٚ&GwAyaYY y
6 BRa.ƙH aEHyj-`)y. P3q. f__f-!*e)M RID,J-I$#M$zY`Rau`藛dў ]:9 2:ٓ ԡ$jL[P 1+b-ʢ0bIb1.Z!d% q?
qbA*D/b2vJzp< s 1PJ>\:/Mf] f7lofclyu_7l:=fhoz8jjvQʓtz|Zsj4zlyjy{6tƨ1tg~*ڨJgi4z=
E^B=U>~#!6=9BHAm#(`
q>C~# & 郂慾^g$~>#^^> ;w zE>>2^(>F ! ?`>}78 xG>G^ E#\_>(b#f 5jIB }M I?7>݇ ?R
Y~#!__ >R}G I^9
p &@@Н|6
*G1t/LQC'ś|KE V?HEPP)EN1t3Ao<-K/\YEoUL] ]vΓDj`SfDTT6uYqYv[6 ]Q yE^lC}V:<0Y O?NX !Xb 1Ê5Ac,bT@CS9?-)ùBg9=o9̳xd `;:L&6?RYfihInj2ɮ~捧x
?+ K=04Hv:reV{2Oc7(' pV-0mCmi;ՙ<0
G*Σ+K @i Y}ky
o{;^{ !(:|:1"
~R}L1rzh3~@9j`\p<AcI
S
RcMF?4dIE" .Ƅav>BP~I dib 1p3 âIaNX0{aB-}+5*ے"6#]q +%k[ZxO))YͨH.y>2<A< ssW$Jt,%S£N,NFWF\IO GesD
GIJ(Su1Y6y'*ncblB,$K[Mps$B
ڳϵ tPB 0M,
UEQH#TKDR0S.E\ pé$jiL $a:D.H!TH<=v9aA5b]W퓂 )|Ƴc9"i])iMxY/Ia]}ywN_!0 qio:ը^đnP§u'O
ygo&Jp"wN\J3ݿǝwas1r @Ө]X` >i1" :Ff7@buW\!{cYZ(cd"#n4x
+bOChBǂ/L$_E~BnݸE"g=mvnH3Íh"['&ޣC`Rx5g+4@\q"_Woc 8G:юp!8gяb :ҐDd"HCh$ qU$+;J&5INvғ
