Parent topic: Enterprise Back Office on Two Servers
microsConfig.properties
file:
myInsightRootDir=Drive:/myMicros/myInsight
reportDefPath=Drive:/myMicros/myInsight/org
OBIEE.ImageTempPath=Drive:/myMicros/myPortal/imagesTemp
mySecureDocXDir=Drive:/myMicros/myInsight/secureMyDocX (if you are using the docViewer portlet)
/Weblogic/
Install_version.exe
Install_version.exe
to launch the installation wizard.Table 3-16 Oracle WebLogic Application Server Information
Field | Description |
---|---|
WebLogic User Name and WebLogic Password |
Create the login credentials for an administrator account on the WebLogic application server. The password must be eight to 20 characters, must not contain special characters, and must include at least one number. |
Local JVM Path |
Verify the folder path to the local Java Development Kit installation. This install path must not contain spaces. |
WebLogic Admin Server Host Name and WebLogic Admin Server Port |
Enter the hostname and port of the Oracle Business Intelligence server, typically 7001. |
App Server Host Name |
Enter the hostname of the Reporting and Analytics WebLogic application server. |
Node Manager port |
Enter the port used by the Node Manager, typically 9556. |
E:
drive, you can create the mapped drive Z:\
and enter the path as shown in the following image:
Figure 3-3 Mapped Network Drive to OBI Server
myMicros
installation folder. For example, Z:\myMicros\
Make sure the filepath includes the following components: folder_path/file_name.extension
Table 3-17 Database Information
Oracle Database | Microsoft SQL Server |
---|---|
|
|
Table 3-18 Repository Database Information
Oracle Database | Microsoft SQL Server |
---|---|
|
|
Table 3-19 Report Mail Font Configurations
Field | Description |
---|---|
Enable User Font |
Select whether to allow using a custom font when rendering PDFs. You can then enter the path to the font, or click Choose to navigate to the font. |
Limit detail query days |
Enter a date limit for executing audit/analysis detail queries. The Organization configuration can override this setting. |
Limit summary query days |
Enter a date limit for executing audit/analysis summary queries. The Organization configuration can override this setting. |
New Line Style for infoDelivery CSV format |
Select whether to use Windows, Unicode, or HTML line styling when formatting Report Mail items in CSV. |
Load reports by market segment |
Select whether to load reports dynamically by appending the organization or role market segment to the template name. |
http://Gift and Loyalty URL:80/offers/
Table 3-20 Master Server Configurations
Field | Description |
---|---|
RTA database login and RTA database password |
Enter the RTA database login credentials for inserting and updating the |
COREDB login and COREDB password |
Enter the COREDB login credentials for file transport. The account must have the same level of permissions on the Core database/schema. |
Email account name for the Errors Administrator and Email account password |
Enter the e-mail account credentials for the Error Administrator. |
Merak 8.5 or higher |
Select whether Merak 8.5 or higher is installed on the environment. |
Where is the Merak installation located? |
If Merak is installed on the environment, enter the installation path. |
Server1 account password |
Enter the password for the server1 login account. |
Cache type for the Master Service |
Select the Master Service cache type from the drop-down list. |
Table 3-21 Posting Server Configurations
Field | Description |
---|---|
How many posting threads should run on the server simultaneously? |
Enter the number of simultaneous posting threads. Entering a number greater than eight can lead to performance degradation. |
How many days of psLogs should be saved? |
Enter the amount of days that the posting server preserves the Result sets and the entries in the |
What directory should hold psLogs? |
Enter the path to the folder where the posting server saves the logs in .zip format. |
Move History by location rather than full server? |
Select or deselect whether to move history by location rather than moving history by server. If you deselect this option, the admin server stops posting for the duration of the move. |
Limit move history day range |
Select or deselect whether to limit moving history by date. You should typically only use this option when you partition databases by date. |
What name would you like to use for Temporary Menu Items? |
Enter the name the posting server uses for temporary menu items. |
What database user should posting use? |
Enter the database account name for posting. |
What is the password for this user? |
Enter the database account password for posting. |
Run alignment with definitions posting? |
Select or deselect whether to run alignment while posting definitions. Select this option if the environment contains an aggregation engine. |
Table 3-22 Alert Engine Configurations
Field | Description |
---|---|
Push alert service username and Push alert service password |
Enter the login credentials for the push alert service. |
Number of alert threads |
Enter the number of alert threads. |
Portal DB User and Portal DB Password |
Enter the Enterprise Back Office database login credentials. |
Core DB User and Core DB Password |
Enter the core database login credentials. |
Location Activity DB User and Location Activity DB Password |
Enter the location activity database login credentials. |
RTA DB User and RTA DB Password |
Enter the RTA database login credentials. |
CE DB User and CE DB Password |
Enter the CE database login credentials. |
Table 3-23 Admin Server Configurations
Field | Description |
---|---|
Trailer to send in alerts from Admin Server |
Enter trailer text in the four fields provided. |
Email account to send alerts from |
Enter the email name, without the domain, that the Admin Server uses to send alerts. |
Number of hours before a location is considered out of contact |
Enter the maximum number of hours before the Admin Server flags an unresponsive location. |
Email addresses to send long alert messages to |
Enter the email name, without the domain, to which the Admin Server sends long alert messages. You can separate multiple addresses with a comma. |
Email addresses to send short alert messages to |
Enter the email name, without the domain, to which the Admin Server sends short alert messages. You can separate multiple addresses with a comma. |
Email addresses to send copies of org alerts to |
Enter the email name, without the domain, to which the Admin Server sends a copy of all alerts. |
Folder containing custom packages for Admin Server |
Enter a folder path containing custom packages. |
Table 3-24 Aggregation and Adjustment Service Login
Field | Description |
---|---|
Core database login and Core database password |
Enter the core database login credentials. |
RTA database login and RTA database password |
Enter the RTA database login credentials. |
Portal database login and Portal database password |
Enter the Enterprise Back Office database login credentials. |
Location Activity database login and Location Activity database password |
Enter the location activity database login credentials. |
Name for Analysis/Aggregation Instance |
Enter a unique name for this instance of the analysis/aggregation service. The service inserts the name into the database to denote which service processed a job. |
Connection Cache Type |
Select a connection cache type from the drop-down list. |
Table 3-25 Weather Configurations
Field | Description |
---|---|
What is the database login for the Weather Service? |
Enter the username for the database login, typically MSSQL. |
What is the database password for the Weather Service? |
Enter the password for the database login. |
How many days of weather should be stored in the database? |
Enter the number of days of weather information that should be stored and retained in the database. Enter 0 to disable database storage. |
Normal: Review the install folder, features, and disk space requirements.
Advanced: Review and edit individual variables in the installation files, then review the install folder, features, and disk space requirements.
root\temp\MM_Log.log
root\temp\MMInstaller.log
root\myMicros\Uninstall_myMicros\Logs\myMicros_Install_datetime.log
OBI server hostname:7001/console
and log in using the WebLogic administrator account credentials created during the installation.The status may be set to Starting if you check the WebLogic console immediately after completing installation. Verify that the status changes to Running.
beasvc bifoundation_domain_appServ1
Oracle WebLogic NodeManager(path to Oracle Middleware wlserver installation)
Related Topics