Zheng Tech Blog

According to the Oracle document , WebCenter Spaces provides out-of-the-box translations for 27 languages and 100 different locales. These 27 languages are available after the WebCenter installation and no additional developments/configurations are needed. There are two ways to see the translated WebCenter Space. One is via the provided language changer UI on the Space page header. The other is via the browser locale setting. For the WebCenter framework application, the 27 languages are also available for those build-in services and features.Since the framework application doesn't have the out-of-the-box language changer UI but you can always set your preferred locale in your client browser. For example, here is a snapshot of the admin page of a WebCenter framework application displaying in English language. Now I change my preferred browser display language to Spanish (ES). Refresh the portal page and I can get it displaying in Spanish. Again I chang

I recently came across a scenario to consume the JSP file from WebCenter. It's not a usual scenario but it could be an option in the customer's environment. The customer has some JSP files stored in file system and consumed by some other Portal platform other than WebCenter. The JSP files contain conditional check in the scriptlet to display output dynamically. Now WebCenter is going to replace the old platform and options are discussed to how to consume the JSP files on the files systems. One option, of course, is to convert the JSP files into content files stored in the WebCenter Content server. This will need some additional work on the content server side to prepare the JSP file counterpart. If the logic in the JSP scriplet can be handled by content server side, then it could be an easier job. If not, multiple content files will be needed for one JSP file conversion. Let's look at the second option, which is to consume the JSP file directly from the file systems li