4 Administrative Tasks
This chapter contains the following topics:
4.1 Language Support
Currently, the following languages are supported in One View Reporting:
- Arabic
- Chinese Simplified
- Chinese Traditional
- Czech
- Danish
- Dutch
- Finnish
- French - France
- German
- Greek
- Hungarian
- Italian
- Japanese
- Korean
- Polish
- Portuguese - Brazil
- Spanish
- Swedish
- Turkish
- Russian
JD Edwards EnterpriseOne users using the above languages need to set the JD Edwards EnterpriseOne user profile to indicate the appropriate language. At runtime, the system passes the user's language preference to BI Publisher to run the report in the user's language.
The user should also set the UI language for BI Layout Editor to the language of his choice. To set the language in BI Publisher Layout Editor, click on the User Name, then click "My Account". There are two settings related to language in the BI Publisher Layout Editor:
- Report Locale
- This is the language with which you run BI Publisher reports. You can leave this field blank and JD Edwards EnterpriseOne will pass the proper report locale using the JD Edwards EnterpriseOne user's language setting.
- UI Language
- This is the language of the menus and descriptions within the BI Publisher Layout Editor. You can change this to the appropriate language of your choice.
All of the delivered JD Edwards EnterpriseOne One View reports contain translations of the previously mentioned languages.
4.2 Troubleshooting
This section discusses some issues you might encounter and possible resolutions.
4.2.1 One View Menu Does Not Appear In Applications
If you cannot see the One View menu in the P01012 or other applications, make sure that:
- Your JD Edwards EnterpriseOne user mapping is set up correctly in P0092. It is case-sensitive.
- You can log into the BI Publisher server using the user ID and password.
- Your BI Publisher account has the BIAuthor role.
- The softcoding record is set up for the correct environment and user combination in P954000.
- Feature authorization for your user account and the form you are trying to access is set up correctly in P958974.
4.2.2 When Clicking On the One View Menu Icon, Nothing Happens
If nothing happens when you click on the One View menu icon, make sure that you clear your browser file cache.
4.2.3 One View Menu Loading But No Reports Appear
If you click on the One View menu icon, and see the word ”Loading” but no reports appear, and you are using a version of Server Manager prior to 9.1.0.2, you must add a new One View JVM Setting for WebLogic 11g or WebSphere 7.
To add a new One View JVM Setting for WebLogic 11g:
- Log on to the WebLogic Admin console.
- Open Environment in the Domain Structure, and then select Servers.
- Select the Server Start tab.
- Add this JVM setting to the Arguments:
-Djavax.xml.rpc.ServiceFactory=oracle.j2ee.ws.client.ServiceFactoryImpl
To add a new One View JVM Setting for WebSphere 7:
- Log on to the WebSphere Application Server Admin console as jde_user.
- Go to Servers, Server Types, WebSphere Application Servers, AS_JS_88, Java and Process Management, Process Definition, and then Java Virtual Machine.
- Add the following to the Generic JVM setting field and save:
-Djavax.xml.rpc.ServiceFactory=oracle.j2ee.ws.client.ServiceFactoryImpl -Djavax.xml.soap.SOAPConnectionFactory=oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnectionFactory
Note:
If you are using Server Manager 9.1.0.2 or a later version to install the JAS instance, this setting is added automatically.4.2.4 Errors when Saving Reports
If you receive an error when you try to save a report, try the following:
- Make sure that your BI Publisher user and password mappings are setup correct in your user profile.
- Try restarting the BI Publisher server to fix the issue.
- If you see an invalid user and password error message in the HTML server error log, it indicates the user and password in the user profile do not match the BI Publisher server.
- Make sure that the JVM settings are configured correctly. See the One View Menu Loading But No Reports Appear section.
4.2.5 Errors in BIP Layout Editor on All Reports
If you receive a red error or ”pdf not found” error while trying to render the One View Reports in BIP Layout Editor, make sure that:
- Your machine is inside of the company firewall using a cable network. If you are using a wireless network, it may be outside of the company fire wall.
- The BI Publisher server and HTML server are within the same firewall. If not, contact your IT Department to make sure that network security allows the BI Publisher server and HTML server to ping each other.
- If BI Publisher and the HTML server are in different domains, you are using the full address (IP address of full name with domain) to access the HTML server.
4.2.6 Failed to Save Report Error and Problem Running Shared Report
If you receive the error message ”Failed to Save the Report” when attempting to save the Data Model for a report that you are creating, or if you are trying to run a shared report and all you see is a Processing popup message for a second and then nothing happens, you may have a problem with the JD Edwards EnterpriseOne connection to the BI Publisher server. After creating the BI Publisher users in BI Publisher, you must restart the BI Publisher server before trying to connect from JD Edwards EnterpriseOne.
4.2.7 Missing Boilerplates in Components Folder in BI Publisher
If you installed Oracle Business Intelligence Enterprise Edition (OBIEE) and BI Publisher on the same server, you might not see the Boilerplates functionality in the Components folder under the Shared Folders.
In order to reload the boilerplates feature:
- Sign onto the BI Publisher server (http://host:port/xmlpserver).
- Select Administration, System Maintenance, Server Configuration as shown:
- On the Catalog form, click the ”Upload to BI Presentation Catalog” button.A confirmation message appears in the upper right corner of the Administration page.
- Click Apply to save the configuration.
- Once the upload is completed, you see the Components enabled in the Shared Folders.Note:Since this is an integrated BI Publisher in OBIEE, you cannot edit the permissions from BI Publisher; you need to edit security through OBIEE.
- To edit permissions, sign into OBIEE (http://host:port/analytics).
- Select ”More” to open the drop-down menu, and then select Permissions.
- Review and edit the permissions accordingly.
4.3 Performance Considerations
The performance of each report depends on the number of rows each report retrieves, the amount of logic each report processes, and the number of graphical and tabular components on the report.
To improve the performance of a report:
- Limit the number of rows each report retrieves.
- Look at the number of event rules for each grid row that are being fetched on the One View Report applications.
- Look at the graphical and tabular components in the report. Sometimes a pivot table with a large number of columns may take a long time to render. In this case, reduce the number of columns in the pivot table.
In general, it is a good idea to reduce the number of fields selected in the data model. This will speed up the report generation and rendering.
One View Reporting is an interactive solution that is not designed to retrieve tens of thousands of database records. If you need to work with a large amount of data, using either the Read Only JDBC driver or a UBE report will provide better performance.
4.4 Scalability Considerations
When you run a One View report, the HTML server retrieves the report data. The data is then passed to the BI Publisher server for report rendering and generation. This means that running a One View report adds more load to the HTML server and the back end database. The additional load is similar to adding
No comments:
Post a Comment