I have one Notes Template ntf in which the Openntf Domino API plugins do not appear in 'Plug-in Dependencies' library, eg. org.openntf.domino.xsp etc. They are installed on both the server and the local machine, as we use XPiNC. They appear in any a new application created from the template and they appear in other templates and other nsfs. The plugin xml references them but they are still not in there.
<import optional="true" plugin="org.openntf.domino.xsp"/>
The Notes template is on a server. How do I get them in there or solve the problem, I have tried various import methods to no avail, this area is not a strong point for me.
Thanks for any help.
You cannot use an NTF with XPinc. The status bar will show a message about it not running. You can have an NSF with a TEMPLATE NAME that will refresh other database that inherit from that template. If you need the NTF for database creation purposes, develop in an NSF that has a TEMPLATE NAME from which the NTF inherits. (EG: MyAppDev). THe NTF then has a TEMPLATE NAME from whihc other databases inherit (EG: MyApp)
If you're getting an error that you cannot import a class in Domino Designer, there are two places to look.
The library needs "ticking" on the Xsp Properties. This tells the application that it needs that particular plugin at runtime. If it's missing on the server, you'll get an error.
The library needs installing for every Domino Designer that's going to be used to work on the application. Upgrading Notes to a new version will invariably disable previously installed plugins, so you need to go to File > Application > Application Management.... Custom plugins are in the second category, and if they have a red circle crossed through, it's disabled and needs re-enabling.
Related
I’m experiencing an issue with customization projects in Acumatica 2017 R2 Build 17.203.0029.
Specifically, custom screens, while in my project XML, are not visible within the customization project browser nor can they be navigated to once published (which occurs without error). This only occurs on my staging server. Everything works fine in my local dev environment and even on a different instance of Acumatica. My local dev environment matches the staging server in every possible way (Acumatica version, other packages, etc.)
Older versions of the same customization project have been published before and did not exhibit this behavior. It’s only after I replaced the project with newer version of the same project that I encounter the missing custom screen issue.
As shown in the screenshot below, remnants of the custom screens are present in the Customized Screens window. And the ASPX files are present and shown in the Custom Files window.
Screenshot of missing custom screen data
When I compare the “Edit Project Items” objects between the staging the server and my local dev version, they appear the same.
It it possible that the internal customization or sitemap tables on the staging server have inconsistent data? Is there anyway to rebuild them?
The solution appears related to the users roles config. I had not assigned access rights to the custom forms. Doing so solved the issue. The custom screens are now accessible by direct URL and are shown in the customization project browser. Maybe this will help someone else.
I had this same issue when trying to Deploy the customization to another instance.
To fix it I had to go to the site manager and change the URL of the new page
from: "/Pages/SO/CustomName"
to: "~/Pages/SO/CustomName"
I want to ask you about the configuration to the bootstrap4 xpages,i installed it in the domino server then in the domino designer,when i go to the Aapplication>Properties>XPages>xspProperties>Page generation i select the libraray bootstrap and extlib but when i return to the tab general to choose the theme bootstrap i didn't have this choice! i will illustrate you the problem withe these print screen:
This is easiest if the server and Domino Designer are version 9.0.1. Then you can just use the latest Extension Library, which includes everything from Bootstrap4XPages except Select2 component (I believe this was because of licensing issues). Installing the "-designer" package from that will hook into an extension point added subsequently which allows extension libraries to contribute options to that list of themes available.
If using an earlier version of Domino, you need to manually type the relevant theme name into that combobox (it allows you to either select from the available options or type in another option).
Thanks Paul,I installed ExtLib now i have the bootstrap in the list default theme but not in the library id, I will illustrate you the problem with these print screens:
There is a packaged application created in Oracle ADF (lets generalise and say any Java EE framework) that I would like to customise/extend. I want to make changes like add a new JSF page or modify a JSF page in there and change the data which appears on the page.
I do not have the source code, just the war/ear file. Can I import this in JDeveloper for ADF (or Eclipse/NetBeans/IntelliJ in case of other EE frameworks) and create new objects extending the jar files in there without having the source code?
You can run your Jdev in customisation Developer role , open your EAR file , go to your JSF , jsff and try to have customisation put on top of it. You will need to deploy this as MAR file. Similar concept also applies to Oracle's Webcenter and it's taskflow customisations. Also , for this feature Seeded customisation should be enabled in your deployment profile.
Read more here : Customization
Also found this - how customisable the ADF app is depends on how the app is written in the first place. Use of MDS enables higher degree of customisability:
https://docs.oracle.com/middleware/1212/adf/ADFFD/customize.htm#ADFFD2085
I am having a problem with Domino Designer and, to be honest, am not sure if the question belongs here or not...
When I create a new XPage, then drag the Single Page Application from the Mobile panel to the XPage I am not getting the Wizard?
I am using Designer 9.0.1, have installed the current OpenNTF ExtLib (901v00_03.20140120-0650) from OpenNTF and made sure that the correct version is referenced on both the Server (using the tell http osgi ss com.ibm.xsp.extlib command) and in Designer (About / Designer / Plug-in Details).
Does anybody have an idea what I am doing incorrectly?
Thanking you in advance
Ursus
The Extension Library release comes with a couple of updateSite zips inside of it:
updateSiteOpenNTF.zip
updateSiteOpenNTF-designer.zip
updateSiteOpenTNTFExtended.zip
updateSiteOpenNTFSamples.zip
Be sure you are using the updateSiteOpenNTF-designer.zip, and not the standard updateSiteOpenNTF.zip. The designer zip, as the name suggests, contains the extlib content specifically for Designer, such as the Single App Wizard, as well as the rest of the extlib plugins that come in the first zip file listed above.
I know this is not specifically a programming question, but programmers will often have to do this work.
How do I create a website with Liferay portal - the docs are pretty light on this fundamental issue and are all for version 4.4. I am using version 5.2 and the docs don't seem to be relevant.
Do you know what the basic steps are. So far I have logged in as the bruno user and can see the 7cogs website and edit it. But I now need to create my own website (for my company) and be able to develop portlets to add to the parts of the page.
Further I notice that the docs talk about doing work in Eclipse. If our website is all static HTML, (the reason we want liferay is mainly so that we can edit content items using its content management tools), then will there be any need for Java dev, or will it all be drag n drop and clicking to get setup. Any guidance will be much appreciated.
Liferay can be used as a simple CMS, without much Java knowledge : creating, editing and positioning of web content fragments are drag'n'drop and use of the included rich text editor.
But to start using Liferay for your company, there are two main steps : a technical configuration (database, etc.), and a look'n'feel customization.
The technical part
First of all, you should get rid of the 7cogs website : this is called a hook in the Liferay wording. To do that, if you are using Tomcat for the application server, just delete the 7cogs directory as stated here.
You can now create the configuration file for your installation : it's a simple text properties file, named portal-ext.properties and placed in the webapps/ROOT/WEB-INF/classes folder of your tomcat installation.
This file handles most of the configuration of the Liferay portal, for example :
the name of your company
if you want to display a terms of use page on first login
if you want anybody to be able to create an account on your portal
the database where the data will be stored
To do this, the properties in the portal-ext.properties override default properties found in a embedded portal.properties file located in the jar file portal-impl.jar, in the webapps/ROOT/WEB-INF/lib directory. Just unzip the jar file in a temporary folder to access the portal.properties file.
A sample portal-ext.properties file :
company.default.web.id=yourcompany.com
terms.of.use.required=false
company.security.strangers=false
jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username=root
jdbc.default.password=root
Once done, you can startup your application server. As the default admin (named test, something you can change in the portal-ext.properties file), you can access to the centralized web "control center", located in the "dock" (the strange menu labelled "welcome Test" in the upper right part of any page once logged in).
I would advise you to read the administration guide, useful for most administrative tasks.
The "branding" part
Liferay uses "Themes" to automatically decorate the portal pages (logo, navigation, portlet borders...) using images, CSS, Javascript (JQuery) and the templating language Velocity. The themes are bundled in a .war file, like a standard web application, and deployed on the fly either via the control center or by dropping the file in the deploy directory of the server.
Liferay can use several themes at the same time, one for each community (a group of pages, users and content) for example.
Creating your own theme can be done afterwards, using the "Plugins SDK".
The Wiki, forums and blogs can be very useful.