How to create custom JSP in Documentum web publisher? - documentum

I'm trying to create a web page where some content(parts of the page such as footer/header etc) will come from documentum and some data on the page will com from external oracle database.
From what I can tell from Documentum Web publisher docs it seems like I should create a "presentation" that is JSP rather than XSL, but I am not able to figure out how to do that.
Is this the correct approach or is there a better approach? Is there a link to clear sample? Can all this be published into documentum from the web publisher frontend, or do I need direct access to documentum server(via unix etc)?

I got this to work in webpublisher, key was to create a presentation file that when applied will publish as a JSP rendering, JSP code is embedded in the XSL presentation file. Was not very difficult, just not easy to find in the myriad of documentation that Documentum webpublisher comes with.
Documentation

Related

HCL domino add entries to view externaly

I have a hcl application to whose View I want to add entries from my local pc. I have very little knowledge about HCL in genral and have been looking for a soultion for days now without any success. Maybe Im looking at the wrong places but there was little to find. All I know right now is that I will probably end up sending my local data for the entries via postman and I do have to make an agent?/method that is accessable via browser that can receive these information and make entries with them.
I was just pushed into this thing. I wouldnt mind some usefull links to build my foundation as well.
There are many ways to add documents to a Notes/Domino database.
You are not very specific, it is not even clear if you want to do it programmatically. As Torsten said in his comment to your original post, there are many ways to do that.
Here are a couple:
Using the Notes rich client.
Through a web browser, accessing a web-enabled Domino database. This assumes the creator of the database has exposed the functionality to create documents on the web.
Use COM (or Java) to create the documents from an external scriptable application or using a programming language/platform supporting COM:
https://help.hcltechsw.com/dom_designer/9.0.1/appdev/H_EXAMPLES_ACCESSING_THE_DOMINO_OBJECTS_THROUGH_COM.html
Call a REST service on the Domino server that will create new documents. You can write a REST service using Lotusscript, Java or XPages:
https://www.slideshare.net/TexasSwede/break-out-of-the-box-part-2 (you can skip to slide 19)
Use Domino Access Services (DAS), a framework for adding REST services to Domino. A DAS service is implemented in Java and deployed as an OSGi plug-in:
https://ds-infolib.hcltechsw.com/ldd/ddwiki.nsf/dx/Create_your_own_Domino_REST_service_using_DAS
and
https://www.slideshare.net/JohnDalsgaard/engage-ug-rest-services-2015
Use node.js and the Domino AppDev Pack: https://doc.cwpcollaboration.com/appdevpack/docs/en/homepage.html
and
http://www.c3ug.ca/c3ug-blog/2020/6/30/announcement-learning-the-domino-appdev-pack-a-free-course-from-c3ug
There are probably a few more ways that I am forgetting...
Before you do anything else, you need to learn more about the Domino platform, the structure of a database, and the proper terminology used in Domino. If you don't understand the basics, you will not be able to write any kind of integration with Domino.

Should I have views in a .NET Core API

At the company I work at we have a couple of different services
API (.NET Core)
Internal Frontend (React)
External Frontend for customers (React)
I was asked to create some views which will be converted to PDF's by an API, but I can't decide where to put them as they are not related to our Internal- or External-facing projects.
My first thought was to put them in our .NET Core API. However this has previously been a strict json-only API, so I have an itch that this is not the intended use.
So internet, my questions are as follows
Is it a big NO-NO to put Razor-views in our API?
Should I dedicate a microservice to this?
What is best practice?
Thanks in advance!
You're right, Razor views will be excess. I see two options:
Backend: Create an endpoint which will return a PDF file based on passed data. Of course you can expand data. This way is similar with Razor: you have a view model and render it to PDF file. An example of library: iTextSharp.LGPLv2.Core
Frontend: Convert HTML to PDF on client's side. Something like react-pdf
I prefer first option, because, first of all, there is already an option "Save as PDF" in browsers, so it will be some kind of duplication of functionality. And on the other hand back-end PDF generation seems more flexible (you can use all of your domain and you can create independent layout either) and you can organise some kind of file cache.

af:inputfile drag and drop not supported in IE11

For one of our clients we are building a web application with oracle adf.
One of the requested features of this application is having a drag-and-drop file upload.
Fortunately the af:inputfile component supports this feature out of the box.
Unfortunately that feature is not supported in Internet Explorer 11, which we absolutely have to support.
Now I have been trying to get it to work using the dropzone.js library and the drag and drop functionality seems to be working. but I haven't been able to get the POST request to the ADF side of things quite right.
Even if I did it would be a lot of custom code that would have to be maintained, if it's the only way to make it work that is fine but if there is a more elegant solution to this I would like to know.
What you can do is to use ADF JavaScript APIs, more specifically AdfFileUploadManager(https://docs.oracle.com/middleware/1213/adf/api-reference-javascript-faces/oracle/adf/view/js/util/AdfFileUploadManager.html)
You need to instantiate it by giving it the ADF Component reference, which that can be an af:inputFile with display="none"
Then you can utilise your DropZone or any other functionality and use addFileToQueue to send this information to server side and convert it to UploadedFile.

Can a WCF Service display a help page or other content?

If you enter a service endpoint in a browser you get a Microsoft generated page with a link to the wsdl and some sample C# and VB code for creating an instance of the service client. If you enter the wsdl link in a browser you get the wsdl. This all assumes no strange security restrictions of course.
Is there a way to have a service return a page of your own design? If I wanted to have a nice help screen describing the available service methods, or describing possible error messages for example. Either replacing the MS generated default page, or something that can be viewed like a wsdl but with a ?help query parameter for example.
I'm looking for really simple here with minimal changes to the existing services. If possible something that can be done by content creators or technical writers and not the service developers.
I'm not sure if you can override the default help page, but you can definitely serve up a help page. This article on WCF Custom Help Page explains how.

Mysql and Dojo Connection

Is there any way to connect mysql database with dojo web pages. Kindly give me some guide lines so that I can make it possible.
Dojo is a Javascript toolkit. When running in the browser, you will need some sort of adapter on the server to communicate with a sql database, usually through some sort of abstraction. It's considered bad practice to do anything which would pass through sql requests from client javascript code for security and probably for other reasons. Very often, a simple "web service" (servlet, php script, etc.) would service requests, read from the database and emit data to the client over HTTP in JSON, XML or some other format.
That said, Dojo does provide some abstractions beyond that. dojo.data provides an API for data access from Javascript which abstracts the data source, and it is used by various Dojo widgets including the dojox.grid. Take a look at QueryReadStore which comes with a sample PHP implementation.
AFAIK not without any serverside component (Servlet, PHP etc.)