Data Center Markup Language (DCML) Organization Transitions to ...
454872
The DCML Organization has announced a decision to move its technical and marketing activities to OASIS, organized as a new OASIS Member Section.
81452
The leading vendors in the data warehousing market are running scared of new entrants to the market that are offering data warehouse appliances (i.e. pre-integrated hardware, software, storage combinations) that can offer greatly superior performance at a significantly lower price.  In this white paper we will dispel the 'fog of war' that currently pervades the data warehousing landscape, dismissing those question marks that are irrelevant and gratuitous, but highlighting any genuine issues that need to be addressed.
91307
Partner conference keynote lays out roadmap for transition from a traditional software company.
253773
Are the C programming language and its object-oriented offspring - C++, C#, Objective-C - still well-suited to the requirements of multithreaded, network-oriented computing environments today? That's the question on the minds of engineers at Microsoft Research, whose latest programming language is today being officially moved off the back burner.
74125
Macros for key mappings, tags and entities that can be used with DocBook/XML and other similar markup languages.
705049
(InfoWorld) - Welcome back to the great Office Server smorgasbord. Thereâll be a related review soon covering a couple of open source answers to SharePoint, including Liferay and Plone. And come October, youâll be seeing a fully graded review of the release versions of Office Communications Server and Exchange Server 2007. [ See our Special Report for parts 1, 2, and 3 of this series. ] Meanwhile, weâre topping off this four-part series with a look at how MOSS (Microsoft Office SharePoint Server 2007) and Project Server 2007 combine to give project managers a better handle on team management. Project 2007 This isnât a review of the Office Project 2007 client, but weâd be remiss if we didnât run down a few of its newer capabilities before moving to the server. The 2007 client incorporates the new ribbon-style UI contained in most of the other Office 2007 client applications. This is intended to make the UI easier to learn for new users and faster for experienced users, but weâre only lukewarm on its success in those endeavors. The new ribbon doesnât seem to decrease complexity as much as it simply reorganizes it. Features and concepts will still need to be learned, and experienced users will still need to figure out where those same functions are located in the new UI. Youâll find two basic flavors of the Project client (Project Standard 2007 and Project Professional 2007) bolstered by a third (Project Web Access 2007) once youâve installed Project Server 2007. Only Project Standard can be run as a stand-alone client application with full functionality. Both Professional and Web Access require Project Server on the back end -- Professional so you can access all its features, Web Access so you can access it at all. Standard and Professional carry most of the same features for basic project management, including project editing, all the calendar views and task creation capabilities, etc. Web Access really only allows Gantt chart views and task creation at this level, though if the OLAP capabilities provided in the new Project Server 2007 appeal to you, then Web Access is the only UI that will let your users access those features. Where Standard and Professional begin to differ is in team management. Only Professional gives project managers full resource management features, including team assignments, collaboration support, and specific things such as timesheets. Also, only Professional can make use of the capabilities provided by SharePoint when it and Project Server are combined for better back-end data access. Customizability, however, is a mixed bag, so shop carefully. You can customize Project Standard to a certain degree using Visual Basic for Applications. However, only Project Professional and Web Access can make use of the much beefier API offered by Project Server. Additionally, should project managers want to use the new Serverâs permissioning capabilities, they will have to turn to Professional and Web Access as well. Finally, Project Server can only be administered from the Web Access UI, unless youâve combined it with SharePoint, in which case it can largely be managed from SharePointâs central administration screens. For the most part, Microsoft has ensured that Project Professional is the required client version to make use of Project Server 2007. While the Web Access UI is somewhat functional, itâs really only good as an executive-style viewer of team project data and as a feature add-on to the fat client interface. Project Standard is good only for single-user project managers. Project Server 2007 and MOSS Architecturally, Project Server 2007 runs a middle road between Office Groove Server 2007 (which doesnât need SharePoint at all) and Office Forms Server 2007 (which is wholly contained in SharePoint Enterprise). Project Server is definitely its own entity, but one that can be enhanced in combination with SharePoint. Specific points of enhancement include integration with the Windows Workflow Foundation, document libraries, organizationwide search capability and team work site orientation. To clear some confusion right off the bat, however, MOSS includes a list feature called Project Tasks, which offers some Gantt-style features. This is an independent feature, however, and has no relation or connection to Project Server 2007. If you want to upgrade an existing Project 2003 server to Project 2007, you are in for some detail work. There are no easy wizards here. Migrating data is done via a special .ini file with a series of possible switch parameters that must be configured using a text editor. And, by the way, this step is mandatory. Youâre not going to get away with running a 2003 Project Server next to a 2007 Project Server and waiting until the data migrates itself through user interaction; Project Server 2003 and Project Server 2007 canât communicate, so the upgrade process is unavoidable. Once youâve upgraded, itâs time to connect your existing Project Server 2007 farm to a new or existing MOSS farm. This isnât just a straightforward matter of enabling communication between the two, however. Your first task in this scenario is to move your Project Server machines into the SharePoint domain which unfortunately means you will need to take the SharePoint farm down for this operation. The Project Server 2007 disks will need to install files on each SharePoint Server with front-facing client functionality. Once installed there, each of those instances will need to run the SharePoint Products and Technologies wizard. After that, youâll need to decide which of those machines will become actual Project Server application servers. Only on the Project Server application servers will you need to enable the Project Application service from the Central Management console. This all sounds involved, but Microsoftâs documentation makes it a fairly easy step-by-step process. The tricky part is managing your planning process properly so you know which services need to be enabled and where. Once all that work is completed, youâre still not done. Now, SharePoint is going to want to control the management of all team work sites. So the team sites youâve configured under Project Server will need to be migrated to the MOSS machine as well. After that, youâll also need to unhook Project from its internal configuration manager and wire it into SharePointâs equivalent. Again, Microsoftâs docs make this a fairly simple set of steps, but if youâve got a choice, installing Project Server within a SharePoint farm right from the start is easier. Finally, all the clients who were looking to Project Server for their team sites will need to be pointed at the new sites running off SharePoint -- thatâs the easiest part. You will need to remember that any clients looking to access Projectâs SharePoint features will still need to have the Office Project Professional 2007 client installed. We suppose thatâs reasonable given the nature of Microsoft, but we were actually hoping to see some included viewer functionality within SharePoint that would allow non-Project client users at least to see certain Project files even if they couldnât alter them. Even with the Web Access UI, however, that doesnât seem to be possible. New interfaces and features So after all this installation hassle, what does Project Server 2007 really give you? First, it smartens up your Project Server team work sites. These now have access to SharePoint-managed permissions, document libraries, communication capabilities, and search indexes. SharePoint users will be able to access Project data, not just to simply manage projects but also as part of SharePoint workflows. On a more granular level, we also enjoyed the new Project Web Access look and feel, which can run off a stand-alone Project Server or off a SharePoint Project application server. This has been updated to meld nicely with the new SharePoint UI. Microsoft has also updated the Project Server permissioning system. Administrators now have control over a number of new features, including calendar and Web views, feature add-ins, and specific data views. Itâs a powerful new set of security controls, but administrators will have to endure a learning curve to take full advantage of it. Microsoft has also taken a number of features from Project Server 2003 and beefed them up. Youâll find deeper Outlook integration via the new Outlook Add-In. This gets installed on a user-by-user basis via their Web Access accounts and amounts to a smarter Outlook sync feature. Once installed, it allows users and administrators to use Outlook as another interface for Project. That means project line items can show up as tasks or calendar items and be tracked all the way back to Project Server. Outlook can also act as a timesheet interface with its data again tracked by administrators via Project. Reporting is the recipient of another big upgrade when using Project Server 2007 because its reporting capabilities can now make use of data gleaned from not just Project clients, but also Project work sites and SharePoint work sites and document libraries. Users then get the ability to arrange that data in whatever reporting front end fits their needs: Word 2007, PowerPoint 2007, or Excel 2007. Install the Cube Building Service and your users will be able to access Microsoft SQL Analysis Services to build OLAP-style views for deep drill-down on Project data. This can be viewed using Project or using PivotTable features in Excel. Moving from project to project also gets a boost with customizable templates. Project Server comes with several out-of-box project templates, but these can be edited for specific needs or even created from scratch. Templates cover look and feel for users on the client as well as what they see on the team work site and even what they might see in outside applications such as Excel. Even better, templates run right down to the individual field level, meaning that a template can actually map data relationships between a task field in Project 2007, for example, and a reporting field in Excel. Out-of-box templates cover basic project types for a variety of vertical industries, such as construction or technology R&D, but can easily be tweaked for more specific tasks. This lets your company build a library of templates that project managers can use to quickly get a project moving. There are more features in Project Server 2007 than we can fully cover here (new cost and budgeting features, for instance, as well as slick integration with Office Project Portfolio Server). But as a stand-alone upgrade to Project Server 2003, itâs already worth the trouble. Combined with SharePointâs capabilities, it can be downright amazing in its integration of project management functionality and tracking in projects that never had these benefits before.
313186
Analysis: The DataPortability Workgroup ponders online about retaining rights but easing evolution.
65692
com October 12, 2004, 10:10 PM PT. This fourth priority&#39;s main focus has been enterprise directories as organizations spawn projects around identity infrastructure.
32816
com November 1, 2004, 9:56 AM PT. This fourth priority&#39;s main focus has been enterprise directories as organizations spawn projects around identity infrastructure.
495342
com October 19, 2004, 4:16 PM PT. With most organizations that planned to move already moved to Microsoft Server 2003, OS migration has dropped to the bottom ranks after making
202255
OK, we had an extended breather from our last look at BIND's zone file pri.example.org. It's time to finish up and get a sense of what these records mean. To go off-topic a little, recently, I had the task of setting up two OpenLDAP servers and putting together a test environment for a project with several developers and several applications including some LAMP applications. Without a working knowledge of DNS, the project would have gone amuck.
124078
I think I've mentioned this before but on Saturday Feb 12th I'll be talking  about the Jakarta FeedParser at CodeCon  in San Francisco.  I published an outline  of the talk on the FeedParser wiki.  I'm hoping to have a 0.5 release done before then and havepotentially another suprise in the works.
168478
VMware and Cisco see a data center operating system coming, in which a data center cloud would be populated by servers, storage and Cisco's "intelligent" networking gear, all managed by Cisco and its partners -- starting with VMware.
480369
On Wednesday Microsoft announced that it had completed the development of Microsoft Operations Manager (MOM) 2005, its next-generation operations management server product, which will ship in separate versions aimed at enterprises and mid-sized businesses
743118
(Source: MessageLabs)Administrators struggle with ever increasing complexity in the data center. Join Brian Babineau, Enterprise Strategy Group and Anne O'Neill, Symantec Corporation for an evaluation of these options and the discussion of Veritas Server Foundation from Symantec, a novel approach to Data Center Automation that embodies Symantec's vision for a solution to DCA that is both complete and simple. We invite you to register now for full access to this online broadcast.
481228
Mark your calendar: November 22. That's the day, barring something unforseen, that OPML 2.0 will move from a draft to a final frozen spec. If you plan to use OPML 2.0, or you're already using it, please set aside a few hours to carefully review the spec, between now and the end of September, or at the latest early October, to be sure it makes sense to you.  We're doing this very slowly and carefully so people will believe in the quality of this spec. If you don't think it's a good spec, now is the time to say why. Speak now or forever hold your peace. You may not like the format, that's not the issue now -- it's the spec we're trying to finalize.  Thanks for your help!
331124
An introduction to XML and DocBook: what is it and why should I learn yet another data format?