Infor MyDayInstallationGuide 1 1 1

7/29/2019 Infor MyDayInstallationGuide 1 1 1

http://slidepdf.com/reader/full/infor-mydayinstallationguide-1-1-1 1/70

Infor MyDay

Installation Guide

Version 1.1



Copyright © 2009 Infor All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor

and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of

their respective owners.Important NoticesThe material contained in this publication (including any supplementary information) constitutes and contains

confidential and proprietary information of Infor.

By gaining access to the attached, you acknowledge and agree that the material (including any modification,

translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein,

are the sole property of Infor and that you shall not gain right, title or interest in the material (including any

modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive

right to use the material solely in connection with and the furtherance of your license and use of software made

available to your company from Infor pursuant to a separate agreement (“Purpose”).

In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such

material in strict confidence and that your use of such material is limited to the Purpose described above.

Although Infor has taken due care to ensure that the material included in this publication is accurate and complete,Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or

other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability,

consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or

omissions in this publication (including any supplementary information), whether such errors or omissions result from

negligence, accident or any other cause.

Revision History

Date Change Description

March 5, 2009 Added step for CSI user in Infor Security setup;

removed InforPublicMDM from restored databases;

added CSI audit step under Creating the ERP

component; added section on verifying codes and

code list synchronization, added appendix forupgrading MyDay content database

March 11, 2009 Revised section on verifying codes and codelists

March 16, 2009 Removed references to accounting entities in App. F

March 18, 2009 Added section on clearing PublicMDM information

March 23,2009 Changed uninstall folder name in App. D.

April 1, 2009 Modified web page references.

April 2, 2009 Added step to App. C.

April 13, 2009 Added step in Installing MyDay section; added App

G, moved sections in post-installation steps

May 20, 2009 Miscellaneous edits

June 8, 2009 Removed step in Post-restoration tasks in App. F

Publication InformationRelease: MyDay version 1.1.1

Publication Date: 8 June 2009



Contents | 3

Infor MyDay Installation Guide

Contents

About this guide................................................................................................................................ 5

Intended audience......................................................................................................................... 5

Organization..................................................................................................................................6

Contacting Infor............................................................................................................................. 7

System requirements........................................................................................................................ 8

Database server............................................................................................................................ 8

Application server..........................................................................................................................9

Client...........................................................................................................................................11

Infor MyDay port requirements.................................................................................................... 12

Preparing for the installation ......................................................................................................... 13

Installation of specific applications .............................................................................................. 15

Customizing component installation (optional) ........................................................................... 19

Changing component properties ................................................................................................. 19

Changing component database users......................................................................................... 21

Installing MyDay.............................................................................................................................. 22

Clearing PublicMDM information................................................................................................... 23

Importing security permissions.....................................................................................................24

Creating security hierarchies – accounting entities ....................................................................25

Creating administrative users for MyDay...................................................................................... 26

Configuring file permissions for Infor On-Ramp.......................................................................... 27

Restoring database contents......................................................................................................... 28

Modifying BIS data inbox properties............................................................................................. 30

Processing Public MDM tenant codes........................................................................................... 31

Starting MyDay routing applications............................................................................................. 32

Starting Infor On-Ramp...................................................................................................................33

Starting Infor On-Ramp in detached mode.................................................................................. 33

Starting Infor On-Ramp in interactive mode (optional) ................................................................ 33

Logs ............................................................................................................................................33



4 | Contents


Creating and deploying a routing definition ................................................................................. 34

Importing the enterprise template................................................................................................ 34

Building and deploying the enterprise components.....................................................................34

Creating a routing and activating the solution ............................................................................. 44

Restarting Infor On-Ramp ........................................................................................................... 46

Starting MyDay applications .......................................................................................................... 47

Synchronizing Public MDM tenant codes ..................................................................................... 48

Restoring BIS data inbox properties ............................................................................................. 49

Verifying codes and codelist synchronization ............................................................................. 50

Specifying an accounting entity in PublicMDM............................................................................ 52

Installing reports ............................................................................................................................. 53

Installing the Infor Reporting report designer .............................................................................. 53

Configuring the auditing feature for Infor Reporting ....................................................................54

Importing MyDay reports (optional) ............................................................................................. 55

Configuring the system for drillbacks........................................................................................... 56

Creating business users for MyDay .............................................................................................. 57

Verifying the installation................................................................................................................. 58

Appendix A: Accessing Infor applications ................................................................................... 59

Appendix B: Password restrictions............................................................................................... 60

Appendix C: Applying patches ......................................................................................................61

Appendix D: Uninstalling MyDay ................................................................................................... 62

Appendix E: Upgrading MyDay...................................................................................................... 63

Appendix F: Upgrading MyDay content ........................................................................................66

Appendix G: Exporting security users and permissions.............................................................70



About this guide | 5


About this guide

This guide describes the system requirements and installation of the components used with Infor MyDay.

It also describes the Infor MyDay configuration to be done after installation.

Intended audience This guide is for professional services or system administrators who install and configure the system.

Prerequisite knowledge

To fully understand the information presented in this guide, you should first read the Infor Open SOAOverview Guide . The Infor Open SOA Overview Guide discusses the major concepts of Infor OpenService Oriented Architecture (SOA) and defines common terminology. That guide also includes a list of

related documents.

Before attempting to install and configure the components needed for Infor MyDay, you should have

some knowledge and abilities in the following areas:

Knowledge of Tomcat configuration

For Windows-based installations, administrative level skills and knowledge for Windows and Microsoft

SQL Server, including:

− Troubleshooting performance and measuring resource demand

− Installing and configuring Microsoft SQL Server

− Configuring a database for local and/or network access

− Creating and dropping SQL Server databases manually

− Using monitoring techniques to assess the performance of SQL databases

For Oracle-based installations, database administrative level skills and knowledge



6 | About this guide


OrganizationThe installation guide contains these sections.

Section Description

System requirements Requirements for the database server, application server, and

clients, as well as reserved port numbers

Preparing for the installation Describes the databases and users to create, a script to run, and a

properties file to edit. Has a matrix showing, if you choose to install

only some parts of MyDay, which applications require which parts

Customizing component installation Steps to customize the installation process

Installing MyDay Steps for the installation.

Clearing PublicMDM information Steps to clear PublicMDM information from several databases.

Importing security permissions Steps to import the initial security permissions into Infor Security.

Creating security hierarchies Steps to define an accounting entity for the ERP in Infor Security.

Creating administrative users Required responsibilities and roles for the various applications, and

steps to create them in Infor Security.

Configuring file permissions On-Ramp configuration files to which you must restrict access.

Restoring database contents Databases to restore - that is, load content into - using backups.

Modifying BIS data inbox properties Steps to modify inbox properties

Processing Public MDM tenant

codes

Steps to process tenant codes

Starting MyDay routing applications Steps to start the services

Starting Infor On-Ramp Steps to start On-Ramp in either detached or interactive mode.

Creating and deploying a routing

definition

Gives the steps to create a MyDay configuration on On-Ramp using

Infor DCA and DEM: import the enterprise template, build and

deploy components, create a routing and activate the solution.

Starting MyDay applications Lists the services that need to be started.

Synchronizing PublicMDM tenant

codes

Steps to synchronize tenant codes

Restoring BIS data inbox properties Steps to restore inbox properties

Verifying codes and codelist

synchronization

Tells how to synchronize and verify the codes and code lists.

Specifying an accounting entity Steps to define an accounting entity for the ERP in Infor PublicMDM.

Installing reports Tells how to install the report designer, configure auditing, and

(optionally) import the MyDay reports.

Configuring the system for

drillbacks

Tells how to use the MyDay Administration application to set up the

ability to drill back from MyDay into the ERP source data.

Creating business users for MyDay Sets MyDay user roles and responsibilities in Infor Security.

Verifying the installation Tells how to make sure MyDay is working properly after setup.

Appendixes Appendixes for post-installation information



About this guide | 7


Contacting InforIf you have questions about Infor products, go to Infor365 Online Support at http://www.infor365.com. If

you do not have an Infor365 account, click Register now and complete the registration. You will receive alog-on ID and password within 24 hours.

When you access Infor365, you have these options:

To access Infor knowledge bases, incidents, documentation, software downloads, and community

discussion forums, click one of the links on the top menu of the home page.

To add an incident, select one of these options from the Incidents menu:

− Add Product Incident - Specify your product, version, and other details, so that your incident

report is sent directly to the support group.

− Add General Information Request - Use this option for all other requests.

To find the Customer Support telephone number for your region, click Contact Infor in the top right

corner of the home page, specify a product name, and click Search.

If we update this document after the product release, we will post the new version on Infor365. Werecommend that you check this Web site periodically for updated documentation.

If you have comments about Infor documentation, contact [email protected].



8 | System requirements


System requirements

Before beginning the Infor MyDay installation, be sure that the servers and clients are set up as described

here.

Database serverWe recommend that you use a dedicated database server for the databases associated with Infor MyDay(Infor BIS database, Infor On-Ramp database, Infor CSI database, and so on). In most cases, this should

be separate from the database server used by the applications such as ERP that feed into MyDay, so thatthe performance of those applications is not impacted.

The database server must have Microsoft SQL Server 2005 installed. SQL Server should be installed withMixed Mode authentication, which allows both Windows authentication and SQL Server authentication.

The database server must be running a minimum of either Windows 2003 Server Enterprise Edition, or

Windows 2003 64-bit Standard Edition.

The user who will install MyDay must have Administrator rights on this server.

The hardware specifications for the database server depend on the volume of transactions in the ERPsystem.

Enabling remote connections on SQL Server

In order to perform the installation and run scripts against the SQL Server from a remote computer, youmust enable remote connections on each instance of SQL Server. To do this, follow these steps on thedatabase server:

1 From the Windows Start menu, select Programs > Microsoft SQL Server 2005 > ConfigurationTools > SQL Server Surface Area Configuration.

2 On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration forServices and Connections.

3 On the Surface Area Configuration for Services and Connections page, expand Database Engine

and click Remote Connections. Select Local and remote connections and select the appropriateprotocol to enable for your environment. Then click Apply.

Click OK when you receive the following message:

Changes to Connection Settings will not take effect until you restart the Database Engine service.

4 On the Surface Area Configuration for Services and Connections page, expand DatabaseEngine and click Service. Click Stop, wait until the MSSQLSERVER service stops, and then click

Start to restart the MSSQLSERVER service.



System requirements | 9


Application serverWe recommend that you use a dedicated application server, separate from the database server(s), on

which you will install and run these components as described in this guide:

Infor Security

Infor Dynamic Enterprise Management (DEM)

Infor Deployment, Configuration, and Administration (DCA)

Infor On-Ramp

Infor Common Services Infrastructure (CSI)

Infor Metadata

Infor Financials Currency

Infor Financials Calendar

Infor Business Information Systems (BIS)

Infor Public Master Data Management (MDM)

Infor Proxy Master Data Management (MDM)

Infor Reporting

Infor MyDay

The user who will install MyDay must have Administrator rights on this server.

The application server must meet these requirements:

1 Ensure that the server has at least:

− 6 GB of RAM available for these applications.

− 2 processors (preferably dual core).

− 30 GB of hard disk space.

2 Ensure that the application server is running a minimum of either Windows 2003 Server EnterpriseEdition, or Windows 2003 64-bit Standard Edition.

3 If the server is also to be used as a client (see page 11), then ensure that a browser is available withthe options listed in the “Client” section.

4 Install Java Development Kit 1.5.x. When you install Java Development Kit (JDK), select CustomSetup and change the Installation Location. Verify the following:

− For installation on a 64-bit server, make sure that you install a 64-bit version of JDK 1.5.x





− Make sure that you install JDK, not a Java Runtime Environment (JRE).

− Do not install JDK in any folder whose name contains spaces.

− Note the installation folder name, since you will refer to it later.

− Under Browser Registration, make sure Microsoft Internet Explorer and Mozilla Firefox is

selected.

Tip: To download JDK from the Sun Microsystems Java Web site (http:// java.sun.com), go to thedownloads section and look for Java SE, previous editions, Java2SE 5.0 downloads. Download JDK5.0. (JDK 1.5 and 5.0 are the same thing.) Ensure that, if you are using a 64-bit computer, youdownload the 64-bit version.

5 Set environment variables for the application server. To do this, go to the System Properties dialog’sAdvanced pane and click Environment Variables.

a Create a new system variable called JAVA_HOME that points to the Java Development Kitinstallation folder.

b Edit the Path system variable to include a pointer to [JDK_install_folder] \bin.

c Make sure there is not an environment variable named CATALINA_HOME.



System requirements | 11


6 Validate the installation of JDK by running the batch programs listed in the commands window.

ClientA client is any computer that accesses Infor MyDay or the other Infor Open SOA components through a

browser. Thus, if you access the component applications through a browser on the application server, theserver is also considered a client. Clients must meet the following requirements:

Clients should use either the Windows XP Professional or the Windows Vista Business Edition

operating system. (Clients installed on a server can use Windows 2003 Server.)

For the browser on the client, use Mozilla Firefox version 3.x or Internet Explorer 7.x. The followingoptions must be set up in the browser:

−

SSL

− Cookies

− JavaScript

Java must be installed on every computer where the Infor Reporting report designer is installed (seepage 53). To verify that Java is set up correctly, you can use a Java test. For an example test page,see the Test your jvm information on the Java Web site (http//java.com).

NOTE: This test page tells you that you are using an older version of JRE. However, you must not

update your Java version, since at this time we support only JDK 1.5.





Infor MyDay port requirementsBy default, the ports listed here are used by MyDay and should not be used by another application. After

installation is complete, you can change the port numbers if necessary.

If the application server is running behind a firewall, your firewall software must be configured to allowaccess to the ports listed here.

Port Used by

389 LDAP

1433 (SQL)

1521 (Oracle)

MyDay databases

1616 JMX Console (monitors On-Ramp)

8010 HTTP for DEM/DCA

8015 AJP Connector port for DEM/DCA

8019 Apache Shutdown port for DEM/DCA

8030 HTTP for PublicMDM, ProxyMDM, Currency and Calendar

8035 AJP Connector port for PublicMDM, ProxyMDM, Currency and Calendar

8039 Apache Shutdown port for PublicMDM, ProxyMDM, Currency and Calendar

8050 HTTP for BIS

8055 AJP Connector port for BIS

8059 Apache Shutdown port for BIS

8070 HTTP for CSI and Security

8075 AJP Connector port for CSI and Security

8079 Apache Shutdown port for CSI and Security

8088 CSI monitoring of processing queues on Infor On-Ramp

8090 HTTP for MyDay Administration and Reporting

8095 AJP Connector port for MyDay Administration and Reporting

8099 Apache Shutdown port for MyDay Admin and Reporting

8413 SSL for DEM/DCA

8433 SSL for PublicMDM, ProxyMDM, Currency and Calendar

8453 SSL for BIS

8473 SSL for CSI and Security

8493 SSL for MyDay Admin and Reporting

61617 ESB server



Preparing for the installation | 13


Preparing for the installation

Before starting the installation, set up the following files, users, and databases.

1 If you have not checked in the last few days, access Infor365 for the latest version of this Infor MyDay Installation Guide and your appropriate ERP/FMS integration guide. These documents contain thelatest updates.

2 Copy the MyDay folder from the installation DVD into the local disk of the application server. Thiscreates a local folder named MyDay (for example, C:\MyDay for a Windows installation or /opt/myday

for a Linux installation). In the rest of this document, this folder is referred to as [MyDayPackage].Under the MyDay folder, you should see two subfolders:

− Installer contains a file called Installer.zip that includes all files used during the installationprocess.

− Content contains all database and reports content that is loaded into the applications at the end

of the installation process.

Note: Do not delete this folder after the installation, because it contains all the necessary

configuration and structure and can be used to install future version upgrades and software patches.

3 Extract the contents of the Installer.zip file into the [MyDayPackage]\Installer folder.

4 On the database server, in SQL Server Management Studio, create a database user named

inforuser. (Optionally, you can edit the database script

[MyDayPackage]\Installer\etc\CreateUsers.sql to change the default password in it. Then run thescript to create this user.) For this user account, the following should be set up:

− “sa” privileges

− Enforce Password Policy should not be selected

− The password for this user should observe the restrictions set up in “Appendix B: Password

restrictions.”

5 On the database server, create the following databases. (Optionally, you can use the database script

[MyDayPackage]\Installer\etc\CreateRBHPDatabases.sql to create these databases.)

−

InforBISConfig

− InforBISData

− InforBISDataConsumer

− InforCSI

− InforCSIAudit



14 | Preparing for the installation


− InforCurrency

− InforDCA

− InforDEM

− InforESBIOBox

− InforFinancialCalendar

− InforIR

− InforMetadata

− InforProxyMDM

− InforPublicMDM

− InforRBHP

− InforSecurityMDM

6 Run the script [MyDayPackage]\Installer\etc\SetIsolations.sql against the master database on the

database server. Make sure there are no connections to databases whose names begin with “Infor…”when you run this script.

7 On the application server, edit the following properties in the file

[MyDayPackage]\Installer\master.properties where [MyDayPackage] is the root drive and folder containing the files used in the MyDay installation:

Property Description Example

installer.path Location of MyDay installer

package

C:/MyDay/Installer(see note below)

installation.path Location where MyDay will be

installed. This folder should already

be created. In the rest of this

document, this folder is referred to

as [MyDayHome].

C:/Infor(see note below)

server.1.name Complete hostname [appserver].infor.com

ldap.1.server.password Password for the user "manager"

which is used to sign into Infor

Security to import user privileges

and create all other users

any password that follows

“Appendix B: Password

restrictions“

database.1.server.name Name of the database server, if

different than the application server

[dbserver].infor.com

database.1.server.port The port on the database server

configured to listen for connections

1433

database.1.server.user.id Name of the database user inforuser

database.1.server.user.password Password for the “inforuser” user [password]






database.1.admin.id Name of the database

administrator

inforuser

database.1.admin.password Password for the “inforuser” user [password]

components Comma-separated list of

component names to install

See table below

containers List of tomcat containers to be

installed

1,2,3,4,5

os.64bit Property should be set to true if the

server used for the installation is a

64-bit computer AND a 64-bit JDK

is installed. Any value other than

true is treated as false.

os.64bit = false

Notes:

When setting the path properties above, use a forward slash (/) instead of a back slash (\). Using aback slash causes the installation process to fail.

Ensure that there are no forward slashes at the end of the installer.path or installation.path properties.

To verify whether the application server is a 64-bit computer:

a On the server console, select Start > Run and enter dxdiag.

b If a prompt displays, asking if you want to verify your drivers, click No.

c When the program finishes, if this is a 64-bit computer, the Operating System line will look similar

to this: Windows [version] x64 or 64-bit edition.

d Click Exit.

Installation of specific applicationsYou can install individual applications from those delivered as part of the MyDay Installer package, rather

than installing the complete MyDay framework. If you do this, use the following table to determine whichcomponents, containers and databases are co-dependent and must be installed at the same time.

The columns represent MyDay applications: front-end applications to which users can sign in, and back-

end applications that handle activities between the application server and the database. The rows represent MyDay components (in orange), containers (in green), and databases (in blue). Eachapplication column contains at least one row with an X to indicate that the component, container, or

database in that row is required for the application. Multiple Xs in a column indicate that multiple objectsmust be installed together for the application. Rows marked N/A indicate that the application does not

require any of the objects in that group. For example, Infor On-Ramp does not require any container(because it runs in its own OSGi container), and Infor Security does not require any database.

Note the following about the components, containers, and databases listed here:





Entries in the Component Name group (orange) must be listed, separated by commas, in the

components property line of the [MyDayPackage]\ Installer\master.properties file.

The configuration described below is the standard MyDay configuration. Some ERP systems may

require additional or different components, databases, or containers. See the ERP’s IntegrationGuide for details.

Entries in the Container group (green) must be listed, separated by commas, in the container property line of the [MyDayPackage]\Installer\master.propertiesfile. These are the tomcat

containers that must be running in order for the application (in the column marked with an X) to run.

Entries in the Database group (blue) are databases that must be created prior to the installation. Thedatabases are associated with the applications in the columns marked with an X.

M y D a y

B I S

R B H P

D E M / D C A

S e c u r i t y

C S I

P u b l i c M D M

P r o x y M D M

I n f o r O n - R a m p

I n f o r R e p o r t i n g

C u r r e n c y

F i n a n c i a l C a l e n d a r s

Component Name

Currency X X

FinancialCalendars X X

InforBISConfig X X

InforBISConfigServer X X

InforBISData X X

InforBISDataConsumer X X

InforBISDataServer X X

InforCalendarServer X X

InforCAS X X

InforCSIX X

InforCSI_Audit X X

InforCSI_Server X X

InforCurrencyServer X X

InforDCA X X





M y D a y

B I S

R B H P

D E M / D C A

S e c u r i t y

C S I

P u b l i c M D M

P r o x y M D M



C u r r e n c y

F i n a n c i a l C a

l e n d a r s

InforDCA_Server X X

InforDEM X X

InforDEM_Server X X

InforESB X X

InforLDAP X X

InforMetadata X X

InforPublicMDM X X

InforPublicMDMServer X X

InforProxyMDM X X

InforRBHP X X

InforRBHP_Server X X

InforReporting X X

InforSecurity X X

InforSecurityMDM X X

Container Number

1 X X X N/A

2 X X X N/A

3 X X X N/A X X

4 X X N/A X

5 X X N/A

Database

InforBISConfig X X N/A

InforBISData X X N/A

InforBISDataConsumer X X N/A





M y D a y

B I S

R B H P

D E M / D C A

S e c u r i t y

C S I

P u b l i c M D M

P r o x y M D M



C u r r e n c y

F i n a n c i a l C a

l e n d a r s

InforCSI X N/A X

InforCSIAudit X N/A X

InforCurrency X N/A X

InforDCA X X N/A

InforDEM X X N/A

InforESBIOBox X N/A X

InforFinancialCalendar X N/A X

InforIR X N/A X

InforMetaData X X N/A

InforProxyMDM X N/A X

InforPublicMDM X N/A X

InforRBHP X X N/A

InforSecurityMDM X X



Customizing component installation (optional) | 19


Customizing component installation (optional)

The MyDay installation package contains the appropriate and recommended configuration for the various

components in the MyDay framework, their database names, users, passwords and tomcat containers.

It is unlikely that you will need to modify this configuration; however, if it is necessary, this sectiondescribes the steps involved. If you are not modifying the configuration, skip to the next section.

Each component has its own folder under the [MyDayPackage]\Installer\Componentsfolder structure.The folder name matches the component name listed in the master.properties file (see page 14).

Changing component propertiesEach component folder under [MyDayPackage]\Installer\Components contains a

[componentname].properties file. This file sets the property values relevant to that application. If youchange the properties in one of these files, the installer uses the properties from the component

properties file instead of the ones specified in the master.properties file.

The most common properties that require changes are listed in the following table. These properties refer

to database connections.



20 | Customizing component installation (optional)



database.base The database defined in the

master.properties file where thedatabase for the component will be

installed

database.1

database.base.server.scheme The database schema name used by

the current component

InforRBHP

database.base.server.user.id The user name that the component

uses to connect to the database

rbhpuser

database.base.server.user.password The user password to connect to the

database

[rbhpuser password]

database.ods.server.user.id

(see note below)

The user name that is used to connect

to the InforBISData database.

bisuser

database.ods.server.user.password(see note below) The user password to connect to theInforBISData database. [bisuser password]

Note: Because the following components each require database connections, you may add these

properties (if they do not exist) or remove the # comment notation from the beginning of the line (if theproperty is commented out) so they can be used by the installer. The database.ods.server.user.idand

database.ods.server.user.passwordproperties are required by only four of these components, asdescribed below:

InforBISConfigServer – also requires database.ods.server.user.id and

database.ods.server.user.password properties

InforBISDataConsumer – also requires database.ods.server.user.id anddatabase.ods.server.user.password properties

InforBISDataServer

InforCalendarServer

InforCSI_Audit

InforCSI_Server

InforCurrencyServer

InforDCA_Server

InforDEM_Server

InforESB

InforMetadata

InforProxyMDM

InforPublicMDMServer



Customizing component installation (optional) | 21


InforRBHP_Server – also requires database.ods.server.user.id anddatabase.ods.server.user.password properties

InforReporting – also requires database.ods.server.user.id and database.ods.server.user.password

properties

InforSecurityMDM

Changing component database usersBy default, MyDay uses a single database user (inforuser) to connect to all databases used by thevarious components. If necessary, you can define individual database user accounts for each component.

If you do this, you must edit the property files for each component to modify the

database.base.server.user.id and database.base.server.user.passwordproperties as described

above. (Optionally, you can edit the database script

[MyDayPackage]\Installer\etc\CreateUsersAdvancedOptions.sql to change the default password foreach database user, and then run the script to create these individual users.)

Database username

Tracks use of this service

bisuser Infor BIS application

calendaruser Infor Calendar

csiuser Infor CSI application

currencyuser Infor Currency

dcauser Infor DCA

demuser Infor DEM

humanuser Logins

iruser Infor Reporting application

marsuser Infor On-Ramp

metadatauser Infor Metadata

proxymdmuser Infor Proxy MDM application

publicmdmuser Infor Public MDM application

rbhpuser Infor MyDay application

securityuser Infor Security MDM application



22 | Installing MyDay


Installing MyDay

1 From a command prompt on the application server, navigate to the [MyDayPackage]\Installer folder

and run the install.bat batch file.

After the installation begins, the control for the command prompt is suspended and returns when theinstallation completes. The batch file installs all of the components required to use MyDay.

2 When the command prompt returns, review the [MyDayPackage]\Installer\logs\install.log file andsearch for any errors. If the installation was successful, the message BUILD SUCCESSFUL appears

at the end of the file.

3 During the installation, the installer creates a keystore file in the [MyDayHome] folder. This file is

unique for each system and is used to establish secure connections between the server and theclients. Back up this file to a safe location outside the installation directory, so it can be restored ifneeded.

4 From the command prompt, run the [MyDayPackage]\Installer\patch.bat file to apply all availablepatches that are included with the release. For instructions on how to apply additional patches that

may become available, see “Appendix C: Applying patches.”

5 When the command prompt returns, review the [MyDayPackage]\Installer\logs\patch.log file and

search for any errors. If the installation was successful, the message BUILD SUCCESSFUL appearsat the end of the file

6 Configure the system as described in the rest of this guide. If you encounter errors during any step,

consult the troubleshooting information in the guide associated with the component (Infor Security,Infor DEM, and so on) where you are currently working.



Clearing PublicMDM information | 23


Clearing PublicMDM information

In SQL Server Management Studio, run the script [MyDayPackage]\Installer\etc\clearPublicMDM.sql against the following databases:

InforCurrency

InforFinancialCalendar



24 | Importing security permissions


Importing security permissions

1 Start these Windows services in the following order:

− InforSecurity LDAP

− Infor Tomcat1

− Infor Tomcat5

2 If necessary, you can set the startup mode of these Windows Services to "Manual" instead of“Automatic.” If this installation has been made on a server, keep the startup mode as "Automatic.”

3 Sign in to the Infor Security application using the URL shown in “Appendix A: Accessing Inforapplications,” with the user ID manager and the password that you defined in the master.properties

file. (See ldap.1.server.password in the table on page 14.)

Note: During the first access to each application/port, the browser displays a warning message that a

secure connection failed. To correct this, add an exception. If you need assistance, consult thebrowser’s online help.

To avoid receiving these error messages, you must obtain a certificate signed by an authority such as

Verisign, and then update all clients to add Infor’s default certificate as a trusted certificate.

4 Import the security permissions file into the Infor Security application:

a Click SECURITY.

b From the menu, select Advanced > Tools.

c In the Import section, browse to [MyDayPackage]\Installer\etc\MyDayFullExport.xml.

d Click Import. A message confirms the successful import of the security permissions file.

5 Do not sign out of Infor Security, since it is used again for the next task.



Creating security hierarchies – accounting entities | 25


Creating security hierarchies – accounting entities

In Infor Security, define an accounting entity to use for the ERP. An accounting entity is a corporation or a

subset of a corporation that is independent in regard to one or more operational or accounting functions.This entity produces a profit and loss and balance sheet from a complete, balanced set of transactions. It

is often, but not always, a legal entity. An accounting entity is defined within a tenant and can containlocations.

To define an accounting entity through the Infor Security application:

1 Click SECURITY.

2 Click Security Hierarchies.

3 Click the Detail icon next to Accounting Entities.

4 Click Add Node

5 Specify a value for the new accounting entity in the Code field.

6 Click Submit.



26 | Creating administrative users for MyDay


Creating administrative users for MyDay

You must create administrative users for the MyDay components as shown in the table below. This table

lists the applications to which a user could have access, the responsibilities a user could have in thatapplication in a specific role, and the roles that must be assigned to the user account in Infor Security.

Application Responsibility Role Assignment

MyDay Admin MyDay Administrator InformationTechnology.DataAdmin (primary)

BIS BIS Administrator InformationTechnology.DataAdmin (primary)

PublicMDM PublicMDM Administrator InformationTechnology.DataAdmin (primary)

CSI CSI User InformationTechnology.SystemsAdmin (primary)

Reporting Reporting Administrator InformationTechnology.DataAdmin (primary)

DCA Business Analyst InformationTechnology.DataAdmin (primary)

InformationTechnology.SystemsAdmin

DEM Business Process Analyst InformationTechnology.BusinessProcessAdmin

(primary)

Note: The Financial Calendars and Currency applications do not require users to have any special roles;

therefore, any of the users created above automatically have access to the Financial Calendars andCurrency applications.

To create users through the Infor Security application:

1 Click Users.

2 Click New (in the upper right corner) and fill in the information for the new user, including the detailsand password. User passwords should observe the restrictions specified in “Appendix B: Password

restrictions.”

3 In the Security Hierarchies tab, click the Details icon next to Roles. Then use the arrow buttons toassign the appropriate roles to the user and click Submit. You can also assign locations and

accounting entities to the user.

4 If this user requires access to CSI, in the Security Hierarchies tab click the Details icon next to

Accounting Entities. Assign all the entities defined in the previous section that will be used by theERP. Doing so allows this user to audit messages generated by the ERP.

5 Click Submit to save the new user.

For more information about creating users, roles, and passwords, see the Infor MyDay System Administration Guide . To export and back up the information you just entered, see “Appendix G:

Exporting security users and permissions.”



Configuring file permissions for Infor On-Ramp | 27


Configuring file permissions for Infor On-Ramp

Set the permissions for the following files so that they are readable and writable only by the owner of the

file. The owner of these files must be either the user who starts Infor On-Ramp (for example, Administrator) or the group to which the user who starts Infor On-Ramp belongs (for example,

Administrators). There must be only one entry.

[MyDayHome]\esb\configuration\jmx.password

[MyDayHome]\esb\configuration\jmx.access

For detailed instructions on setting these permissions, see the information about How to Secure aPassword file on Microsoft Windows on Sun Microsystems’s Java Web site (http://java.sun.com).



28 | Restoring database contents


Restoring database contents

Overview

After a new installation, the databases do not yet contain the configuration that is required to make the

MyDay application fully operational. Infor provides this configuration in the form of database backups.Restoring the database content from the backups completes the configuration so that the application

includes metrics and reports, as well as the import and export services that retrieve data and render it intothe metrics and reports.

NOTE: This section applies only to new installations. If you have previously restored content databases

and have run the script processTenantCodes.sql, use the steps in “Appendix F: Upgrading MyDay

content” to upgrade your existing installation with new content, instead of this section.

Contact Infor for the latest content databases. Do not use the content databases distributed with thesoftware located in the [MyDayPackage]\Content folder. The steps in this section assume you have an

up-to-date version of the content databases. The content backups consist of 4 database backups and aset of SQL scripts.

The database backups are:

InforBISConfig

InforBISData

InforIR

InforRBHP

The SQL scripts, which are used in later steps of the installation, are:

processTenantCode.sql

counterMyDay.sql

processedMessageCounter.sql

deleteFromInforOnRamp.sql

deleteFromProxyMDM.sql

Steps

1 Stop the following Windows services (note that Tomcat2, 3, and 4 may not be running at this point):

− Infor Tomcat1

− Infor Tomcat2



Restoring database contents | 29


− Infor Tomcat3

− Infor Tomcat4

− Infor Tomcat5

2 To load the contents from the backup files, perform these steps on the database server:

a Restore the database InforBISConfig with the downloaded backup file InforBISConfig.bak.

b Restore the database InforBISData with the downloaded backup file InforBISData.bak .

c Restore the database InforIR with the downloaded backup file InforIR.bak.

d Restore the database InforRBHP with the downloaded backup file InforRBHP.bak.

When restoring these content backups, always select Overwrite the existing database on the Options

page of the Restore Database task screen in Microsoft SQL Server Management Studio.



30 | Modifying BIS data inbox properties


Modifying BIS data inbox properties

During initial processing, you must temporarily change the inbox.threads property. You will restore it

later.

1 Open the file fortress.properties located in

[MyDayHome]\tomcat2\webapps\com.infor.bis.data.server\WEB-INF.

2 Find the inbox.threads property and record its current value on paper or in another file, so it can berestored later.

3 Change the inbox.threads value to 1 and save the file.



Processing Public MDM tenant codes | 31


Processing Public MDM tenant codes

To load the standard Public MDM codes:

1 Start the Windows service Infor Tomcat3.

2 On the database server, in SQL Server Management Studio, run the tenant creation script

processTenantCode.sql against the InforPublicMDM database. This script is included in the ZIP file

that contains the content database backups.

3 Run this command in SQL Server Management Studio to determine whether the process hasfinished:

SELECT * FROM [InforPublicMDM].[dbo].[PUB_STANDARD_DATA_CREATION];

If the result contains a row where the value for column C_SUCCEEDED is set to '1', then the processcompleted successfully and all necessary codes were created in Public MDM.

If the result contains a row where the value for column C_SUCCEEDED is set to '0', then the processfinished, but an error occurred. Contact Infor Support for information about a recovery procedure.

If you see the error message

Invalid object name ‘InforPublicMDM.dbo.PUB_STANDARD_DATA_CREATION’ then you have not applied all available patches. You can finish this process and apply the patches

later; however, you must use a different method to determine whether the process has finished. Runthe script counterMyDay.sql , which is included in the content ZIP file. Wait for the number of codes

reported for PublicMDM to stop changing. t the beginning of the process, the number of codesremains at 0 for a while, but later it increases. This should take at least 45 minutes. After you think

the processing is complete, wait an additional 5 minutes to ensure that the number does not changeagain.

4 Stop the Windows service Infor Tomcat3.



32 | Starting MyDay routing applications


Starting MyDay routing applications

Start these services to start the routing:

Infor Tomcat1

Infor Tomcat5



Starting Infor On-Ramp | 33


Starting Infor On-Ramp

Starting Infor On-Ramp in detached modeTo start Infor On-Ramp as a Windows service, use the Windows Service manager to start the

infor.container.1 service.

Starting Infor On-Ramp in interactive mode (optional)If you do not run Infor On-Ramp as a Windows service, start the Infor On-Ramp in interactive mode.

For computers running Windows:

1 To go to the Infor On-Ramp installation folder, enter cd [MyDayHome]\esb from a command prompt.

2 Enter esb to start the Infor On-Ramp.

For computers running UNIX or Linux:

1 To go to the Infor On-Ramp installation folder enter cd [MyDayHome]/esb.

2 Enter esb to start the Infor On-Ramp.

LogsInfor On-Ramp log files are stored in the folder [MyDayHome]/esb/logs .



34 | Creating and deploying a routing definition


Creating and deploying a routing definition

The following steps create a configuration on Infor On-Ramp that allows it to mediate message

exchanges between the different components that were installed with MyDay.

Importing the enterprise templateTo import the template:

1 Sign into the DCA application using the URL shown in “Appendix A: Accessing Infor applications.”Use the user ID and password you defined for the DCA business analyst in “Creating administrative

users for MyDay” on page 26.

2 Click Deployment Configuration.

3 Click Templates and then Enterprises in the left pane. This displays the ENTERPRISETEMPLATES page.

4 Click Import. (This button is at the top right corner of the page.)

5 Browse for the Enterprise Template that has been provided for the integration between the ERPsystem and the MyDay components. Although a sample enterprise template file has been bundled in

the [MyDayPackage]\Installer\etc\EnterpriseTemplate.xml file, we highly recommend that youcontact Infor and request the most up-to-date version to use in your installation.

6 Click Import and wait for confirmation that the import process completed successfully.

Building and deploying the enterprise componentsTo build and deploy the components:

1 Click Deployment Configuration.

2 Expand Deployment Builder in the left pane.

Creating server instance(s)

Create a server instance for the application server where the MyDay components are installed. To create

the server instance:

1 Under Deployment Builder in the left pane, click Servers.

2 Click New (This button is at the top right corner of the page).



Creating and deploying a routing definition | 35


3 Specify this required information:

Field Expected Value/Example

Notes

Server Template windows:2003 Template for Windows 2003 Server

ID myday_server Name of the server where On-Ramp is installed

4 Click Submit to save the changes.

5 On the Properties tab, click Modify addresses.

6 Click on the existing entry for localhost to select it, and click on Delete to remove it.

7 Click New.

8 Specify this required information:


Notes

value [appserver].infor.com Host name or IP address of the server where On-

Ramp is installed

9 Click OK to save the address information.

10 Click Submit to save the server information.

Creating MyDay database resource instance(s)If all MyDay components use the same database server, only one MyDay database resource is required.

If the components run on different database servers, which is a rare occurrence, you must define oneresource for each MyDay database server.

To define the MyDay database resource instance:

1 Click Resources in the left pane.

2 Click New.

3 In the Template field, select MSSQL or the appropriate database type where the resource has been

created.

4 In the ID field, specify myday. (If you must create multiple MyDay resource instances, each IDshould be unique, for example myday_1, myday_2, and so on.)

5 Click Submit.





6 Specify this required information on the PROPERTIES tab:


Notes

hostname [dbserver].infor.com Hostname used in the URL to connect to the MyDay

database

port portnumber Port used in the URL to connect to the MyDay

database

schemaname dbname

(see note below)

Schema name. Default is dbname

username inforuser

(see note below)

User name for the resource instance. Default is an

empty string

password [inforuser password]

(see note below)

Password for the resource instance. Default is an

empty string

Notes:

− If you use the default values as shown in this table, then during the Component Instance creation,DCA will insert the standard values provided by the enterprise template. For example, if you leave

the schemaname set to dbname, then when creating the CSI component instance, DCAautomatically inserts InforCSI in the Schema Name field. The default values used by DCA can be

overwritten at the container or component level.

− Resources can be reused in containers and components when they reuse the same hostname

and port. When this is not the case, you must create additional resources.

− Later, you will be asked to specify a database username and password for a container instance.

Since you have specified the username and password here, you can leave these fields blank on

the container instance, and DEM uses the values you entered here in the database resourceinstance as defaults.

7 Click Submit again to save the resource properties.

Creating an ERP database resource instance

Define a database resource instance for your ERP database server. To define the ERP resource

instance:


2 Click New.

3 In the Template field, select MSSQL or the appropriate database type where the resource has been

created.

4 In the ID field, specify the ERP name.

5 Click Submit.







Notes

hostname [dbserver].infor.com Hostname used in the URL to connect to the ERP

database

port [portnumber] Port used in the URL to connect to the ERP database

schemaname [dbname] ERP database name

username [user name] SQL user name used to access the ERP database

password [password] Password used to access the ERP database

7 Click Submit again to save the resource properties.

Creating a broker resource instance

For the MyDay deployment, one broker resource is required. To define a broker instance:


2 Click New.

3 In the Template field, select Broker.

4 In the ID field, specify broker.

5 Click Submit.

6 Leave the default broker property values in the Properties tab unchanged.

Note: You can overwrite the port number at each container level. This allows broker resources to be

reused across containers.

7 Click Submit again to save the resource properties

Creating a container instance

To create a container instance:

1 Click Containers in the left pane.

2 Click New.

3 Specify the following required information:

Field Expected Value Notes

Template OSGi Name of the template.






ID 1 Container ID. This ID must match the ESB (On-Ramp)

container ID used during the installation. The installer

uses the default value infor.container.1. DCA

automatically fills out the first two nodes of the name

(infor.container), so enter only 1 here.

Installed On

Server

server.windows.[appserver] Name of the server configured earlier in this section

Error

Component

infor.csi.local Component that will handle error logging on the container.

Note: No components have been created yet. After

completing the next section, you will update the container

with this information (see page 42).

4 Click Submit to save the container information.



database infor.resource.myday MARS database resource created in the previous section

schemaname InforESBIOBox Database schema name for On-Ramp

username inforuser Database user name for On-Ramp

password [password] Password for the inforuser database account

broker Infor.resource.broker Broker resource created in the previous section

port 61617 Port provided by default

Note: The schemaname for Infor On-Ramp is provided by default. Do not modify it unless the

database is configured differently. If the username and password fields are left blank, the valuesentered on the database resource (infor.resource.myday) are used by default in DEM during the

deployment (see “Creating a routing and activating the solution” on page 44).

The other fields on this tab are used for tuning the performance of message processing by Infor On-Ramp. Make changes to the default values listed here only after performing an overall analysis of the

installation and hardware.

Field Defaultvalue

Description

mars.localrouter.maxConcurrentConsumers 50 The maximum number of threads that canbe created to route messages to the

component’s inboxes.

mars.localrouter.concurrentConsumers 20 The minimum number of threads that can

be created to route messages to the

component’s inboxes.

6 Click Submit.





Creating MyDay component instances

For the MyDay deployment a predetermined number of components are also required. To create the

container instances:

1 Click Components in the left pane.

2 For each component, perform these steps:

Note: The CSI component must be created first, since it will be specified as the Error Component formost of the other components.

a Click New.

b In the Deployed in Container field, select the container (infor.container.1) created in the

previous section.

c Select the appropriate template for the component being created.

d In the ID field, DCA automatically supplies the first two nodes of the name (for example, infor.csi)

based on the selected template, so you specify only the last local node, local. This name must belowercase.

e In the Error Component field, select infor.csi.local from the combo box for all the new

components that you define, except CSI and CSI-Audit, which have a blank error component.

f Click Submit to save the component information.

g In the Properties tab, specify the database resource and corresponding properties for eachcomponent:

Template databaseresource(see notes)

schemaname username password

CSI infor.resource.myday

InforCSI inforuser

(see notes) [password]

(see notes)

BIS-Config infor.resource.myday

InforBISConfig inforuser [password]

BIS-Data infor.resource.myday

InforBISData inforuser [password]

BIS-DataConsumer infor.resource.

myday

InforBISDataCons

umer

inforuser [password]

Currency infor.resource.myday

InforCurrency inforuser [password]

Financial Calendar Infor.resource.myday

InforFinancialCale

ndar

inforuser [password]

ProxyMDM infor.resource.myday

InforProxyMDM inforuser [password]





Template databaseresource(see notes)


PublicMDM infor.resource.myday

InforPublicMDM inforuser [password]

Reporting infor.resource.myday

InforIR inforuser [password]

RoleBasedHomePages infor.resource.myday

InforRBHP inforuser [password]

CSI-Audit infor.resource.myday

InforCSIAudit inforuser [password]

Notes: The value for schemaname is provided by default in the Enterprise Template. If you leavethe username and password blank here, the username and password values that were entered

during creation of the MyDay database resource (see page 35) will be used automatically during

deployment.

If more than one MyDay database resource was defined because MyDay component databasesare on different servers, specify the appropriate resource in the database resource field.

h On the Properties tab for each component, the property poller.deleteProcessedMessages

indicates whether the messages to (Inbox) and from (Outbox) the selected component should be

deleted from the database after they are processed by the Infor On-Ramp. The default value is

false, meaning that messages will not be deleted. Not deleting the messages after processing is

helpful when debugging message routing; however, be aware that the “false” setting will increasethe size of the inbox and outbox tables on the database considerably over time. This canpotentially impact performance. To prevent performance issues, Infor On-Ramp automatically

deletes all messages that were processed more than 36 hours ago.

The other fields on this tab are used to tune the performance of message processing by Infor On-Ramp. Make changes to the default values listed here only after performing an overall analysis of

the installation and hardware.

Field DefaultValue

Description

listener.concurrentConsumers 5 * The minimum number of threads that can be

created to consume messages delivered by

Infor On-Ramp and place them in the

component’s inbox for processing.

* Although this default value is best for most

components, it may vary for components

that must process a larger number ofmessages.





Field DefaultValue

Description

listener.maxConcurrentConsumers 15 * The maximum number of threads that can

be created to consume messages deliveredby Infor On-Ramp and place them on the

component’s inbox for processing

* Although this default value is best for most

components, it may vary for components

that must process a larger number of

messages.

poller.rowsLimit 20 The number of messages that the polling

daemons can retrieve from the component’s

outbox at one time and can make available

for routing to Infor On-Ramp

pollingDaemon.maxPoolSize 10 The maximum number of threads that can

be created to retrieve messages from the

component’s outbox and make themavailable for routing to Infor On-Ramp

pollingDaemon.minPoolSize 10 The minimum number of threads that can be

created to retrieve messages from the

component’s outbox and make them

available for routing to Infor On-Ramp

pollingDaemon.sleepTime 5000 The interval, in milliseconds, at which the

polling daemons check the component’s

outbox for more messages after all

messages have been delivered for routing

i Click Submit to save the properties.

3 For the CSIAudit component only, you must also enable it to audit other components:

a Click Edit.

b Click the Audits tab.

c Click New. A new row is added. Select a component from the table above. Repeat this step untilall the components in the table, except the CSI and CSIAudit components, are added.

NOTE: Auditing is helpful for debugging and for performing message tracking. However, please

consider the performance trade-off. When auditing is enabled, the volume of messages handledby On-Ramp is at least double its normal amount. Thus, unless you have concerns or specialneeds, we recommend that you do not enable auditing during this installation process. Later, if

necessary, you can enable auditing of messages going into specific components only bymodifying the CSIAudit component and then sending an updated deployment to Infor On-Ramp.

We also strongly recommend that you do not enable auditing during initial data loads, when thevolume of messages is likely to be higher than the day-to-day transactions that the system will

handle later.

d Click Submit to save this information.

4 Review the details for all the components and approve them.





5 When you finish, verify the status of all the components in the list – they should all be Approved. Ifnot, go back and approve them.

Assigning the error component to a container

Now that you have defined an error component, you can assign it to the container:

1 Click Containers in the left pane.

2 Click the Details icon next to infor.container.1 in the list of containers.

3 Click Edit.

4 Select infor.csi.local as the error component.

5 Click Submit.

Creating the ERP component instance

To create the container instance for the ERP component:

1 Click Components in the left pane.

2 Perform these steps:

a Click New.

b In the Deployed in Container field, select the container (infor.container.1) created earlier.

c In the Template field, select the appropriate template for the ERP.

d In the ID field, DCA automatically supplies the first two nodes of the name (for example,

infor.syteline) based on the selected template, so you specify only the last local node.

Note: This name must be lowercase, and the full ID (all three nodes) must match the logical ID

configured for the ERP system. This value must also match the fortress.id value of the ERP,which in most cases is found in the fortress.properties file of the ERP installation. Make sure you

enter the appropriate value; otherwise you will have problems during the routing and delivery ofmessages.

e In the Error Component field, select infor.csi.local from the combo box.

f Click Submit to save the component information.

g In the Properties tab, specify the database resource and corresponding properties:





Template database resource(see note)


[ERP] infor.resource.[ERP] [ERP database

name]

[user name to

access ERPdatabase]

[password to

access ERPdatabase]

Note: In the database resource field, specify the ERP database resource that you defined earlier.

h On the Properties tab, the property poller.deleteProcessedMessages indicates whether the

messages to (Inbox) and from (Outbox) the ERP should be deleted from the database after theyare processed by the Infor On-Ramp. The default value is false, meaning that messages will not

be deleted. Not deleting the messages after processing is helpful when debugging messagerouting; however, be aware that the “false” setting will increase the size of the inbox and outbox

tables on the database considerably over time. This can potentially impact performance. Toprevent performance issues, Infor On-Ramp automatically deletes all messages that were

processed more than 36 hours ago.

i Click Submit to save the properties.

j Return to the CSIAudit component and edit it to add the ERP component to its list of audited

components:

• Click Edit.

• Click the Audits tab.

• Click New. A new row is added. Select the ERP component you added above.

NOTE: Auditing is helpful for debugging and for performing message tracking. However,please consider the performance trade-off. When auditing is enabled, the volume of

messages handled by On-Ramp is at least double its normal amount. Thus, unless you haveconcerns or special needs, we recommend that you do not enable auditing during this

installation process. Later, if necessary, you can enable auditing of messages going intospecific components only by modifying the CSIAudit component and then sending anupdated deployment to Infor On-Ramp. We also strongly recommend that you do not enable

auditing during initial data loads, when the volume of messages is likely to be higher than theday-to-day transactions that the system will handle later.

• Click Submit to save this information.

3 Review the component’s details and approve the component.





Approving server instances

The server instances created in the previous sections are created with a Draft status. Before you can

include them in a deployment for activation, you must approve them.

To approve the servers you created:

1 Click Servers in the left pane.

2 Click the Details icon next to server.windows.[appserver] in the list of servers. On the SERVER page,click Approve (in the upper right corner).

3 Verify the status of the servers in the list – they should all be Approved.

Executing deployment

Note: Make sure that the Infor On-Ramp service (infor.container.1) is running before performing thesesteps.

To deploy all the components to the On-Ramp:

1 Click Deployments.

2 In the list of deployments, click the Details icon next to the <<DRAFT>> deployment.

3 On the DEPLOYMENT <<Draft>> page, click Deploy (in the upper right corner).

4 In the dialog that displays, specify the Name and Description of the deployment and click OK.

5 Sign out of the DCA application.

Creating a routing and activating the solution1 Sign into the DEM application, using the URL shown in “Appendix A: Accessing Infor applications.”

Use the user ID and password you defined for the DEM business process analyst in “Creatingadministrative users for MyDay” on page 26.

2 Click Dynamic Enterprise Management.

3 Expand Business Routing in the left pane.





Creating a routing

To create a routing:

1 Click Routings in the left pane.

2 Click New.

3 On the ROUTING (NEW) page:

a Select the Routing Template to use (for example, MyDay SyteLine Routing Template ).

b Specify a Name for the routing (for example, MyDay SyteLine Routing ).

c Click Submit. The lower pane displays all the routes that were included as part of the new

routing.

d Click Approve (in the upper right corner).

Activating the solution

Note: Before following these steps, make sure the Infor On-Ramp service (infor.container.1) is running.

Activating the solution sends the routing defined in the previous section to the On-Ramp:

1 Click Solutions in the left pane.

2 In the list of solutions, click the Details icon next to <DRAFT>.

3 On the SOLUTION <<Draft>> page, click Activate (in the upper right corner).

4 In the dialog that displays, specify the Name and Description of the deployment and click OK.

5 Sign out of the DEM application.





Restarting Infor On-RampTo load the new configuration, you must restart Infor On-Ramp.

If you started Infor On-Ramp in interactive mode, use these steps to stop and start the service on either

Windows or Linux:

1 From the Infor On-Ramp console window, enter the command close.

Some log messages and confirmations display. When the On-Ramp stops, the default command

prompt returns, pointing to the [MyDayHome]\esb folder.

2 With the command prompt still pointing to [MyDayHome]\esb folder, enter esb to restart On-Ramp.

If you started Infor On-Ramp as a service, restart it on the Windows Service Manager application.



Starting MyDay applications | 47


Starting MyDay applications

To start the MyDay applications:

1 Restart the Infor On-Ramp. To restart Infor On-Ramp in interactive mode, use a command prompt to

go to the Infor On-Ramp folder [MyDayHome]\esb and then enter esb. To restart Infor On-Ramp asa service, start it from the Windows Service Manager application.

2 Start the Windows services:

− Infor Tomcat1

− Infor Tomcat2

− Infor Tomcat3

− Infor Tomcat4

Do not start the Infor Tomcat5 Windows service

Note: Under the current MyDay configuration, the service Infor Tomcat5 is only used by the DEM andDCA applications. To preserve CPU and memory resources, we recommend that you keep it stopped.

Start it only if changes are made on the resources or routing definitions, as described in “Creating anddeploying a routing definition” on page 34. To prevent this service from starting automatically wheneverthe applications server is restarted, its Startup Type should be set to Manual in the Windows Services

Manager.



48 | Synchronizing Public MDM tenant codes


Synchronizing Public MDM tenant codes

The MyDay applications are now synchronizing the tenant codes created in “Processing Public MDM

tenant codes“ on page 31.

That initialization process takes a long time to run. To see if it has finished, run

processedMessageCounter.sql,which is included in the ZIP file that contains the content databasebackups, from SQL Server Management Studio. Continue running this script occasionally and check the

results. When the number of unprocessed messages is zero for each component, the script is complete;otherwise the system is still processing messages.

Wait for this synchronization to complete before continuing with the next step.



Restoring BIS data inbox properties | 49


Restoring BIS data inbox properties

After the tenant code processing is complete, restore the BIS data inbox properties:

1 Open the file fortress.properties located in


2 Find the inbox.threads property and change the value back to its original value, as recorded in

“Modifying BIS data inbox properties” on page 30.

3 Save the fortress.properties file.

4 Restart the Tomcat2 service to reload this setting.



50 | Verifying codes and codelist synchronization


Verifying codes and codelist synchronization

After the On-Ramp is configured and all components are running, you can verify that the standard

codelists and codes created in PublicMDM are correctly sent to all other components.

To verify this:

1 In SQL Server Management Studio, run this script, which is included in the content ZIP file:

processedMessageCounter.sql

This script automatically connects to and runs against the appropriate databases.

For each component, the number of unprocessed messages should be zero, as shown in the

following example. Otherwise, the system is still processing messages.

Inbox of Component Number of unprocessedmessages

PublicMDM 0

Currency 0

Calendar 0

BISConfig 0

BISData 0

IR 0

InforRBHP 0

Outbox of Component Number of unprocessedmessages

PublicMDM 0

Currency 0

Calendar 0

BISConfig 0

BISData 0

IR 0

InforRBHP 0

2 After all messages are processed, run this script (also included in the content ZIP file) in SQL Server

Management Studio: counterMyDay.sql

The number of codes, dimensions, and hierarchies and codelists in each component should match

the number in PublicMDM, as shown in the following example. Currently, some components, such as



Verifying codes and codelist synchronization | 51


InforCurrency, might have more codelists and codes than PublicMDM; however, this is a temporarysituation. The numbers in the example below (2385 and 110) are for illustration only and may change

depending on the version of the database contents that is imported.

Component Number ofcodes

Number ofdimensions

Number ofhierarchies

PublicMDM 2385 110 110

Currency 2385 110 110

Calendar 2385 110 110

BISConfig 2385 110 110

BISData 2385 110 110

IR 2385 110 110

InforRBHP 2385 110 110



52 | Specifying an accounting entity in PublicMDM


Specifying an accounting entity in PublicMDM

You must set up an accounting entity for the ERP in PublicMDM, which then provides the accounting

entity to all components including the ERP.

To specify the accounting entity in PublicMDM:

1 Sign into the PublicMDM application using the URL shown in “Appendix A: Accessing Infor

applications.” Use the user ID and password you defined for the PublicMDM administrator in“Creating administrative users for MyDay” on page 26.

2 Click CONFIGURATION.

3 Click Codes in the left pane.

4 Double-click Accounting Entities in the list.

5 Click New.

6 Specify information to define the accounting entity. This code name should match the accounting

entity you specified in Infor Security on page 25.

7 Click Submit.



Installing reports | 53


Installing reports

Installing the Infor Reporting report designerThe Infor Reporting report designer should be installed only on the computers of users who will authorreports. Users who simply want to view reports do not need the report designer; however, they must run a

supported Web browser as specified in the Client section of “System Requirements” on page 11.

The report designer installation requests connection information for several applications. This informationis used to configure the default connection settings for the report designer. Refer to the port informationon page 12 when answering the prompts. You can update the connection settings after installation.

To install the Infor Reporting report designer:

1 Run IRDesignerInstaller.exe, found in the [MyDayPackage]\Installer\etc folder.

2 Click Next.

3 In the Choose Install Folder dialog, to accept the default location (C:\Program Files\Infor Reporting)click Next. Or enter a new location and click Next.

Note: Java must be installed on the computer where you install the report designer.

4 In the Single Sign On dialog, enter the server location and SSL port of the Infor Security application

and click Next. The server location is the computer name where MyDay is installed. The default SSLport number for the Infor Security application is 8473.

5 In the LDAP Configuration dialog, enter the server location and SSL port of the Infor LDAP serverand click Next. For more information about LDAP, see the Infor MyDay System Administration Guide .

6 In the IR Services Location dialog, enter the server location and port number of the Infor Reporting

application. If you used the default values during MyDay installation, specify these values:

Field Value Notes

Host MyDay application

server name

Name of the application server where MyDay is

installed

Port 8090 HTTP port number of the Apache tomcat instancewhere the Infor Reporting application was installed

IR Services User

Name

[username] Name of the user that you created for the Infor

Reporting application, belonging to the DataAdmin

role, during “Creating administrative users for

MyDay” on page 26

IR Services

Password

[password] Password for the database user

7 Click Next.



54 | Installing reports


8 Click Install.

9 When installation is complete, click Done.

Configuring the auditing feature for Infor ReportingBecause the InforIR database that was restored in “Restoring database contents” on page 28 containsreferences to the database where it was created, you must update the references to point to the newdatabase server.

1 Select Start > All Programs > Infor > IR Designer. The report designer opens.

2 If the IR Report Manager pane is not visible, open it: select Window > Show View > Other> InforReporting > IR Report Manager and click OK.

3 In the IR Report Manager, right-click the Report Store and select Connect.

4 In the IR Report Manager, expand the Libraries folder and double-click Infor Reporting AuditStyles to open the library.

5 Select Window > Show View > Outline.

6 In the Outline view, expand the Data Sources node and double-click Audit Data Source to edit it.

7 Change the data source definition to contain the correct connection information to the IR database:

Field Value Notes

Driver URL jdbc:jtds:sqlserver://[database_server]:[database_port]/InforIR [database_server] and [database_port] iinthe URL refer to the database server and

port number of the InforIR database

schema

User Name [Infor Reporting database user name] Name of the database account (usually

inforuser) that was created in “Preparing

for the installation” on page 13

Password [password] Password for the Infor Reporting database

user

8 Click Test Connection to verify that the connection can be established with the new information.

9 Click OK to close the dialog box.

10 If the IR Report Manager pane is not visible, open it: select Window > Show View > Other> InforReporting > IR Report Manager.

11 Right-click the Infor Reporting Audit Styles library node and click Save.

12 Right-click Infor Reporting Audit Styles again and click Unlock.



Installing reports | 55


Importing MyDay reports (optional)The InforIR database that was restored in “Restoring database contents” on page 28 already contains the

MyDay reports. The following steps are needed only if new versions of reports become available and youmust override the reports currently in the database.

1 Select Start > All Programs > Infor > IR Designer. The Report Designer opens.

2 If the IR Report Manager pane is not visible, open it: select Window > Show View > Other. Thenselect Infor Reporting > IR Report Manager and click OK.

3 In the IR Report Manager pane, right-click the Report Store and select Connect.

4 Due to a known issue, existing content cannot be overwritten. Delete the library titled Infor MyDayStyles.

5 Right-click Report Store and select Import from Package.

6 In the Infor Reporting report designer, browse to the [MyDayPackage]\Content folder.

7 Select the Reports.zip file and click Open.

Refer to the Infor Reporting documentation for information about creating reports.



56 | Configuring the system for drillbacks


Configuring the system for drillbacks

1 Sign into the Infor MyDay Administration application using the URL shown in “Appendix A: Accessing

Infor applications.” Use the user ID and password you defined for the MyDay administrator in“Creating administrative users for MyDay” on page 26.

2 Click DEPLOYMENTS.

3 Click New and add a row for the ERP application. Refer to the MyDay Implementation Guide for yourERP system to find the correct values to use with your application.

Field Description Example

Name application name SyteLine

Logical ID Prefix infor.[appname] infor.syteline

Logical ID lid://infor.[appname].[instance]

This value must match the ID

defined in “Creating the ERP

component instance” on page 42

lid://infor.syteline.oh

Host Name or IP Address ERP host server name or IP address slutil1

Port Number ERP port 8080

Secured Indicates whether the drillback to the

ERP system is secured (SSL based)or unsecured

No

4 Click Submit.



Creating business users for MyDay | 57


Creating business users for MyDay

You must define business users for MyDay through the Infor Security application. These users are

assigned to roles such as Purchase Manager, Sales Manager, and so on.

To define business users:

1 Sign in to the Infor Security application using the URL shown in “Appendix A: Accessing Infor

applications,” with the user ID manager and the password that you defined in the master.propertiesfile.

2 Click SECURITY.

3 Click Users.

4 Click New (in the upper right corner) and fill in the information for the new user, including the Detailsand Password tabs. When defining passwords, see the list of acceptable characters specified in

“Appendix B: Password restrictions.”

5 In the Security Hierarchies tab, click the Details icon next to Roles. Then use the arrow buttons toassign the appropriate roles to the user and click Submit. You can also assign locations andaccounting entities to the user.

Note: MyDay users assigned to business roles (for example, Purchase Manager, Sales Manager,

and so on) must be associated with the appropriate accounting entity defined for the ERP, in additionto being assigned to the proper roles.

6 Click Submit to save the new user.

For more information about creating users, roles, and passwords, see the Infor MyDay System Administration Guide . To export and back up the information you just entered, see “Appendix G:

Exporting security users and permissions.”



58 | Verifying the installation


Verifying the installation

After the installation is complete, sign into MyDay and set up a user. Then sign in as that user and launch

several metrics and reports to verify that the installation worked and data is flowing through the system.Be sure that the metrics and reports you select are supported for your back-end ERP system.

If the data is not flowing all the way through the system, there are several places you can look forproblems. Use the Infor Common Services Infrastructure (CSI) application to find failures related to BOD

structure. For instance, if a message has an invalid format, or is missing a mandatory field, CSI willdescribe the problem. Use the Audited Messages > History function to view successful message

transmissions, and Errors > History functions to find failed message transmissions. For moreinformation, see the CSI documentation.

To find other problems, you may need to look at the log files for the individual MyDay components, whichare located in the logs folder of the tomcat container where each component is deployed.



Appendix A: Accessing Infor applications | 59


Appendix A: Accessing Infor applications

Listed below are the HTTP URLs to use when accessing the Infor applications you just installed. Replace

the [hostname] part of the URL with the complete computer name of the server where the applications areinstalled. These URLs are case-sensitive.

Use the user ID and password you defined for each application in “Creating administrative users forMyDay” on page 26.

Infor Application URL

Infor Business Information Services Configuration http://[hostname]:8050/BISConfig

Infor Business Information Services Data http://[hostname]:8050/BISData

Infor Business Information Services Data Consumer http://[hostname]:8050/BISDataConsumer

Infor Common Services Infrastructure (CSI) http://[hostname]:8070/csi

Infor Currency Master Data Management http://[hostname]:8030/Currency

Infor DCA http://[hostname]:8010/dca

Infor DEM http://[hostname]:8010/dem

Infor Financial Calendars Master Data Management http://[hostname]:8030/FinancialCalendars

Infor MyDay Administration http://[hostname]:8090/homePageAdmin

Infor Public Master Data Management http://[hostname]:8030/InforPublicMDM

Infor Security Administration http://[hostname]:8070/Security



60 | Appendix B: Password restrictions


Appendix B: Password restrictions

When defining database user or application user passwords, in addition to letters (both uppercase and

lowercase) and numbers, the following special characters are acceptable:

Character description Character ampersand &

asterisk * at symbol @

caret ^ close parenthesis ) colon : comma , equals sign = exclamation point ! greater than symbol >

left bracket [ less than symbol <

open parenthesis ( percent % period . pipe | plus sign + question mark ? right bracket ] semicolon ; tilde ~ underscore _



Appendix C: Applying patches | 61


Appendix C: Applying patches

When a patch is provided for any MyDay component, perform the following steps to apply it:

1 Review the README file provided for the patch before beginning the installation process. The

installation process is not always the same for every patch, and any differences are described in theREADME file. It is also important to understand the prerequisites and impact of the change beingmade.

2 Stop all tomcat services that are currently running, and stop the Infor On-Ramp (infor.container.1).

3 Copy the provided patch zip file into the [MyDayPackage]\Installer\patches folder.

4 From a command prompt on the application server, navigate to the [MyDayPackage]\Installer folderand run the patch.bat batch file.

Running this file applies the patch and moves the zip file into the

[MyDayPackage]\Installer\Components\[Component]\patches folder, where [Component] is thename of the component for which the patch was applied.

5 When the command prompt returns, review the [MyDayPackage]\Installer\logs\patch.log file andsearch for any errors. If the patch is applied successfully, the message BUILD SUCCESSFUL

appears at the end of the file.

6 Restart all tomcat services. Then restart the Infor On-Ramp service (infor.container.1).



62 | Appendix D: Uninstalling MyDay


Appendix D: Uninstalling MyDay

To uninstall MyDay components:

1 Stop these Windows services:

− InforTomcat5

− InforTomcat4

− InforTomcat3

− InforTomcat2

− InforTomcat1


− Infor.container.1

2 Run the batch script [MyDayPackage]\Installer\uninstall.bat.

Note: Like the install process, the uninstall process uses the values set on the components andcontainers properties of the master.properties file to determine which components to uninstall. If youleave the default values, all containers and components are uninstalled. For details on how to

uninstall specific components or containers, refer to the table in “Installation of specific applications”starting on page 15.

3 The uninstaller will not drop or modify the existing databases. If necessary, to drop the databaseschemas related to Infor MyDay, run the sql script [MyDayPackage]\etc\DropRBHPDatabases.sql as a system administrator.



Appendix E: Upgrading MyDay | 63


Appendix E: Upgrading MyDay

Overview

This section provides the steps to upgrade the application side of MyDay (tomcat services, containers,

web components, LDAP and Infor On-Ramp). No changes are made to the currently loaded data contentand data configuration. This process can be done independently from the process described in “Appendix

F: Upgrading MyDay content.”

Steps

To upgrade from a previous version of MyDay, use these steps:

1 Sign in to the Infor Security application using the URL shown in “Appendix A: Accessing Inforapplications,” with the user ID manager and the password that you defined in the master.properties

file. (See ldap.1.server.password in the table on page 14.)

2 Export the security permissions file into the Infor Security application:

a Click SECURITY.


c In the Export section, leave the value on the Data to Export field set to All, and click Export.

d When prompted, click Save and select a location to save the file fullExport.xml.

Save the exported file to a safe location outside the MyDay home folder [MyDayHome] or the

installer folder [MyDayPackage].

3 Stop all InforTomcat services, the InforSecurity LDAP service, and the On-Ramp service(infor.container.1).

4 Run the batch script [MyDayPackage]\installer\uninstall.bat.

Note: Like the install process, the uninstall process uses the values set on the components andcontainers properties of the master.properties file to determine which components to uninstall. During

the upgrade you must uninstall all components and containers, so make sure the original values

provided in the file are still listed. Refer to the table in “Installation of specific applications” starting onpage 15 for the list of components and containers.

The uninstaller does not drop or modify the existing databases. During an upgrade this is not

necessary, so do not run any of the database scripts used in the installation steps.

5 Run the batch script [MyDayPackage]\etc\removeservices.bat.



64 | Appendix E: Upgrading MyDay


6 Delete or rename the current [MyDayPackage] created in Step 2 of “Preparing for the installation” onpage 13. Replace it with the installation package provided for the new release.

7 Edit the master.properties file provided in the new [MyDayPackage] as described on page 14. Make

sure you use the properties file provided for this new release; do not copy or reuse the one from theold installation.

8 Run the script [MyDayPackage]\Installer\etc\UpdateSchemaVersions.sql against the master database on the database server.

9 From a command prompt on the application server, navigate to the [MyDayPackage]\Installer folder

and run the install.bat batch file.

After the installation begins, the control for the command prompt is suspended and returns when theinstallation completes. The batch file installs all of the components required to use MyDay.

10 When the command prompt returns, review the [MyDayPackage]\Installer\logs\install.log file andsearch for any errors. If the installation was successful, the message BUILD SUCCESSFUL appears

at the end of the file.

11 Install any patches:

a Check the [MyDayPackage]\Installer\Patchesdirectory to see if there are any patches includedin the release. If no patches are available, skip to Step 12.

b From the command prompt, run the [MyDayPackage]\Installer\patch.bat file to apply all patches

that are included with the release.

c When the command prompt returns, review the [MyDayPackage]\Installer\logs\patch.log fileand search for any errors. If the installation was successful, the message BUILD SUCCESSFUL

appears at the end of the file.

12 Start the following Windows services:


− Infor Tomcat1

13 Sign in to the Infor Security application again and import the users/permissions file that was

exported in Step 2:

a Click SECURITY.


c In the Import section, browse to the file exported in Step 2.

d Click Import. A message confirms the successful import of the security permissions file.

14 Set the file permissions for Infor On-Ramp, as described on page 27.

15 Start the remaining Windows services:



Appendix E: Upgrading MyDay | 65


− Infor Tomcat2

− Infor Tomcat3

− Infor Tomcat4

− Infor Tomcat5

16 Start Infor On-Ramp either in detached mode or in interactive mode, as described on page 27.

17 Sign into DCA and deploy the configuration that was created during the original installation process – see “Executing deployment“ on page 44.

18 Sign into DEM and activate the solution that was created during the original installation process – see

“Activating the solution“ on page 45.

19 In the Windows service manager, restart the Infor On-Ramp service (infor.container.1). The broker

then loads the components and routings.



66 | Appendix F: Upgrading MyDay content


Appendix F: Upgrading MyDay content

Overview

This section provides the steps to upgrade the MyDay content used by some of the MyDay components.

The data being upgraded in these steps deals with the configuration of the import and export servicesresponsible for retrieving data and rendering it in metrics and reports that are made available to the user

through the MyDay Admin pages.

Before starting this process, all available patches must be applied to the system. For further details, see“Appendix C: Applying patches.” Also review the Readme.doc file included with the downloaded contentupdate for additional information and requirements associated with this upgrade process.

This process can be done independently from the process described in “Appendix E: Upgrading MyDay.”

Recording information for later reconfiguration

Record the following information that will be used for manual configuration after you restore the content

databases:

Any Import Services that are marked as “Disabled”

Any personalized (non-default) settings configured in the MyDay pages

The deployment configuration for the drillbacks

Restoring the content databases

1 Download the ZIP file from the Infor365 Patch Download area and extract the database backup files

and associated SQL scripts.

2 Stop the Infor On-Ramp. If you started Infor On-Ramp in interactive mode, enter the command close in the Infor On-Ramp console window. If you started Infor On-Ramp as a service, stop it from the

Windows Service Manager application.

3 Stop all of the following Windows services that may be running at this time:

− Infor Tomcat1

− Infor Tomcat2

− Infor Tomcat3

− Infor Tomcat4



Appendix F: Upgrading MyDay content | 67


− Infor Tomcat5

4 To load the contents from the backup files, perform these steps on the database server:

a Restore the database InforBISConfig with the downloaded backup file InforBISConfig.bak.

b Restore the database InforBISData with the downloaded backup file InforBISData.bak .

c Restore the database InforIR with the downloaded backup file InforIR.bak.

d Restore the database InforRBHP with the downloaded backup file InforRBHP.bak.

When restoring these content backups, always select Overwrite the existing database on the Options

page of the Restore Database task screen in Microsoft SQL Server Management Studio.

Synchronizing the databases

After restoring the databases you must synchronize them with your existing InforPublicMDM database.

1 In SQL Server Management Studio, run [MyDayPackage]\etc\clearPublicMDM.sqlagainst both theInforCurrency and InforFinancialCalendardatabases. This clears out the data that the PublicMDM

component sent to these databases during data synchronization.

2 Open the 6 embassy.properties files (located in the folders listed below) and temporarily set the

publicmdm.embassy.fortressInitializer.autoStart property to 'true'. Save each file after making the

change.

− [MyDayHome]\tomcat2\webapps\com.infor.bis.config.server\WEB-INF

− [MyDayHome]\tomcat2\webapps\com.infor.bis.data.server\WEB-INF

− [MyDayHome]\tomcat3\webapps\com.infor.financials.calendar.server\WEB-INF

− [MyDayHome]\tomcat3\webapps\com.infor.financials.currency.server\WEB-INF

− [MyDayHome]\tomcat4\webapps\IRServices\WEB-INF

− [MyDayHome]\tomcat4\webapps\analytics.server\WEB-INF

3 During initial processing, you must temporarily change the inbox.threads property. You will restore it

later.

a Open the file fortress.properties located in


b Find the inbox.threads property and record its current value on paper or in another file, so it can

be restored later.

c Change the inbox.threads value to 1 and save the file.

4 Restart Infor On-Ramp. To restart Infor On-Ramp in interactive mode, use a command prompt to go

to the Infor On-Ramp folder [MyDayHome]\esb and then enter esb. To restart Infor On-Ramp as aservice, start it from the Windows Service Manager application.



68 | Appendix F: Upgrading MyDay content


5 Start the Windows services:

− Infor Tomcat1

− Infor Tomcat2

− Infor Tomcat3

− Infor Tomcat4

Do not start the Infor Tomcat5 Windows service. (Under the current MyDay configuration, the service

Infor Tomcat5 is only used by the DEM and DCA applications.)

6 After the services restart, messages begin flowing through the system. Wait for all messages tocomplete. To see if this has finished, run processedMessageCounter.sql (included in the content

ZIP file) from SQL Server Management Studio. Continue running this script occasionally and checkthe results. This script automatically connects to and runs against the appropriate databases.

For each component, the number of unprocessed messages should stop changing but will not bezero. Also, the number of unprocessed messages should be the same across all 6 components. If

the numbers are still changing or are not the same across the 6 components then the system is stillprocessing messages and you must wait. When it appears that no more messages are changing,

wait a few more minutes to be sure it is done. (Sometimes it can take a minute for a single messageto be processed.) After waiting a few minutes, check one more time and verify that none of the

numbers have changed.

All messages must be complete before continuing, or the databases will not be synchronizedproperly.

7 When no more messages are flowing, restart the following Windows services again. This starts a

new set of messages flowing through the system.

− Infor Tomcat2

− Infor Tomcat3

− Infor Tomcat4

8 To check if these new messages are complete, run processedMessageCounter.sql (included in thecontent ZIP file) from SQL Server Management Studio. Continue running this script occasionally and

check the results. When the number of unprocessed messages is zero for each component, the scriptis complete; otherwise the system is still processing messages.

9 In SQL Server Management Studio, run counterMyDay.sql (included in the content .ZIP file) andverify that each of the components has the same number of codes, dimensions and hierarchies.

10 Open the embassy.properties files (located in the folders listed below) and reset the

publicmdm.embassy.fortressInitializer.autoStart property to 'false'. Save each file after youchange it. (This step prevents unnecessary messages from flowing through the system.)

− [MyDayHome]\tomcat2\webapps\com.infor.bis.config.server\WEB-INF



Appendix F: Upgrading MyDay content | 69


− [MyDayHome]\tomcat2\webapps\com.infor.bis.data.server\WEB-INF

− [MyDayHome]\tomcat3\webapps\com.infor.financials.calendar.server\WEB-INF

− [MyDayHome]\tomcat3\webapps\com.infor.financials.currency.server\WEB-INF

− [MyDayHome]\tomcat4\webapps\IRServices\WEB-INF

− [MyDayHome]\tomcat4\webapps\analytics.server\WEB-INF

11 Restore the BIS data inbox properties:

a Open the file fortress.properties located in


b Find the inbox.threads property and change the value back to its original value, as recorded

earlier in these steps.

c Save the fortress.properties file.

12 Restart the Tomcat1, Tomcat2, Tomcat3, and Tomcat4 services.

Post-restoration tasks

Using the information you saved earlier, perform these configuration tasks:

1 Reset to 'Disabled' any Import Services you turned off.

2 Redefine the settings for your metrics.

3 Re-establish the deployment configuration for the drillbacks.



70 | Appendix G: Exporting security users and permissions

Appendix G: Exporting security users and

permissions

Use these steps to back up the users and permissions created in the Infor Security component. If theusers and permissions are backed up, they can be restored later, during a system recovery or during

replication of data to other environments within the same customer installation.

1 Ensure that these Windows services are running:


− Infor Tomcat1

2 Sign in to the Infor Security application using the URL shown in “Appendix A: Accessing Infor

applications,” with the user ID manager and the password that you defined in the master.propertiesfile. (See ldap.1.server.password in the table on page 14.)

3 Export the security permissions and users file from the Infor Security application:

a Click SECURITY.


c Click Export. A popup window prompts for the location where the file should be saved.

4 Copy the exported file to a safe location so it can be imported when necessary.

Note: Unless you are instructed otherwise by Infor, do not import this file across installations using

different versions of MyDay.

Date post:	03-Apr-2018
Category:	Documents
Upload:	koosengelbrecht
View:	216 times
Download:	0 times

Infor MyDayInstallationGuide 1 1 1

Documents