I used the Domino Attachment builder for the first time and it seemed to work just fine, but when I tried to open the attachment using the link, I received an error. The reson for the error is the URL behind the link:
The database filename is something I have never seen before (two underscores + replica-id + .nsf). In any case the link does not work. Could someone kindly tell me how I can make the Domino Attachment builder generate a working attachment link. Thank you very much.
This topic has been locked.
10 replies Latest Post - 2009-05-20T13:21:23Z by SystemAdmin
Pinned topic Domino Attachment: Strange link
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-05-20T13:21:23Z at 2009-05-20T13:21:23Z by SystemAdmin
Re: Domino Attachment: Strange link2009-04-17T11:10:28Z in response to SystemAdminFurther info: The problem is apparently not the database name, but rather the fact that the url contains the iiop-port. If I copy the URL to a browser and remove the port from it it does open the attachment. But the main question remains; how can I create a working URL with Domino Attachment builder. Thanks in advance.
Re: Domino Attachment: Strange link2009-05-13T14:27:03Z in response to SystemAdminIn your web-inf/config/domino_config/yyy.properties (where yyy is the name of your properties file with connection information), take a look at the ServerName key/value pair. Change the port to your Domino web server's http port.
You probably have:
Change it to:
ServerName=host:80 (or whatever port your Domino http server is running on).
Re: Domino Attachment: Strange link2009-05-14T10:26:46Z in response to SystemAdminHi Sam,
Thanks for your response. I did try that already, but when I deploy the war on the Portal server and then try to access the application, I get this:
Error accessing Domino view.
View: (1. TOC)
Error: NotesException: Could not get IOR from Domino Server: http://Server1:80/diiop_ior.txt
So the entire application fails. This makes sense since the portlets communicate (to my knowledge) with Domino thru diiop. Thus I have to use the Diiop-port. I only have one domino properties document in my project and that's the default (tried to change it to http and diiop). Could I use two different properties; one for the application (diiop) and one for the attachments (http)? And how would I then use them?
Thanks again for looking into this.
Re: Domino Attachment: Strange link2009-05-14T14:08:58Z in response to SystemAdminHi,
Perhaps your Domino Web Server is running on a port other than port 80, or the Domnino web server is not started.
Several options to get the http port:
- If you have access to the Domino admin console: To start Domino web server, on Dom admin console, type "load http"
- If you have access to the Domino admin console, type "show tasks". Look for a line like this, which has the port: HTTP Server Listen for connect requests on TCP Port:8081
- If you have a Notes client, open the names.nsf database on the Domino server. Select the view Configuration\Servers\All Server Documents\; find your domino server document and open it. Select Ports tab, Internet Ports sub tab, Web subtab. Get the port number from the "TCP/IP port" number input.
So in short, make sure Domino Http task is running and verify the correct port it is running on.
Let me know how it goes.
Re: Domino Attachment: Strange link2009-05-15T05:53:22Z in response to SystemAdminHi,
Thanks again, but still no success. The http is running ok. I tested this by copying the URL generated by the Domino Attachment builder to the IE browser and then removing the port 63148 from the host:
ORIGINAL URL (by the builder, not working):
MODIFIED URL (copied to IE, working fine):
If I use the port 80 in the modified URL, it works but IE removes the port in the returned page. My background is Domino and I have a rather short experience in the world of Portal development, so I suspect my problems are in the Portlet Factory model rather than in Domino (just guessing).
I would like to return to something you said earlier about using the http port in the Domino server properties file of my Portlet Factory project. It says in the file that I should use DIIOP if my Domino version is newer that R5:
- Default connection properties for the Domino builders.
- The Domino builders communicate with Domino by making remote
- IIOP calls. Thus the Domino server must be running the DIIOP.task.
- For SeverName, specify the Domino hostname and port that can be
- used to fetch the CORBA IOR.
- Domino R5: You must run the Domino Web Server
- so the builder can retrieve the IOR. Append
- the Domino HTTP port number to the servername.
- For example, localhost:80
- Username and Password are required for either version.
Re: Domino Attachment: Strange link2009-05-15T14:01:28Z in response to SystemAdminIn the Help for the Domino Data Access builder, the "Domino server setup" section says:
To support the ability of this builder to browse a Domino database, establish the following Domino server setting: in the Current Server Document in Domino, under Internet Protocols, HTTP, be sure that the choice for Allow HTTP clients to browse databases setting is yes.
Can you verify that setting is correct?
Another important question: Is your Domino web server configured to forward non-ssl http traffic to ssl (https)?
Mainly, so corba will work, domino requires that the corba IOR must be fetched on a non-ssl port, either directly from diiop task on port 63148 or via a non-ssl http port. If you plan to use the Domino Attachment builder, you should specify the http port so that the generated url for the attachment will use the http port instead of the diiop port.
The instructions in the .properties file you mention below will be better at explaining this in the next release.
Re: Domino Attachment: Strange link2009-05-20T06:19:05Z in response to SystemAdminHi,
To answer your questions:
1) Yes, the setting "Allow HTTP clients to browse databases" is "Yes" on the server document of my server document.
2) No, the server is not configured to forward non-ssl http traffic to ssl.
So if I define the default Domino properties document in my Portlet Factory project to use the HTTP port and try to click the "Get Databases and Views" button in the "Domino Data Access" builder, I get this error:
class com.bowstreet.webapp.engine.WebAppRuntimeException: lotus.domino.NotesException
Plug-in Provider: IBM
Plug-in Name: WebSphere Portlet Factory Designer UI
Plug-in ID: com.bowstreet.designer.ui
NotesException: Could not get IOR from Domino Server: http://MyServer:80/diiop_ior.txt
at lotus.domino.NotesFactory.requestIORPlain(Unknown Source)
at lotus.domino.NotesFactory.requestIORUsingArgs(Unknown Source)
at lotus.domino.NotesFactory.getIOR(Unknown Source)
at lotus.domino.NotesFactory.createSessionUP(Unknown Source)
at lotus.domino.NotesFactory.createSession(Unknown Source)
Thus I come back to a question I asked before: Should I perhaps use two .properties files in this project; one for the "Domino Attachment" builder and one for the rest of the builders? I have tried this, but no success there either? I understand from your posts that one .properties file referring to the HTTP port should be enough. For some reason that does not work here though.
Thanks for your time,
Re: Domino Attachment: Strange link2009-05-20T09:03:07Z in response to SystemAdminHi,
A little more info on this case. If I copy the URL from the error message (http://MyServer:80/diiop_ior.txt) to a web browser, it works fine and the text file opens to the browser window.
Re: Domino Attachment: Strange link2009-05-20T13:21:23Z in response to SystemAdminRegarding your previous question about using two .properties files: You can't specify a .properties file for the Domino Attachment builder.
The Domino Attachment builder uses a Domino Data Access or Domino View & Form builder in your model. (Specified in the "Domino connection handler" input). Thus, the Domino Attachment builder gets its connection settings from whatever .properties file is being used in those builders.