If you are using the Crystal Web Service then the layouts needs to be manually copied to a location where the Crystal Web Service is installed. This is for Web Client and IFS EE and Aurena. So you can have the rpt layouts is a relevant location you wish. One such place is the manual installation folder.

Have a look at the following links for more information on how to install / configure and troubleshoot Crystal Web Service issues.

F1 Documentation:

https://docs.ifs.com/techdocs/Foundation1/020_installation/400_installation_options/005_operational_reporting/110_configure_crystal_web_service/default.htm

Videos:

https://wit.ifsworld.com/technology/recordings/content/CR_Installation.mp4

https://wit.ifsworld.com/technology/recordings/content/CR%20Prerequisites.mp4

https://wit.ifsworld.com/technology/recordings/content/CR_Troubleshooting.mp4

*Admin note: Replaced wit links with doc links. (April 2020)

@ChanakaAmarasekara :
Thanks, I know what I must do while install.
I hoped there is some standard practice to achieve right folder structure and avoid forgot manually copying of layouts.
For example Delivery Builder could automaticaly copy all *rpt from <module>\server\layout to ManuallInstallation folder.

Agreed. But from a framework work perspective the layouts are crated by the customer and is harvested in customer harvest. So there is not hard and fast rule where to have the layouts.

We have plans to remove this inconvenience of manual copying. In that case a specific place would be defined. Yet, this is in design/discussion stage still.