Multiple connections view in Hawtio - hawtio

Is there a way where in I can view multiple connection information in the same tab in Hawtio? Right now, for every connection, it opens in a new tab.
I want to view all connections in the same tab.

No hawtio only views a single JVM.

Related

Master Data Explorer disables Model and Entities after every action in Excel

I'm working with SQL Server 2014 and Excel 2013 with the Master Data Services Add-on (SQL Server and Excel are both trial versions.)
When I connect to the model then I perform any action on an entity in that model, the Model and the list of Entities in the Master Data Explorer panel become disabled and I have to close the pane, reconnect to the MDS server and select the model again.
My MDS security settings are fine because I can edit the entities I want from Excel, it's just the disabling that is a pain.
Is this the behaviour of the trial version? I haven't found anything that says it is.
Thanks
The Master Data Explorer panel works primarily for a new empty worksheet. If you are viewing a worksheet already populated with an entity and its attributes, there's nothing for the Panel to do. Use the tool bar buttons on the Master Data tab to manipulate an entity. Use the panel to open existing entities into a blank worksheet.

XPages Navigator Control to Open Profile Document?

Converting a legacy Notes application to XPages with Extension library.
Using application layout with navigator control for basic site navigation.
Stuck on how to have a navigator menu item open a profile document for editing by administrator type user...
Have an XPage created that binds to the profile form, but not finding way to have it opened on the onClick event of navigator menu item?
Any suggestions?
You can use ordinary data source. First, get UNID of profile document and initialize data source with it.
WARNING: profile documents are cached, you need to restart http or reset application if there is some background change to profile document (otherwise you see old values). Avoid using profile documents with frequent changes!
With XPages, profiles are obsolete. A better approach is to move the contents of the profile to a regular document and then in the application_init () method read all that data into the application scope. If you have updating profiles then this is critical because of the issues updating profiles across multiple servers and JREs.
If you must use the profiles, on the navigator, set it to open the profile.xsp in Edit mode. The profile.xsp then Edits the profile with the Default Formulas of each bound field retrieving the value from the profile using SSJS. The Submit button runs SSJS which iterates through the items on the document and writes them to the profile, but does not save itself to disk.

xPage as Welcome Page

I am trying to setup xPage as Welcome page for notes client and to be deployed via policies. Only issue it opens up 2 window, one which is Bookmarks.nsf frameset and second one is the xPage. Tried many different ways to close frameset, but some internal setting doesn't like this since its a welcome page frame... any ideas or if somebody has done similar project.
I tried opening a view thru welcome page which opens up the xPage and then to close the view in Postopen event, but no luck. also tried same with Form.
Appreciate help .. badly stuck in it.
One way to do that is:
open your xpage in the client
right click on the tab and create a new bookmark for it
right click on the newly created bookmark and click "set bookmark as home page"
I don't know if you can do that via policies, but at least it works if I do it interactively
You can set this by policy by adding to the ini
StartupDB =
That will load the NSF every time the client opens. This command does not respect the enforce flag as its enforced by default, do not set the enforce flag...
You can also set the nsf to replicate by policy so remote users will be able to open it as well.

Lotus Notes Views are not showing up in the web browser

We have a legacy Lotus Notes application that we want to see if we can make an improvement, first by making a test environment for this application. Currently the application is located on the main server and being replicated every 15 minutes to the web server. The replica on the web server has different forms and views since they are adjusted to display the information on the web browser (in my understanding)
I have made a new copy of the application that is on the main server without any problem. I had some problem replicating it to the web server since I do not understand what will happen to those element design that are not being used in the application on the web server. So what I did was replicating the application from the main server to the web server, then deleted all the design elements on the web test then copy all the design elements from the production environment to the web test.
By doing that I was able to get into the login page then log in. After I login, the frameset that suppose to display the default view giving this error message 'HTTP Web Server: Couldn't find design note'. First of all, I thought this is normal since I could not find the view in the database and that confused me since the live system works without that view present on the database BUT when I tried to access a view that I know present on the database, I still get the same error.
So after all that I opened the web test application on a Lotus Notes client. I can open the views that are exist. Now at this point there are 2 things that I am very frustrated about:
The live system works even when the code specifically mentions views that I cannot find from the Domino Designer. It just does not make any sense
As a test I created a 'Test' view on the web test application. Basically I just told it to fetch one of the form called 'WORec' that contains Work Order information. Into my surprise, the view opens up on the web browser but shows no result, which frustrates me even more since the view 'WOByName' gets all the Work Orders just fine. These 2 views have the same selection formula, so I really do not understand why 1 view is able to show data where the other does not. Moreover if I tell the test view to fetch all the documents in the database it only fetch those documents that are not 'WORec' form
I know this is long but if I can get some pointers on what I am doing wrong here. I am just trying to create a test environment. Unfortunately I never dealt with Domino web application or a replication that completely has different element design.
Let's start with the test view.
When you created the view, you need to first verify it is a Public view. Private views or Shared Private on First Use (SPOFU) views are not what you want here.
also, verify the name and alias of the view is unique to your database.
Next, verify your selection formula is correct.
use formula, instead of simple so you can actually see the formula. e.g.
SELECT #UpperCase(Form) = "WOREC"
Refresh your view designer (F9) - do you see your records coming through?
also, make sure the view is not hidden from Web clients... you will see this in the designer client, when looking at a list of views - a column indicating whether or not it is hidden from web clients, note clients, mobile clients, etc.
if not, open one of the documents up. Show properties, verify the form property in the box (2nd tab), matches the value "WORec". If not, correct your view selection with the correct form name spelling.
Next, you need to make sure you are allowed to view this from the web.
Open the Access Control List (ACL) and add "anonymous" as reader or above.
Open the view in Designer, and Preview it in web browser.
As for the "Couldn't find design note" message - that's not good. You definitely are missing design elements. Whether this is due to a selective replication formula issue, or acl issue, or whatever, is hard to tell. But if you have a Notes thick client and a separate web version, I would recommend different databases (or master templates) and not trying to use selective replication to handle that sort of thing.
As I understand it, you replicated the database then deleted all design elements and manually replaced them by copying from the production web replica. Instead, you should have made a template from the production web database (by doing a design-only copy), and then you should have used the 'Replace Design' feature to update the test web database from that template.
As an aside: an application built the way you describe (two replicas on separate servers, each with a different set of design elements) is a pretty bad implementation. It may have been done in the very early days of Domino, before the "Hide from Notes client" and "Hide from Web" properties were available at the design element level. Or it may have been done deliberately for "security purposes" (which I put in quotes because relying on Domino design element to enforce security on a Domino web application doesn't really make the application any more secure). You may be stuck with this... but you may not be. So before you try to improve or enhance this application, I think you should look into using the "Hide from... " properties on the design elements.
On the other hand, if you stick with the current design, I do want to mention that you're going to need to make sure the ACL settings and selective replication settings on your main and web test replicas match the ACL selective replications settings on the corresponding production replicas. Otherwise, you'll end up with a jumble of design elements when the test databases replicate across servers.
I suggest you to make a new copy of the Notes Database that is on your web server to your test server.
try to open in with your browser and check that all is OK.
open this copy in designer and check that it contains the views that you didn't see previously on test.
I'm not sure that you have really 2 different designs (one for webser different from the one of your main server) so:
- on the main server: open the File/Replication/Option for this application. In advanced, check When web server receives from .... if the design elements is checked.
if not it makes sense that there are TWO different design versions.
Maybe the view you didn't find (on the web server) restricts use? to check this:
- In the view (on the main server) check in the properties of the view the tab with a key "all readers and above". If it's uncheck THIS is the reason why they don't exist on the web server AND that you don't see them in the designer:
If your don't have the role or are not the person which can "who may use this view" you don't see the view and can't copy it.
To correct this simply enter the ACL (file/Application/Access Control) and grant you the corresponding role.
I hope I helped

SharePoint list webpart connections option not visible

I want to connect two list webparts. The problem is that when I go to "Edit Web Part -> Connections" this option "Connections" doesn't apperar.
Searching on google found this: http://office.microsoft.com/en-us/windows-sharepoint-services-help/connect-data-in-web-parts-HA010024105.aspx. There is a paragraph that says: "The Web Part menu may not be enabled or visible on your Web Part Page for several reasons, including that the Web Part or the zone does not support connections, you are using a browser that is not compatible with Windows SharePoint Services, or connections are disabled on your site"
I think connections are disable on my site. Where can I enable connections on a SharePoint site?
Thanks for your help!
Ha ha. In Internet Explorer 11, you have to view Sharepoint sites in "Compatibility Mode"! Imagine that! Without Compatibility Mode, IE won't display the connection menus - but Firefox and Chrome will! Apparently, this is even a problem with Sharepoint 2013.
I saw this problem even when Connections were enabled.
The workaround was to choose Edit Web Part and Click "Apply". This magically made the connection menu appear. However when the page is reloaded, the workaround needs to be applied again.
I'm not 100% sure if I remember correctly, but I had the same issue last week.
First you need access to the central administration at the sharepoint host.
In there, you have to click on "Application Managment" -> "Manage Web Applications"
Then select your web app and click on Web Part Security in the ribbon. If i remember right you should find an option there to allow connections between webparts.
Here in my experience I found that on wiki page web part connection is not possible, if you want to connect two web parts or two list, go and add your lists, or webpart onto webpart page, and on edit page connect them, ok.
There are some issue with placing filter web parts on a wiki page. The filter web part is not visible and it's impossible to select the webpart menu when in page edit mode.
I encountered it a few times. Like user2780851 states. Enable the publishing features, add a new (publishing) page (so in the 'pages' library not in the 'sitepages' library). When you add the filter webparts on this publishing page all the menu options (and the connection option) will be available.
I was able to get things to redisplay without using compatibility mode. In IE 11, what I had to do was hit F12 to pull up the developer menu, and then under the emulation tab, I switched my user agent to Internet Explorer 10, and then it started working correctly. My problem that lead me to this thread was that my web part menu wasn't displaying at all. This is a serious Microsoft fail. Probably why they are planning to abandon IE altogether. Good riddance, says I.
I've found that this issue has caused a lot of confusion, and led people to incorrectly think that connections between web parts isn't available on wiki pages.
The Connections option will appear as long as you are in the edit mode of any web part on the page - it doesn't have to be a web part which will be involved in the connection.
First you need access to the central administration at the sharepoint host.
In there, you have to click on "Application Managment" -> "Manage Web Applications" Then select your web app and click on Web Part Security in the ribbon. If i remember right you should find an option there to allow connections between webparts.
this is answer right i did it and it works

Resources