|
|
|
 |
 |
SharePoint was born out of a simple idea: “Sharing Documents”. Microsoft developed family of software products called “SharePoint”, to perform features like File Sharing, Collaboration, and Web Publishing. In simple terms, SharePoint acts as the single platform to share, communicate, store, and collaborate the content, documents, and records.It is the most widely used technology for document sharing and workflow automation.
Why monitor SharePoint 2010?
Read the full post
Like most application servers, WebSphere 8.5 has a rich management infrastructure based on JMX, or Java Management Extensions. In fact, the WebSphere administration console uses JMX to connect to the server to issue queries and perform administrative operations. In a previous post I showed you how to secure JBoss’ JMX connector. While there is a lot of information out there on how to connect to WebSphere via JMX, most of the examples involve either disabling SSL, or worse – disabling security globally. So let’s see how we can access WebSphere’s JMX connector remotely in a secure way. Like most things WebSphere, this could look very daunting at first, but once done, you will have a reliable and secure setup.
Read the full post
Welcome M3Among the many hats I wear, I also wear a DevOps/SysAdmin hat in Lacoon Security.
When I was invited to custom tailor the monitoring solution for Lacoon Security, I didn’t even hesitate and recommended to use Monitis and M3.
Partly because I wrote M3 but mainly because I think it is a really good solution.
Lacoon Security implements a security service for mobile devices, based on the cloud.
Lacoon’s monitoring needs were rather complex, however, nothing Monitis & M3 could not achieve. Here is the proof.
Read the full post
Incentive for raw commandsM3 (or its newer version which you should be using – M3v3) can do pretty much. However it can’t do anything.
M3 is good at timing execution of commands, apply simple parsing and upload the data to Monitis. Allowing you as the SysAdmin (and end-user of M3) to easily shape and design Custom Monitors for your system improving overall system uptime and stability.
Many times this is indeed what happens when trying to monitor different applications. The simple process of ‘Execution -> Parsing -> Reporting’ gets the job done. What happens when it doesn’t?
Well, I’ll tell you what happens – you are left a bit puzzled and think you’ll have to implement the Custom Monitors API which Monitis provide. True – until not long ago.
M3v3 bring you ‘Raw Commands’ capability in its last version.
Read the full post
Recently, we have been talking a lot about JMX – especially about using the Monitis JMX Agent to monitor your JBoss server. As I mentioned in my previous post, in JBoss 6.x and earlier versions, the JMX web console and the JMX connector do not require authentication. This obviously presents a security risk – anyone who knows the hostname and port number can connect to your JBoss server, and not only examine the MBean properties, but even invoke administrative operations. Fortunately, there are some easy steps you can take to prevent this from happening on your production servers. But first, let’s talk briefly about two components of the JBoss management ecosystem.
http://localhost:8080/jmx-console
Monitis GFI is a specialist provider of web and Cloud monitoring services that include website monitoring, site load testing, transaction monitoring, application and database monitoring, Cloud resource monitoring, and server and internal network monitoring within one easy-to-use dashboard. Over 100,000 users worldwide have chosen Monitis as their provider of choice to increase uptime and user experience of their services and products. What makes Monitis' solutions different is that they are fast to deploy, feature-rich in technology and provide a comprehensive single-pane view of on-premise and off-premise infrastructure and applications.
