![2013 ms word bi publisher add in 2013 ms word bi publisher add in](https://technology.amis.nl/wp-content/uploads/images/BIPub_WordAddinMenu.jpg)
2013 ms word bi publisher add in windows#
So in Windows server you must specify the drive letter like "C:\fonts\CustomArial.ttf". Truetype path: should be an absolute path. Weight: specify "normal" or "bold" for the font weight. Style: specify "normal" or "italic" for the font style. This name should match the name which appears as font name when viewing the rtf template in MS word.
![2013 ms word bi publisher add in 2013 ms word bi publisher add in](https://www.oracleport.com/wp-content/uploads/2020/09/BIPublisher2.png)
The family attribute is case-insensitive. If you specify "Default" for this attribute, you can define a default fallback font. Under the section these are the available values:įont family: specify any family name for the font. Please note that the location is different for AS400 platforms as mentioned above. Both default location and other custom font locations should have the same permission as the E1 delivered fonts location which is \system\resource\truetype.Īny OS-level user IDs that E1 utilizes (e.g., for Windows/UNIX/Linux: the user ID used to start E1 services, for AS/400: ONEWORLD, JDE, and any other separate OS-level proxy IDs used to run UBEs) should have at least "Read Permissions" on the fonts folder where the fonts are located.Īlso, check that the following fonts exist on the Enterprise Server \system\JRE\\lib\fonts directory. This default font location can be overridden by defining the new location in xdo.cfg file as explained in the below. On V7R1, there is only the new “J9 JVM” available.Į1's default JVM location for 8.98.3.0 and above is J9 JVM.įor 8.98.3.0 and above: /QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit/jre/lib/fontsįor 9.1 and above: /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/fonts On V5R4 and V6R1, there are both “classic JVM” and the new “J9 JVM”. If you are still running classic (Sun) Java, copy the font files to (version could be jdk16): /QOpenSys/qibm/ProdData/Java400/jdk15/lib/fonts On V5R3 only the older “classic” JVM available.This is obsolete now. But in AS400, there are more than one JVM technology with different combinations. Example: E:\Program Files(x86)\Java\jrockit-jdk1.6.0_45-R28.2.7-4.1.0\jre\lib\fontsįor AS400 platforms, Enterprise One does not ship JRE as it is “in-built” in the OS. If the enterprise server jde ini has a defined inProcessJVMHome path under Section, make sure to place the fonts under jre\lib\fonts folder of the used jre. Tools release 9.2 and above (all platforms except AS400)ĮnterpriseOne folder. Tools release prior to 9.2 (all platforms except AS400)ĮnterpriseOne folder \system\JRE\lib\fonts Fonts default Location for Embedded BIP Engine (XMLP kernel) In order to test this on enterprise server, the font has to be added to the xdo.cfg or directly to the template. In order to build the template you can place the font in the fonts directory of the client where you are building the template, note that this will not work on the Enterprise Server. Fonts can be defined for embedded BIP engine (XMLP kernel) through the BI Publisher configuration file xdo.cfg a OR Fonts can be added directly to the template. There are 2 ways to add fonts to Embedded BI Publisher reports.
![2013 ms word bi publisher add in 2013 ms word bi publisher add in](https://docs.microsoft.com/fr-fr/microsoft-365-app-certification/media/attested.png)
It is the recommendation of Oracle Global Customer Support to only use true type fonts with Embedded BI Publisher for EnterpriseOne.
![2013 ms word bi publisher add in 2013 ms word bi publisher add in](https://docs.oracle.com/cd/E23549_01/bi.1111/e13881/img/xdo11g_tb_2007.gif)
Other fonts such as PostScript fonts have been known to be used with mixed results, however other font types are not supported. The only font type specifically supported with BI Publisher is true type fonts (.ttf).