text:
US7669199B2 - Installation of software stacks including uncoordinated projects - Google PatentsInstallation of software stacks including uncoordinated projects Download PDF
- Publication number
- Authority
- Grant status
- Grant
- Patent type
- Prior art keywords
- software
- information
- software applications
- installation
- projects
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
This application claims priority from U.S. Patent Application Ser. No. 60/566,310 entitled "OPEN SOURCE APPLICTION DEVELOPMENT TOOLS" which was filed on Apr. 28, 2004, as well as U.S. Patent Application Ser. No. 60/566,301 entitled "OPEN SOURCE SOFTWARE PACKAGE INSTALLATION" filed on Apr. 28, 2004, and U.S. Patent Application Ser. No. 60/566,311 entitled "POST-INSTALLATION TOOLS FOR OPEN SOURCE APPLICATION DEVELOPMENT PACKAGES" filed on Apr. 28, 2004. The entire disclosures of each of these applications are incorporated herein by reference.
The present invention relates in general to software projects including open source projects or projects that are otherwise available for stacking and, in particular, to a tool for assembling, installing and supporting or servicing software stacks.
Conventionally, packages of software have been formed from proprietary applications. These applications have generally been provided by a single source or by industry partners such that the applications have been developed in a coordinated way to facilitate such packaging. However, the assembly and use of such packages has generally been limited by associated licenses. More recently, open source software has grown rapidly in importance and availability. Generally, open source software is software where the source code is available for copying and modification and whose licenses generally give the user freedom to use the software for any purpose as well as to modify and redistribute the software. In this regard, open source software is distinguished from proprietary software in that the source code of proprietary software is generally not made available to the end user and the licenses for proprietary software generally place significant restrictions on use, copying, modification and redistribution. In addition, open source software is generally made available for free or for a reasonable reproduction fee whereas proprietary software is frequently provided on a for profit basis.
Open source software has a number of potential advantages for end users. First, because the source code is available to the end user and the licenses allow for substantial freedom of use and modification, the end user has significant flexibility to adapt and optimize the code for a particular endeavor. In this regard, the end user is not tied into a particular proprietary system. In addition, studies have shown that open source software tends to be of very high quality. That is, due to the open nature of the software and the opportunity for virtually unlimited peer review, the open source software is generally continually improving in quality. Moreover, because the open source software is generally available for free or at a nominal cost, there is a significant potential to use the open source software in a cost effective manner. For these and other reasons, many governments and other entities have mandated or encouraged a transition from proprietary software to open source software for systems under their control.
At the present time, however, significant obstacles remain with respect to fully realizing the potential advantages of open source software or other independently developed or uncoordinated software. One such challenge is assembling software stacks. Typically, a software system, application or tool ("project") does not function in isolation. Rather, a particular project may require another project (e.g., open source or proprietary) as a prerequisite to its proper operation and, once installed, may be used by other projects. Because of these vertical dependency relationships, end users often require or desire a software stack including multiple projects. Assembling such stacks involves identifying individual projects required for an endeavor as well as addressing the dependency relationships. This may require significant expertise and time. Although some open source providers offer coordinated projects or stacks, open source software tends to be uncoordinated.
Another difficulty associated with the use of uncoordinated software such as certain open source software relates to installation. Installation involves addressing various machine configuration issues, integrating software projects, resolving conflicts and testing for proper interoperation of the individual projects as well as interoperation between the projects and machine components. Again, installation often requires significant expertise and time.
In addition, there are a number of post-installation issues relating to the use of such uncoordinated software. For example, the use of any software may require occasional reference to user manuals and other documentation. Such documentation may not be readily available in the context of a stack including multiple uncoordinated (e.g., open source). Even when documentation is available for individual projects, such documentation may not be adapted for the environment of a particular software stack. Similarly, training materials such as tutorials may not be available or optimized for a software stack environment. Other post-installation issues relate to uninstalling projects or altering installed projects or stacks.
The present invention relates to assembling, installing and supporting or servicing software stacks composed of multiple projects, including uncoordinated projects. The projects are software components for particular applications such as proprietary software applications and open source projects. A stack is defined by installing two or more projects in a processing environment (single machine or distributed) such that the projects share one or more logical resources such as a function library or are otherwise configured for cooperative and dependent operation. That is, two projects have a dependency relationship where a first one of the projects requires a project, such as the other (second) one of the projects, to perform a function that defines a substantial part of the first project's application. The projects are thus vertically integrated. In this regard, uncoordinated projects are projects that are not specifically preconfigured for such cooperative and dependent operation in a stack. For example, such projects may be developed by multiple parties working independently or by open source developers.
In particular, the present invention is directed to a tool for addressing a number of the above-noted issues relating to software stacks including multiple uncoordinated components. The tool facilitates stack assembly by identifying individual projects, managing dependency relationships and providing an intuitive graphical interface to assist the user. In addition, the tool facilitates installation by addressing machine configuration issues, resolving conflicts and performing at least partially automated testing. The tool also addresses a number of post-installation issues including the generation of appropriate documentation and training tools, as well as by facilitating de-installation of projects as well as modification of replacement projects and software stacks.
In accordance with one aspect of the present invention, a method and apparatus (collectively, "utility") is provided for enabling convenient access to stacks of uncoordinated software projects. Specifically, the utility involves receiving an input regarding a stack of interest, accessing information regarding potential stacks and outputting stack information responsive to the input. From the perspective of a user or user system, the utility involves accessing a system for providing stack information regarding stacks of (formed from) uncoordinated software projects, submitting an input (e.g., to a local processor or remote platform) regarding a stack of interest and receiving stack information responsive to the input. The stack information may include, for example, an identification of the project content of one or more possible stacks, projects for installation as one or more stacks, and/or installation information for one or more possible stacks. In this regard, for example, a stack or information defining a stack may be assembled from projects or project information responsive to the input, or such stacks or information defining stacks may be predetermined and stored. That is, the stack information can be assembled at various times and in various ways. In any event, convenient access can be provided to information useful in assembling and/or installing stacks formed from uncoordinated software projects, e.g., including one or more open source projects.
In accordance with another aspect of the present invention, a utility is provided for use in assembling stacks of software projects. That is, the utility is useful in determining the project content of a stack. It will be appreciated the utility may further be useful in identifying and/or resolving conflicts, dependency characteristics and other issues relating to assembling a stack. The utility involves operating a computer based tool to receive input information regarding a stack of interest, determine at least a first characteristic of a first project of the stack, and provide information regarding a second project of the stack. The input information may, for example, identify a function of this stack, identify the first project for inclusion in the stack or otherwise provide initial information for use in assembling the stack.
Based on this input information, the computer based tool is operative to determine the first characteristic of the first project. The first characteristic may relate, for example, to a dependency relationship of the first project or a resource requirement. In this regard, the computer based tool may identify one or more projects on which the first project depends, one or more projects having a dependency that is satisfied by the first project or may relate to ports or other resource requirements. This characteristic is used to provide information regarding a second project of this stack. Thus, for example, dependency relationships, conflicts and the like may be identified in an output to the user or resolved so as to assist in stack assembly. For example, one or more graphical user interfaces may identify dependencies or conflicts to resolve in order to complete a desired stack assembly.
The utility can be used to facilitate assembly of uncoordinated projects. In this regard, the first and second projects may be uncoordinated and may include open source projects, proprietary projects, other projects or combinations thereof. Preferably, at least one of the projects in the stack operates at a tools or applications layer of the stack above an operating system level of the stack.
According to another aspect of the present invention, a utility is provided for use in assembling stacks by reference to a knowledge base including information regarding a set of supported projects and dependency information. Specifically, the utility involves identifying a set of software projects and determining, for the set of software projects, a set of dependency relationships relating to interoperation of the software projects. A controller includes logic for accessing information reflecting the dependency relationships and relating particular ones of the software projects based on the dependency relationships. In operation, the controller receives a user input indicating an interest in assembling a stack of projects and identifying, at least by type, at least a first project for inclusion in this stack. Based on this user input and the dependency relationships, the controller identifies at least a second project for inclusion in the stack. For example, a user may indicate a particular function to be performed by the stack or a particular project that the user is interested in using. In the case of an identified function, the controller may identify project options associated with the function from which the user can select a desired project. In any case, once a project is identified, the stored dependency relationships can be used to identify prerequisite projects, projects used by the first project and further associated dependencies. It will be appreciated that such dependency relationships may exist between first and second groups of programs. In that case, each group effectively functions as a project and the assembly of the groups defines a stack. In this manner, the user can efficiently assemble a stack where dependency relationships are satisfied across the stack.
According to a still further aspect of the present invention, a utility is provided for filtering projects in connection with a request to access or use projects. It has been recognized that the ready availability of externally developed projects is problematic for many entities. In particular, in the context of open source projects, such projects are readily available at no or a nominal cost. As a result, personnel may sometimes access such projects without consideration of compliance with license terms or company policy. Moreover, as noted above, open source licenses can include a variety of terms and obligations regarding reproduction or use of the open source software. In many cases, entities may be unaware that such open source projects are being used until undesired consequences have occurred. Accordingly, it would be desirable to provide a tool to assist such entities in facilitating compliance with policies developed by the entity in this regard.
An associated utility in accordance with the present invention involves defining filter criteria relating to access or use of software projects, receiving a request for access to or use of one or more software projects and operating a computer based tool to process the request in accordance with the filter criteria to provide an output responsive to the request. The filter criteria reflect a policy affecting the requestor independent of any rights granted by the providers of the software projects or lack thereof. Thus, for example, the filter criteria may define what projects may be accessed, by whom, and for what purpose. For example different criteria may apply to different personnel (e.g., software developers, IT personnel, accounting) and for different purposes (strictly internal use versus incorporation into product). The filter may be implemented in connection with a stack assembly and installation tool. In this regard, graphical user interfaces may only present project options that are appropriate for the person or purpose at issue or filtered projects may be otherwise unavailable for selection in connection with such user interfaces. In this manner, adherence to the entity's policy concerning projects may be enforced. Projects may be filtered, for example, on a project-by-project basis, based on a type of or category of the projects, or based on a license association of the project.
In accordance with a still further aspect of the present invention, a utility is provided for installing uncoordinated software. An associated system involves a configuration module for configuring a number of uncoordinated software projects into a stack and an installer for installing the stack on a computer. For example, the configuration module may configure the projects into a stack responsive to a request from a user or a user system. In this regard, such a stack may be identified with the aid of an assembly tool as discussed above. Alternatively, the projects may be configured into a stack prior to handling a specific request. Preferably, the stack is configured in a manner that resolves dependency issues with respect to the included projects. In addition, the configuration module may take into account the state of the machine on which the stack is to be installed in connection with considering such dependency issues or resolving potential conflicts. From the perspective of a user or user system, the utility involves submitting input information regarding a stack of interest to a configuration module and receiving installation information. Such installation information may include, for example, information regarding an installation procedure, projects reflecting a configuration for use in the stack and/or installation tools. The utility thus addresses a number of problematic issues relating to installation of stacks formed from uncoordinated projects.
In accordance with a still further aspect of the present invention, a utility is provided for use in installing a stack of uncoordinated projects on a machine or other system designated by a user. An associated installer may be resident on the designated system or interconnected to a system via a LAN or WAN. In addition, the installer may be operatively associated with an assembly utility as described above or may operate independently. The installer utility is operative to receive input information regarding a stack of interest, determine at least a first characteristic of a first project of the stack, and provide information regarding a second project of the stack. The input information may, for example, identify a function of the stack or identify the first project, at least by type. In response to this information, the utility may identify one or more projects having a dependency relationship with the first project or a resource requirement of the first project. Since such information may be used to identify the second project so as to resolve a dependency relationship or avoid a resource conflict. The utility is useful for installing stacks including uncoordinated projects (e.g., open source projects) where at least one of the projects operates at a tools or applications layer of a stack above an operating system level.
In accordance with another aspect of the present invention, a utility is provided for assisting with post-installation support in connection with an installed stack of uncoordinated projects. This support utility may be provided in conjunction with assembly and/or installation utilities as noted above or independently. Moreover, the support utility may operate in connection with a local system or may be accessed via a network, e.g., the Internet. The support utility involves receiving an identification of a stack including a number of uncoordinated software projects, selectively accessing storage to obtain support information specific to that stack and outputting the support information to a user. The support information may include, for example, a tutorial or documentation specifically tailored for the package. Support information may be preassembled and indexed to the stack or may be stored as separate chunks of information that are assembled in response to a request. In this regard, documentation may be stored as structured content, e.g., associated with metadata such as XML tags, identifying a context or association of the data, for example, an association with a particular project. Text and/or graphics may be assembled in this regard. In addition, the support information may be selected based on operating environment information for the stack such as information relating to the machine of a user or operating system of a user.
In accordance with yet another aspect of the present invention, a utility is provided for managing updates in connection with an installed stack of uncoordinated projects. It will be appreciated that updates relating to a stack such as project updates, dependency updates and support information updates may become available from time to time. Managing such updates can be problematic, particularly in the context of stacks of uncoordinated software projects. The utility of the present invention involves receiving information regarding the availability of an update concerning a stack, identifying a stack potentially affected by the update, and providing update information to a user or user system. The update information may include, for example, a notification to a user that updates are available, updated software and/or installation information. In this regard, an update may be automatically installed or installed upon receiving an indication from a user that the update is desired. Preferably, update installations are accomplished while leaving at least a portion of the previously installed stack in an installed state, e.g., without uninstalling one or more projects of the stack. An associated update installation process may involve determining an installation sequence, resolving any dependency or resource conflicts, performing an installation of the update in accordance with the determined installation procedure and testing the update upon installation. Associated support materials may also be made available in connection with the update.
In accordance with a further aspect of the present invention, a utility is provided for enabling substitution of projects within a stack of software projects. The utility involves receiving an input in relation to an installed stack including a plurality of software projects and, in response to the input, substituting for a first one of the projects a substituted project having substantially equivalent functionality. It will be appreciated that this utility is particularly, though not exclusively, useful in connection with open source projects that often have licensing terms that provide significant flexibility in configuring stacks. For example, the utility may be used to substitute a second database project in place of a first database project in a given stack. In this manner, a user can experiment with different projects to build a stack with optional performance for a given endeavor.
In accordance with yet another aspect of the present invention, a utility is provided for managing licensed information. The utility involves storing public information and private information concerning a given software license; providing access to at least a portion of the public information; receiving a request for access to the private information; responsive to the request, verifying an authorization to access the private information, and selectively providing access to the private information based on the verification. For example, in connection with a request to access the private information, a user may be prompted to enter a password or other authorization information. Such authorization information may be used to encrypt and decrypt the private information so as to inhibit unauthorized accesses to such information.
For a more complete understanding of the present invention and further advantages thereof, reference is now made to the following detailed description taken in conjunction with the drawings, in which:
In the following description, the invention is set forth in the context of a graphical installer system that encompasses stack assembly, installation and support functionality. It should be appreciated that, as noted above, such functionality may be provided independently, rather than as part of an integrated system, in accordance with the present invention. Moreover, it will be appreciated that various aspects of the invention have application beyond the specific context described below. Accordingly, this description should be understood as exemplifying the invention, and not by way of limitation.
In the following description, the application development environment is first described in relation to the open source software movement. This represents an illustrative application of stacking uncoordinated projects. Thereafter, a system architecture in accordance with the present invention is described. Finally, specific functionality for stack assembly, installation and post-installation support is described in detail.
I. The Open Source Application Development Environment
The present invention is directed to a tool for use in assembling, installing and supporting software stacks including, for example, stacks that include one or more open source projects. As noted above, stacks including open source projects are particularly apt for illustrating the various aspects of the present invention, as open source projects are typically uncoordinated and are typically associated with licenses that provide significant freedom for configuration in custom stacks. Indeed, the flexibility to modify and combine such projects as desired is a principal motivation for the open software movement. However, it will be appreciated that stacks may be formed from proprietary applications or a combination of open source projects, proprietary applications and other uncoordinated projects where licenses allow. Indeed, it is anticipated that such combinations will become increasingly common. In any event, the invention has particular advantages in the context of forming stacks of uncoordinated software components, i.e., projects or applications that are not preconfigured to share logical resources such as function libraries or otherwise specifically configured for cooperative and dependant operation in a stack.
In the examples below, such stacks are described in the context of an application development environment. In this regard, an application development environment refers to a stack that includes at least one project, that is, an application or a development environment tool, operating above the operating system or hardware levels. This may be understood by reference to
Operating system software and development tools have historically been sold by competing commercial vendors and the software is proprietary.
It will be appreciated that there is generally limited flexibility relating to integrating stacks for the software development environment. More specifically, existing operating systems provide an open platform by which particular products can operate independent of the specific hardware environment to a significant degree. Moreover, many products can operate across multiple operating systems. However, at the application layer 202 and development environment tool layer 204, options are much more limited. Some commercial software developers provide integrated stacks of multiple proprietary products or provide individual products that can be readily integrated into a stack. Similarly, integrated open source stacks or coordinated open source projects are provided by some software developments. These products are developed much like the corresponding proprietary products but have open source rather than proprietary license associations. However, these commercial developers generally have little incentive to accommodate interoperation with respect to products of competing commercial developers. Accordingly, such stacks may be limited to products of a particular commercial developer or a developer and industry partners. Accordingly, an end user has limited flexibility and may be locked into an overall stack environment due to a need for a particular product.
Open source software, particularly Linux, has become widely adopted for the operating system layer. In addition, open source development tools and applications are emerging.
As noted above, while many high quality open source projects are available, there are a number of difficulties associated with the stacking of multiple open source projects (alone or together with proprietary products) to enable a full application development environment. This is graphically illustrated in
Moreover, considerable expertise and time may be required for installation of a stack once assembled. For example, installation issues may involve determining a proper installation sequence, addressing various hardware issues, resolving conflicts and testing an installed stack, for example, to determine that required files are accessible. Post-installation issues involve providing appropriate training tools and documentation as well as facilitating the installation and modification of particular projects as well as stacks. These issues are addressed by a system according to the present invention as described below.
II. System Architecture
The illustrated system 500 includes a knowledge base 504 that stores and provides knowledge required for the noted open source stack functionality and an engine 506 that provides the logic for executing such functionality. The knowledge base 504 and engine 506 may be resident on the user machine 502, or may be at least partially accessible to the user machine 502 via a network such as a WAN, e.g., the internet. Moreover, the knowledge base 504 and engine 506 may be resident on a single processing platform, or a distributed architecture may be employed.
The illustrated knowledge base 504 includes, for each supported project, project information 504A such as identification information and legal information, operational information, and category information. The knowledge base also includes certain machine state information 504B regarding the user machine 502. In addition, the knowledge base includes certain stack information 504C for use in executing functionality at the stack level, such as testing information.
With regard to project information 504A, the information that may be included in the knowledge base 504 to identify a given project may include the project name, version, type, home URL, categories, description (with comparisons and recommendations) and links to full project details. The legal information will generally include any licenses with full license text or links thereto. Such license information provides important legal information to users and further supports license filter functionality as described below. The projects may be stored locally or downloaded or otherwise accessed at the time of installation.
The operational information may include dependency relationship information and other resource information. For example, the dependency relationship information may include a list of prerequisites for each project, along with a description of why that dependency exists and how the dependent project is used. The dependency relationship information may further include a list of other projects that use each project, together with a description of why that dependency exists and how the dependent project is used. As will be understood from the description below, such information is used to properly assemble stacks as well as to provide stack explanation information to the user. In addition to dependency relationship information, the operational information may include other resource information such as ports used.
The category information allows for sorting and filtering of projects. For example, the categories utilized may include:
- Client
- Database
- Documentation
- Internet
- Programming
- Sample
- Security
- Server
- Source Code Management
- Testing
In this manner, users can conveniently access desired project information.
The machine state information 504B may include updated information regarding projects and other resources that are available or unavailable on the user machine 502. For example, if a particular tool such as a database has previously been installed, this may be stored in the knowledge base 504 and taken into account in addressing dependencies and assembling stacks so as to avoid conflicts that might otherwise occur. Similarly, port usage and other resource issues may be accounted for so as to facilitate integration and proper interoperation of installed projects.
The illustrated knowledge base 504 further includes stack information 504C. Certain information may be indexed to stack combinations rather than to individual projects. For example, information corresponding to project information described above may be stored for common stacks. In addition, certain installation information such as testing parameters may be defined in relation to stack combinations.
The knowledge base 504 may store various other kinds of information not shown such as operating environment information. For example, information may be stored to support installation for multiple operating systems and to associate particular uses of projects or stacks with particular operating systems. For example, it may be desired to develop on Windows and deploy on Linux.
The engine 506 accesses the knowledge base 504 at run time to obtain all necessary information and executes logic for stack assembly, installation and post-installation support as described in detail below. The user can use the graphical user interface 508 to receive prompts and other information to assist in implementing this functionality and to enter associated information. The printer 510 allows for generating hardcopy documentation.
It will be appreciated that the illustrated architecture allows for convenient system implementation and maintenance. In particular, projects or other information can be added or modified simply by updating the knowledge base 504 substantially without updating the engine 506 or other system components. Moreover, the engine 506 allows for rendering of interfaces with a consistent look and feel across operating systems or other implementation variations.
III. System Functionality
As noted above, a system in accordance with the present invention may provide open source stack functionality related to assembly, installation and post-installation support.
A. Assembly
Stack assembly generally relates to identifying a number of open source and/or other projects to form a stack for addressing a particular endeavor. In this regard, the system of the present invention can be used to perform a number of functions. For example, information regarding particular projects can be accessed in order to obtain a description of the projects as well as dependency information. In addition, information regarding stacks for common types of endeavors, such as electronic commerce web site design, can be accessed. In this manner, software developers who may have limited knowledge of available open source and other resources may quickly assemble stacks. The system is also fully functional to access machine state information, project information and stack information such that the engine can be used to address dependency relationships and facilitate stack assembly as described below.
Referring to
More specifically, in the panel 602, primary projects are shown in bold. Dependent projects are shown in normal typeface. Mandatory projects are checked and cannot be changed. When a project is highlighted in the panel 602, information relating to that project, in this case Tomcat, is provided in panels 604, 606 and 608. In the illustrated example, the title and version of the project is identified at the top of panel 604 together with information in parentheses indicating whether it is, for example, a mandatory project or installed project. A link to the project home URL is then provided followed by a link to view the project license. Also shown are categories associated with the project that can be used for grouping or filtering the projects and an identification of the ports used by the project. Finally, a description of the project is provided including, in some cases, recommendations or tips relating to the project.
The used-by panel 608 lists other projects that depend on the highlighted project. Conversely, the prerequisites panel 606 shows other projects that are required in order to install the highlighted project. It will thus be appreciated that the panels 606 and 608 collectively define the dependency relationships for the subject project.
This dependency relationship information is derived from the knowledge base and is used by the engine to provide assistance in graphical form related to stack assembly. In this regard, if the user selects a project in panel 602 by checking its associated install box, and that project has a prerequisite that can be fulfilled by two or more other projects, or if there is an unchecked dependency, an indication (e.g., audio or visual) may be provided to prompt the user to resolve such issues. In this regard, the project name turns red in the illustrated implementation and the user is unable to continue with stack assembly until the dependency is resolved. For example, if the project JBoss is selected in panel 602, the JBoss lettering may turn red to indicate that a prerequisite is required. The user can then consult the prerequisites panel 606 which, in this case, would indicate that JBoss needs either MySQL or PostgreSQL to continue. In the illustrated implementation, the "Next" button on the GUI is disabled until the dependency issues have been resolved, thus ensuring that the user does not continue until all requirements are met. In other cases, dependencies may be selected automatically.
In the noted example, the user may then elect to select MySQL to satisfy the JBoss dependency. Once the selection is made, the JBoss project will no longer be listed in red thereby indicating that the dependency has been satisfied and stack assembly and installation may proceed. As noted above, a project type is listed in parentheses next to the project name and version at the top of panel 604. The types of projects include mandatory, dependent, primary or already installed. The project type is a link and if clicked will give a description of each of the project types. Similarly, the license identification is a link which, if clicked, presents the full text of the license in panel 604. The categories associated with each project are also links. If these links are clicked, other projects in the category are listed in the panel 604. For example, if the category "server" is clicked, the panel 604 is filled with a project description box with an initial description such as
- Tools usually found on servers or developer workstations. Not typically intended for end users.
followed by a listing including ANTLR, Apache, Http Server, etc. Projects listed in this description are links which, if selected, provide a more detailed description of the selected project. In this regard, links may be provided throughout the text, for example, when a supported project is listed in the description of another project.
- Tools usually found on servers or developer workstations. Not typically intended for end users.
Once a project has been installed, the next time the user runs the system the installed projects are shaded in panel 602 and are no longer selectable.
A button (not shown) is also provided in the tool bar to toggle between install and uninstall modes. If this button is selected, for example, to switch from the install mode to the uninstallation mode, a pop-up box will appear warning that selected projects will not be installed and confirming that this is what the user intends. Once this intention is confirmed by the user, the system enters the uninstall mode. In this mode, the projects that are installed are shown in the project list of panel 602. Again, primary projects are shown in bold and dependent projects are shown in regular typeface.
By way of example, in the install mode, the user may select Aspect J, Castor, Eclipse and Eclipse plug-ins for installation. It may be noted in this regard that if the Eclipse plug-in is first selected, the Eclipse project will be automatically selected. Once all of the desired projects have been selected, the user may select the next button 610 to proceed. If any of the selected projects require more information to be properly installed, a project properties page will be shown to collect this information. A further user interface screen may be provided, if desired, between the noted project selection and project properties screens to check the ports (and potentially other resource requirements) to make sure the machine state is compatible with the selected projects. If the selected project requirements are not met, the user will be instructed as to how to correct them. In some cases, any problems in this regard can be corrected automatically. In any case, installation can be deterred until all requirements have been met, thereby avoiding potential installation complications. The user can choose to go backward and change project selections as one way to resolve any issues.
An example is shown in
When the user is finished with the installation instruction screen 800, the user can select the next button 802 to go to the installation screen 900 as shown in
The projects that may be installed in this manner may include, for example:
Apache Server
AspectJ sample application
Avalon Phoenix
Maven Developer sample application
Maven Multi-Project sample application
Maven Server sample application
Castor sample application
sample application
MySQL Connector/J
Display Tag
Eclipse Plugin: AspectJ
Development Tools
Eclipse Plugin: CDT
Eclipse Plugin: CSS Editor
Eclipse Plugin: JBoss-IDE
EJB Benchmark
blueglue Existing Server
Roller Weblogger
External MySQL Integration
External PostgreSQL
blueglue Sample: Spring-JSF
blueglue Sample: Spring-Struts
Hibernate/AspectJ sample
blueglue Sample: Spring-Tapestry
blueglue Sample: Spring-Web Work
sample application
Hibernate/Middlegen sample
blueglue Sample: SpringMVC
Hibernate/XDoclet sample
Squirrel SQL Viewer
Java Service Wrapper
Very Quick Wiki
Web Work
It is noted that this exemplary listing includes open source projects as well as at least one proprietary application. Other open source projects and proprietary applications may, of course, be supported.
The GUI may also execute a filter function to selectively enable or inhibit access to particular projects by individual users, e.g., within a client entity. For example, a company may configure the system to assist in implementing a policy regarding, for example, what projects may be accessed, how such projects may be used, and by whom. In this regard, a company may define such projects on a project-by-project basis or by type; may specify a set of projects that may be used internally, the same or a different set of projects that may be incorporated into products (generally or on a product-by-product basis), and other project sets for other purposes; and/or may specify what projects may be accessed by an individual or a set or sets of individuals e.g., by software developers, by IT personnel, by accounting, etc.
It will be appreciated that the filter, the underlying policies and the associated filter parameters are selected by and are the responsibility of the client entity. The filter provides a convenient tool for implementing and improving internal enforcement of such policies after the policies have been devised by the client entity with such consideration of the legal environment and other factors as deemed appropriate by the client entity. It is not intended that the filter be used as a substitute for full consideration of such issues or in lieu a full internal education and enforcement regime.
As noted above, a variety of parameters may be used to configure the filter. One such parameter is license type. In the context of open source projects, there are currently over 45 different recognized open source licenses. These include, for example, the General Public License (GPL), Lesser General Public License (LGPL), BSD, and Apache licenses. Open source licenses are not free of restrictions and obligations and different licenses involve different restrictions and obligations in this regard. While these restrictions and obligations are not always unambiguous, and the specific license terms should be consulted with due care, certain characterizations are possible. For example, certain licenses require that the source code of software, including proprietary software, distributed with the licensed open source software be made publicly available. Such licenses generally include obligations with respect to copyright notices and attributions with respect to copies of the software. Client entities will therefore generally need to carefully consider such licenses in relation to intended uses as part of a compliance program.
These licenses may serve as a parameter of the noted filter. That is, as noted above, license information is associated with each supported project in the illustrated system. These license designations may be selected or deselected by the client entity or system operator, e.g. using a filter graphical user interface, to enable or disable access to projects based on license or license type. Such configuration may be executed for specific users, user groups, intended uses, etc. Upon definition of such a filter or filters, the GUI is operative to inhibit or facilitate access to projects, generally in accordance with the selected filter parameters.
The filter is not necessarily limited to binary allow or disallow functionality. For example, three or more filter levels may be defined such as "red", "yellow" and "green" levels that may correspond levels of license restrictions or obligations. Thus, a particular client entity might decide, in its own discretion and in accordance with its own internal policy, that GPL licensed projects will be associated with the yellow filter level and BSD and Apache will be associated with the green filter level.
The GUI can then be configured to execute different filter functionality in connection with each filter level. For example, "red" projects may be excluded from the project identification panel 602 (
It is noted that such filter functionality may have considerable value apart from the illustrated system. For example, the filter may be used by a compliance officer, wholly independent of any stack assembly, installation and support functionality, to screen projects proposed for use by employees. Moreover, such a filter may be implemented in connection with an Internet gateway filter (e.g., otherwise used to limit internet access in accordance with company policy) to inhibit downloading of designated projects, for example, based on associated URLs. Other execution environments and uses of the filter are possible in accordance with the present invention.
The filters 1202 may be defined by a user by way of user interface of 1204. In this regard, filter identification information, filter parameters and the like may be entered by way of a template or a series of menus displayed on the user interface 1204. In this manner, the user can define a number of filter parameters such as user parameters 1208, use parameters 1210 and license parameters 1212. The user parameters 1208 may identify specific users or user groups, e.g., application developers, IT personnel, accounting, etc. The use parameters 1210 define the intended or allowable uses. Thus, for example, it may be desired to allow one set of projects for internal uses and a second (typically more limited) set of projects to be incorporated into products. The license parameters 1212 allow for controlling access or use of projects based on license associations. Thus, as noted above, certain licenses may be associated with a green filter level, others may associated with a yellow filter level and still others may be associated with red filter level. Appropriate filter rules may be defined for each of these filter levels.
Based on such filter configuration information, the filters 1202 selectively allow access to or use of projects 1206 by a user system 1214. For example, the filters 1202 may inhibit access to selective ones of the projects 1206, may prevent installation of selected ones of the projects 1206, or may provide certain warnings or require certain authorizations in connection with access to or use of individual ones of the projects 1206. Such filtering functionality may be executed in response to an identification of the user system 1214, a user I.D. entered via user system 1214 or otherwise, or an intended use entered by the user. The projects 1206 may be defined by a list of supported projects of a stack assembly, installation and support system as described above, a listing of projects defined by a compliance policy of a client entity, or projects that are identified on a case by case basis, for example, in connection with a request to download a project via the internet.
Once the filter is selected, filter levels may be defined (1306) for that filter. As noted above, a filter may be a binary in this regard or may include more than two filter levels. Thus, a binary filter may be operative to selectively allow or disallow access to specific projects by specific users for specific purposes. A filter with more than two filter levels may allow access, disallow access or allow access with certain restrictions or authorizations. Individual users or user groups may then be selected (1308) for association with the defined license. This allows for different levels of access to particular projects or project groups (e.g., defined by an associated license type) on an individual user basis or by a user group such as an applications development group.
The illustrated process 1300 involves associating (1310) projects with the defined filter levels. Again, this may be done on a project-by-project basis or by groups of projects, e.g., as grouped based on license type or another category such as noted above. It will be appreciated that other filter parameters may be defined in this regard such as, for example, expiration dates and copying or distribution parameters. Once all desired filter parameters have been defined, it is determined whether additional filters need to be defined (1314). If additional filters are to be defined, this process is repeated. Otherwise, the filter is activated (1316) for use in the desired project filter environment.
In use, the filter is operated to identify (1318) a user for a given filter function. The user may be identified based on user identification information entered by the user or based on the identity of the user machine or system. An intended use may also be identified (1320). The intended use may be entered by the user or may be inferred from a user group or other information. In this regard, it will be appreciated that the filter may be operative to a prompt user to enter such information as a gateway function prior to accessing a stack assembly, installation, de-installation and/or support functions. In addition, the subject project is identified (1322). Depending on the specific implementation, such identification may be responsive to a request, such as an installation request, entered by the user or may be performed independent of any user input, in the background or prior to running of the stack assembly, installation and/or support function. In this regard, the filter may operate to prevent display of a filtered project or to prevent selection of a filtered project independent of any input by user. Finally, the filter is operative to execute (1324) the filter function. Such execution may involve selectively allowing access to an identified set of projects, selectively disallowing access to or particular uses of an identified set of projects, or display of limitation information/require appropriate authorizations.
An exemplary installation process 1500 is shown in
In any event, once input information is thereby received, the illustrated process 1500 involves providing (1504) options for at least one project. Thus, for example, if the input information indicates that the stack of interest relates to web design, a variety of web design project options may be identified. For example, such identification may be accomplished by highlighting or otherwise drawing attention to such projects in a list of supported projects. Alternatively, the relevant projects may simply be listed with links to user interfaces that provide project information as described above. It will be appreciated that in some cases only one project may be available rather than a selection of options.
A selection can then be received (1506) for a first project of a stack under assembly. For example, one project from the noted listing of options may be selected via a graphical user interface. Upon such selection, the system determines (1508) dependency relationships for the project. Such dependency relationships may include, for example, projects on which the selected project depends as well as other projects that are used by the selected project. The system also determines (1510) a machine state. For example, this may involve identifying projects that are already installed on the user's machine. The project filter may also be applied (1512) at this point. Based on all this processing, the system constructs (1514) a display reflecting the project filter, machine state and dependency relationships. Thus, based on the project filter, the set of projects that is available for selection or installation may be limited. Based on machine state, previously installed projects may be identified as installed or may be unavailable for selection to be installed. The dependency relationships may be reflected in various graphical elements and text as described above.
From this display, this system can receive (1516) a project selection. For example, the user may select a project on which the first project depends. After such selection, the system can determine (1518) whether all dependencies are resolved. If the dependencies are not resolved, the user may be prompted to make further project selections. Otherwise, the system indicates (1520) that assembly is complete. Such an indication may be provided by way of a pop-up box or other active display element, or may simply be provided by way of the absence of any remaining dependencies (for example, the first project listing may switch from red to black).
It should be appreciated that the system of the present invention may be used simply to assemble a stack without actually effecting installation and that is an important aspect of the present invention. For example, a developer may use logic resident on the developer's system or access a website to execute the functionality described above in order to facilitate the process of, for example, addressing dependency relationship issues and filter functions associated with the client entity's licensing compliance program. The individual projects of that stack may then be obtained and installed independent of the system of the present invention. However, the installer of the present invention performs a variety of useful functions in connection with installation as will be described below.
B. Installation
It should be understood that the identification of a set of projects where the dependency relationships are internally satisfied does not mean that installation will be successful and free of problems. It is generally still necessary to resolve conflict issues, integrate projects (e.g., so that a given project is configured to point to the correct database), and to test the installed stack for proper installation and interoperation of the projects. In addition, a particular sequence may be required for installation. In accordance with the present invention, the GUI is operative to execute a variety of functionality in this regard.
One such function is performing pre-installation checks. For example, the GUI may identify and resolve port conflicts. As noted above, the project information associated with individual projects identifies the ports that are utilized by that project. This port information can be compared to identify and resolve conflicts. The system may further perform a check to verify that any files or other resources required by a project are available and to otherwise verify that all environmental requirements for a project are satisfied on the user machine or system.
Another function is control of the actual installation process. In this regard, the engine may obtain the project list for a stack, analyze the dependency relationships and any other necessary project information to determine a suitable sequence for installation and then execute installation in that sequence. Prior to executing this installation, the controller may execute logic to identify any resources that may be required in order to effect the desired installation.
Another function that is executed by the GUI in connection with installation is database integration. In this regard, individual projects may require a particular database and different projects may be associated with different databases. The GUI is operative to integrate the individual projects with the desired databases so that the projects point to the desired database.
After installation and database integration have been performed, tests may be performed on the installed stack to verify proper operation of the installed stack. This is accomplished by causing the stack to run on the user machine and then executing test procedures that are defined for particular projects, combinations of projects or overall stacks. For example, such tests may involve looking for particular files, checking ports, pinging a server, etc. It will be appreciated that the particular tests may be determined empirically or based on acquired expertise to provide a high likelihood of identifying common installation errors.
The installed stack may then be run with selected samples. That is, a tutorial specifically designed for the installed stack may be provided by the GUI. The user can run this tutorial to learn how to use the installed integrated stack. In connection with this stack, the installed stack executes certain samples. This operates to provide sample tests. That is, proper operation of the stack is verified in connection with executing the samples. These tests are similar to the tests described above but touch more layers of the software stack than the earlier tests and operate in an execution environment. If any errors are identified as a result of these tests, error messages may be provided together with information regarding resolution of the errors or instructions to repeat a portion of the installation process.
Similar issues are presented in connection with addressing project updates. In the context of operating stacks composed of projects from independent sources, e.g., multiple third parties or open source developers, it will be appreciated that updates generally will not be coordinated. That is, updates may occur at different times and may or may not have an impact on compatibility. The installation process described above can be implemented not only in connection with an initial installation, but also in connection with an update installation. That is, appropriate checks, installation sequencing, testing and the like can be designed and executed for a given update.
In this regard, update installations may be implemented automatically, upon manual retrieval of the update, or the user or an administrator of the client entity may be notified of the availability of an update. For example, a system operator may monitor the availability of updates for supported projects and download appropriate information to users or client entities. A user or client entity may then be advised of the availability of updates upon logging into a network, loading of a stack assembly, installation and support system, or selection of any affected project. Such updates may relate to updated project options and support materials as well as to updated software updates. The user or client entity may then select to install or not install the update. It will be appreciated that not all users/client entities may wish to install all updates in this regard.
It will thus be appreciated that the illustrated system provides a number of advantages with regard to the installation and update process and this installation process, considered independent of stack assembly or post-installation support, constitutes an important aspect of the present invention. That is, various elements of this installation process would provide advantages even in the context of a stack assembly developed independent of the present invention. However, even upon assembly and installation of a stack of multiple open source projects, certain post-installation support may be desired. The present invention provides significant advantages in this regard, as will be described below.
C. Post-Installation Support
Upon assembly and installation of an open source software stack, the stack is ready for use by the end user. However, a variety of post-installation functionality may be useful to allow optimal performance of the stack. The present invention provides a variety of functionality in this regard, as described below. Many users may benefit from a tutorial to educate the end user as to the proper use and capabilities of the installed stack. As noted above, tutorials are available for some open source software projects. However, such tutorials generally are not specifically adapted to provide instructions in the context of particular stacks that may be assembled. The present invention provides tutorials in the context of such stacks. The system described above supports a selected set of open source and other projects. These projects can be combined to define a large but finite set of software stacks. The knowledge base stores tutorial information for many or all of these stacks or subsets thereof. Upon installation of a stack, the associated tutorial or tutorials are made available to be run by the user.
Another important post-installation function relates to users manuals or other supporting documentation. As noted above, supporting documentation may be available in connection with individual open source projects. However, heretofore there has generally not been a convenient mechanism to obtain supporting documentation relating to a particular stack. This problem is addressed by the present invention by storing support documentation as structured XML documents. That is, chunks of supporting documentation text are associated with a tag system that links the text to particular projects, combinations of projects and overall stacks. For example, projects and stacks may be related by parent, child and other hierarchical tag structures. When a particular stack is installed, the relevant support documentation can be readily retrieved using the tag system to compile customized support documentation. Associated graphics may be assembled on a custom basis, also. The supporting documentation may be specifically provided for Linux, Windows, and/or other criteria specified by the user or indicated in the user machine information stored in the knowledge base and the appropriate documentation in this regard may be retrieved based on metadata (e.g., tag) associations.
It will be appreciated that the ability to provide custom tutorials and supporting documentation for an open source project, a combination of projects or an overall stack is an important advantage of the present invention that may be utilized independent of the stack assembly and installation tools noted above. For example, developers who have executed a custom stack installation independent of the tools noted above may wish to utilize the present invention to obtain supporting tutorials or documentation. For example, this may be accomplished by running logic resident on the developer's system or by accessing a website operative to provide such tutorials or documentation on a fee basis.
The combination of the flexibility of open source software and the ease of assembly and installation provided by the present invention yields a number of advantages that can not be readily realized in connection with proprietary systems or with open source software in the absence of the tools of the present invention. For example, a user may wish to try various stack options to determine which is optimal for a particular endeavor. For example, a user may wish to switch between different available database tools in connection with a particular open source software stack. In accordance with the present invention, a database switcher, or a switcher for other software components, may be provided. In this manner, the user can prompt the system to switch between one database and another. This system is operative as described above to integrate associated projects of a stack so that they point to the newly selected database. The user can then compare performance of the stack with one database tool (or other resource) and another database tool (or other resource). In this manner, optimization of performance for a particular endeavor can be conveniently achieved. It will be appreciated that proprietary systems generally do not accommodate comparison as between tools of competing providers. Open source systems theoretically allow for such comparisons but as a practical matter this cannot be performed due to the significant complexities associated with switching of tools and associated integration.
The system described above can be implemented a number of ways. For example, the associated logic may be disseminated in physical form to clients with updates provided periodically. Alternatively, the associated logic may be downloaded from an operator's website by a client entity and updates may be periodically downloaded in similar fashion. As a still further alternative, the system may be operated as a hosted application. In any event, use of the system may be licensed, for example, on a per user per year basis. In this regard, it may be desired to make information regarding such licenses available to the licensee while protecting the license information against unauthorized modification.
The private portion 1406 b may include additional information, such as information defining the license term, as to which access is to be limited. The private portion of 1406 b can be accessed by an authorized individual, for example, to update the expiration date or to add licensed seats. This is accomplished by entering license identification information via the user interface 1410 and requesting access to the restricted access fields. In response to such an access request, the user is prompted to enter a password or other security information. This password information is used to encrypt information entered into the private portion of 1406 or to decrypt information from the private portion 1406 b. In this manner, appropriate license information is made available while protecting restricted access information such as information fundamental to enforcement of the license terms.
While various embodiments of the present invention have been described in detail, it is apparent that further modifications and adaptations of the invention will occur to those skilled in the art. However, it is to be expressly understood that such modifications and adaptations are within the spirit and scope of the present invention.
Claims (28)
Priority Applications (4)
|Application Number
|Priority Date
|Filing Date
|US56631004 true
|US56631104 true
|US56630104 true
|US11118099 US7669199B2 (en)
|Installation of software stacks including uncoordinated projects
Applications Claiming Priority (1)
|Application Number
|Priority Date
|Filing Date
|US11118099 US7669199B2 (en)
|Installation of software stacks including uncoordinated projects
Publications (2)
|Publication Number
|Publication Date
|US20060036652A1 true US20060036652A1 (en)
|US7669199B2 true US7669199B2 (en)
Family Applications (4)
|Application Number
|Priority Date
|Filing Date
|US11118101 Active 2027-12-08 US7657866B2 (en)
|Providing documentation for assembling, installing, and supporting of software stacks
|US11118099 Active 2028-09-23 US7669199B2 (en)
|Installation of software stacks including uncoordinated projects
|US11118100 Active 2028-03-26 US7665086B2 (en)
|Software project filter
|US11118084 Active 2028-02-24 US7661089B2 (en)
|Tools for stacking uncoordinated software projects
Family Applications Before (1)
|Application Number
|Priority Date
|Filing Date
|US11118101 Active 2027-12-08 US7657866B2 (en)
|Providing documentation for assembling, installing, and supporting of software stacks
Family Applications After (2)
|Application Number
|Priority Date
|Filing Date
|US11118100 Active 2028-03-26 US7665086B2 (en)
|Software project filter
|US11118084 Active 2028-02-24 US7661089B2 (en)
|Tools for stacking uncoordinated software projects
Country Status (5)
|US7657866B2 (en)
|EP1763792A4 (en)
|JP2007535770A (en)
|CA2563786A1 (en)
|WO2005104798A3 (en)
Cited By (9)
|Publication number
|Priority date
|Publication date
|US20080189777A1 (en) *
|Arthur Deagon
|Application integration
|US20090144700A1 (en) *
|Huff David P
|Method and system for preparing software offerings having software application code and post-install configuration information
|US20100192119A1 (en) *
|Openlogic, Inc.
|Tools for software stacks
|US20100242033A1 (en) *
|Fritsch Brindusa L
|Method and System for Controlling Software Version Updates
|US20110154313A1 (en) *
|International Business Machines Corporation
|Updating A Firmware Package
|US8065671B1 (en) *
|United States Automobile Association (USAA)
|Systems and methods for product updates with provisioning of data items
|US20120079448A1 (en) *
|Openlogic, Inc.
|Stack or Project Extensibility and Certification for Staking Tool
|US8453112B1 (en) *
|Adobe Systems Incorporated
|Systems and methods for collaboratively creating applications using a multiple source file project that can be accessed and edited like a single file
|US8498982B1 (en)
|Openlogic, Inc.
|Noise reduction for content matching analysis results for protectable content
Families Citing this family (43)
|Publication number
|Priority date
|Publication date
|US5944530A (en) *
|Ho; Chi Fai
|Learning method and system that consider a student's concentration level
|US9792659B2 (en) *
|Iplearn, Llc
|Computer-aided methods and apparatus to access materials in a network environment
|US7804609B2 (en) *
|Desktop Standard Corporation
|Methods and systems to connect network printers
|US7496910B2 (en) *
|Desktopstandard Corporation
|System for policy-based management of software updates
|US7757220B2 (en) *
|Discovery Machine, Inc.
|Computer interchange of knowledge hierarchies
|US7590933B2 (en) *
|International Business Machines Corporation
|Method for displaying an annotated file
|US7552429B2 (en) *
|International Business Machines Corporation
|Integrated development environment for managing software licensing restrictions
|US8527504B1 (en) *
|At&T Intellectual Property Ii, L.P.
|Data network content filtering using categorized filtering parameters
|WO2007111684A3 (en) *
|Openlogic Inc
|Stack macros and project extensibility for project stacking and support system
|US20070244897A1 (en) *
|David Voskuil
|Methods and systems for change management for a group policy environment
|US8132188B2 (en) *
|International Business Machines Corporation
|Method and system for extension registry filtering
|US7971187B2 (en) *
|Microsoft Corporation
|Configurable software stack
|US20080184277A1 (en) *
|Microsoft Corporation
|Systems management policy validation, distribution and enactment
|US8065675B2 (en) *
|Yahoo! Inc.
|In-page installer
|US20080281904A1 (en) *
|Va Software Corporation
|Associating service listings with open source projects
|US8762984B2 (en) *
|Microsoft Corporation
|Content distribution infrastructure
|US8347279B2 (en) *
|International Business Machines Corporation
|Base application and stack application synchronization for software installation and maintenance
|JP5210328B2 (en) *
|Information processing system, program, and information processing method
|US8230397B2 (en) *
|International Business Machines Corporation
|Automated solution that detects configuration problems in an eclipse-based software application
|US8688845B2 (en) *
|Microsoft Corporation
|Remote computing session feature differentiation
|US8306946B2 (en) *
|Teradata Us, Inc.
|Deployment manager for master data management
|US8949788B2 (en) *
|Red Hat, Inc.
|Building and packaging software
|US20100175044A1 (en)
|Infosys Technologies Limited
|Method for creating software factory for developing j2ee applications
|US8412852B2 (en) *
|International Business Machines Corporation
|Guaranteeing a single copy of a shared assembly per process
|US20100211579A1 (en) *
|Robb Fujioka
|System and Method For Providing Expert Search In A Modular Computing System
|US20110209144A1 (en) *
|International Business Machines Corporation
|Application runtime expert for deployment of an application on multiple computer systems
|JP2011253417A (en) *
|Ricoh Co Ltd
|Information processor, program introduction support method, and program introduction support program
|US8832654B2 (en) *
|Unisys Corporation
|System and method for autonomous generation of software documentation
|US20120240096A1 (en) *
|White Source Ltd.
|Open source management system and method
|KR20120118353A (en) *
|Broadcast receiving apparatus and method of installing service
|US9170779B2 (en)
|International Business Machines Corporation
|Managing an application development environment
|US20130191249A1 (en) *
|International Business Machines Corporation
|Personalizing customer response
|US9152414B2 (en) *
|Tata Consultancy Services Limited
|System and method to select compatible open-source software and components for developed or conceptualized solution
|US20130326479A1 (en) *
|Qnx Software Systems Limited
|System and method for tracking compliance information for a build-system product
|US20140089898A1 (en) *
|International Business Machines Corporation
|Using multiple technical writers to produce a specified software documentation package
|US9274760B2 (en) *
|Sap Se
|Adaptive developer experience based on project types and process templates
|CN103488738A (en) *
|Method and system for automatically realizing JAVA object and data table SQL (structured query language) file
|US9740854B2 (en)
|Red Hat, Inc.
|System and method for code protection
|US9852138B2 (en)
|EMC IP Holding Company LLC
|Content fabric for a distributed file system
|US9442717B2 (en)
|Vmware, Inc.
|Techniques for automatically identifying input files used to generate output files in a software build process
|CN105260214B (en) *
|Intelligent patch push method and system used in complex systems erp
|US9841952B2 (en)
|Wipro Limited
|System and method for dynamically composing an integrated open source stack
|KR101727015B1 (en) *
|Apparatus and method for matching source code based on open source
Citations (24)
|Publication number
|Priority date
|Publication date
|US5553282A (en)
|Taligent, Inc.
|Software project history database and method of operation
|US5765152A (en)
|Trustees Of Dartmouth College
|System and method for managing copyrighted electronic media
|US5892900A (en)
|Intertrust Technologies Corp.
|Systems and methods for secure transaction management and electronic rights protection
|US20020035451A1 (en)
|Todd Rothermel
|Spatail data enabled engineering, construction, and operations computer-aided design (CAD) project system, method and computer program product
|US20020040469A1 (en)
|International Business Machines Corporation
|System and method for the configuration of software products
|US20020049738A1 (en) *
|Epstein Bruce A.
|Information collaboration and reliability assessment
|US20020174010A1 (en)
|Rice James L.
|System and method of permissive data flow and application transfer
|US20030009740A1 (en) *
|Esoftbank (Beijing) Software Systems Co., Ltd.
|Dual & parallel software development model
|US20030051226A1 (en) *
|Adam Zimmer
|System and method for multiple level architecture by use of abstract application notation
|US20030135842A1 (en)
|Jan-Erik Frey
|Software development tool for embedded computer systems
|US20030192029A1 (en)
|Hughes John M.
|System and method for software development
|US20040054566A1 (en)
|J'maev Jack Ivan
|Method and apparatus for event driven project management
|US20040073789A1 (en) *
|Powers John Stephenson
|Method for collaborative software licensing of electronically distributed computer programs
|US20040244008A1 (en) *
|Myung-Jae Lee
|Method of implementing Linux-based embedded system for mobile communication
|US20050086030A1 (en) *
|Zeidman Robert M.
|Software tool for synthesizing a real-time operating system
|US20050125358A1 (en) *
|Black Duck Software, Inc.
|Authenticating licenses for legally-protectable content based on license profiles and content identifiers
|US20050183021A1 (en) *
|Allen Joel E.
|Method for electronically packaging a user's personal computing environment on a computer or device, and mobilizing it for transfer over a network
|US7139811B2 (en) *
|Actona Technologies Ltd.
|Double-proxy remote data access system
|US7185344B2 (en) *
|Hewlett-Packard Development Company, L.P.
|Method of porting software
|US7246156B2 (en) *
|Industrial Defender, Inc.
|Method and computer program product for monitoring an industrial network
|US20080154965A1 (en) *
|Pedersen Palle M
|Methods and systems for managing software development
|US7418491B2 (en) *
|International Business Machines Corporation
|Architecture for a centralized management system
|US7458062B2 (en) *
|International Business Machines Corporation
|Framework to access a remote system from an integrated development environment
|US7552093B2 (en)
|Black Duck Software, Inc.
|Resolving license dependencies for aggregations of legally-protectable content
Family Cites Families (10)
|Publication number
|Priority date
|Publication date
|US5860012A (en) *
|Intel Corporation
|Installation of application software through a network from a source computer system on to a target computer system
|JPH10240502A (en) *
|Internatl Intelligent Inf:Kk
|System for transferring environment in information equipment
|US6895581B1 (en) *
|Microsoft Corporation
|Replaceable classes and virtual constructors for object-oriented programming languages
|US7233940B2 (en) *
|Answers Corporation
|System for processing at least partially structured data
|US7331034B2 (en) *
|Anderson Thomas G
|Distributed software development tool
|US8275716B2 (en) *
|Contentguard Holdings, Inc.
|Method and system for subscription digital rights management
|US7069547B2 (en) *
|International Business Machines Corporation
|Method, system, and program for utilizing impact analysis metadata of program statements in a development environment
|US7516331B2 (en) *
|International Business Machines Corporation
|Tamper-resistant trusted java virtual machine and method of using the same
|US7188118B2 (en) *
|Veritas Operating Corporation
|System and method for detecting file content similarity within a file system
|US7503031B2 (en) *
|International Business Machines Corporation
|Method of transforming an application into an on-demand service
Patent Citations (24)
|Publication number
|Priority date
|Publication date
|US5553282A (en)
|Taligent, Inc.
|Software project history database and method of operation
|US5765152A (en)
|Trustees Of Dartmouth College
|System and method for managing copyrighted electronic media
|US5892900A (en)
|Intertrust Technologies Corp.
|Systems and methods for secure transaction management and electronic rights protection
|US20020174010A1 (en)
|Rice James L.
|System and method of permissive data flow and application transfer
|US20020040469A1 (en)
|International Business Machines Corporation
|System and method for the configuration of software products
|US20020049738A1 (en) *
|Epstein Bruce A.
|Information collaboration and reliability assessment
|US20020035451A1 (en)
|Todd Rothermel
|Spatail data enabled engineering, construction, and operations computer-aided design (CAD) project system, method and computer program product
|US20030009740A1 (en) *
|Esoftbank (Beijing) Software Systems Co., Ltd.
|Dual & parallel software development model
|US20030051226A1 (en) *
|Adam Zimmer
|System and method for multiple level architecture by use of abstract application notation
|US7139811B2 (en) *
|Actona Technologies Ltd.
|Double-proxy remote data access system
|US20030135842A1 (en)
|Jan-Erik Frey
|Software development tool for embedded computer systems
|US20030192029A1 (en)
|Hughes John M.
|System and method for software development
|US20040054566A1 (en)
|J'maev Jack Ivan
|Method and apparatus for event driven project management
|US7458062B2 (en) *
|International Business Machines Corporation
|Framework to access a remote system from an integrated development environment
|US20040073789A1 (en) *
|Powers John Stephenson
|Method for collaborative software licensing of electronically distributed computer programs
|US7185344B2 (en) *
|Hewlett-Packard Development Company, L.P.
|Method of porting software
|US20040244008A1 (en) *
|Myung-Jae Lee
|Method of implementing Linux-based embedded system for mobile communication
|US7246156B2 (en) *
|Industrial Defender, Inc.
|Method and computer program product for monitoring an industrial network
|US20050086030A1 (en) *
|Zeidman Robert M.
|Software tool for synthesizing a real-time operating system
|US20050125358A1 (en) *
|Black Duck Software, Inc.
|Authenticating licenses for legally-protectable content based on license profiles and content identifiers
|US20080154965A1 (en) *
|Pedersen Palle M
|Methods and systems for managing software development
|US7552093B2 (en)
|Black Duck Software, Inc.
|Resolving license dependencies for aggregations of legally-protectable content
|US20050183021A1 (en) *
|Allen Joel E.
|Method for electronically packaging a user's personal computing environment on a computer or device, and mobilizing it for transfer over a network
|US7418491B2 (en) *
|International Business Machines Corporation
|Architecture for a centralized management system
Non-Patent Citations (11)
|Berglund, E., et al.; "Open-Source Documentation: In Search of User-Driven, Just-in-Time Writing" Oct. 21-24, 2001; pp. 132-141; ACM 1-58113-295-6/01/0010.
|Brian Fitzgerald et al., "Developing an Information Systems Infrastucture with Open Source Software", Jan. 2004, IEEE Software, pp. 50-55, http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=01259216. *
|Carla Freericks, "Open Source Standards on Software Process: A Practical Application", Apr. 2001, IEEE Communications Magzine, pp. 116-123, http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=917513&isnumber=19817. *
|Diomidis Spinellis et al., "How is open source affecting software development?", Jan. 2004, IEEE Software, pp. 28-33, http://opensou rce.mit.edu/papers/spinellisszyperski.pdf. *
|Feller, J., et al.,; "A Framework Analysis of the Open Source Development Paradigm"; 2000, pp. 58-69; International Conference on Information Systems.
|Frishberg et al., "Getting to Know You: Open Source Development Meets Usability", Apr. 20-25, 2002, CHI2002, pp. 932-933. *
|Jeffrey S. Norris, "Mission-Critical Development with Open Source Software: Lessons Learned", Jan. 2004, IEEE Software, pp. 42-49, http://ieeexplore.ieee.org/ielx5/52/28149/01259211.pdf?arnumber=1259211. *
|Jon Froehlich et al., "Unifying Artifacts and Activities in a Visual Tool for Distributed Software Development Teams", Proceedings of the 26the International Conference on Software Engineering, pp. 387-396, May 23-28, 2004, http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=1317461&isnumber=29176. *
|Scacchi, "Strategies for Developing and Deploying Free/Open Source Software", Apr. 26, 2004, Institute for Software Research, UC Irvine, pp. 1-9, "http://web.archive.org/web/20040426004059/http://www.ics.uci.edu/~wscacchi/Presentations/OSS-Strategies/Strategies-Developing-Deploying-FOSS.ppt". *
|Scacchi, "Strategies for Developing and Deploying Free/Open Source Software", Apr. 26, 2004, Institute for Software Research, UC Irvine, pp. 1-9, "http://web.archive.org/web/20040426004059/http://www.ics.uci.edu/˜wscacchi/Presentations/OSS-Strategies/Strategies-Developing-Deploying-FOSS.ppt". *
|SourceForge.Net, Apr. 23, 2003, pp. 1-3, http://web.archive.org/web/20030423010024/http://sourceforge.net/. *
Cited By (15)
|Publication number
|Priority date
|Publication date
|US20100192119A1 (en) *
|Openlogic, Inc.
|Tools for software stacks
|US8832647B2 (en)
|Openlogic, Inc.
|Tools for software stacks
|US8464240B2 (en) *
|Research In Motion Limited
|Method and system for controlling software version updates
|US20100242033A1 (en) *
|Fritsch Brindusa L
|Method and System for Controlling Software Version Updates
|US20120079448A1 (en) *
|Openlogic, Inc.
|Stack or Project Extensibility and Certification for Staking Tool
|US20080189777A1 (en) *
|Arthur Deagon
|Application integration
|US8925052B2 (en) *
|At&T Intellectual Property I, L.P.
|Application integration
|US8065671B1 (en) *
|United States Automobile Association (USAA)
|Systems and methods for product updates with provisioning of data items
|US8612966B2 (en) *
|Red Hat, Inc.
|Method and system for preparing software offerings having software application code and post-install configuration information
|US20090144700A1 (en) *
|Huff David P
|Method and system for preparing software offerings having software application code and post-install configuration information
|US8453112B1 (en) *
|Adobe Systems Incorporated
|Systems and methods for collaboratively creating applications using a multiple source file project that can be accessed and edited like a single file
|US20110154313A1 (en) *
|International Business Machines Corporation
|Updating A Firmware Package
|US9639347B2 (en) *
|International Business Machines Corporation
|Updating a firmware package
|US8498982B1 (en)
|Openlogic, Inc.
|Noise reduction for content matching analysis results for protectable content
|US9092487B1 (en)
|Openlogic, Inc.
|Analyzing content using abstractable interchangeable elements
Also Published As
|Publication number
|Publication date
|US20060031227A1 (en)
|EP1763792A4 (en)
|WO2005104798A2 (en)
|US7665086B2 (en)
|US20060036652A1 (en)
|US20060031226A1 (en)
|US20060036651A1 (en)
|EP1763792A2 (en)
|US7661089B2 (en)
|WO2005104798A3 (en)
|CA2563786A1 (en)
|JP2007535770A (en)
|US7657866B2 (en)
Similar Documents
|Publication Date
|US7823148B2 (en)
|System and method for performing patch installation via a graphical user interface
|US6282709B1 (en)
|Software update manager
|US8495611B2 (en)
|Systems and methods for private cloud computing
|US7516438B1 (en)
|Methods and apparatus for tracking problems using a problem tracking system
|US8296756B1 (en)
|Patch cycle master records management and server maintenance system
|US20080127175A1 (en)
|Packaging software products as single-file executables containing scripting logic
|US7797678B2 (en)
|Automatic generation of license package for solution components
|US20080201701A1 (en)
|Methods and systems for upgrading and installing application packages to an application platform
|US20060101051A1 (en)
|Electronic data capture and verification
|US6338149B1 (en)
|Change monitoring system for a computer system
|US20040205179A1 (en)
|Integrating design, deployment, and management phases for systems
|US6560776B1 (en)
|Software installation verification tool
|US20080209503A1 (en)
|Method and system for managing license objects to applications in an application platform
|US20030221190A1 (en)
|System and method for performing patch installation on multiple devices
|US20050080811A1 (en)
|Configuration management architecture
|US20040187103A1 (en)
|Software updating system and method
|US20020144256A1 (en)
|Method of deployment for concurrent execution of multiple versions of an integration model on an integration server
|US20110145789A1 (en)
|Application configuration deployment monitor
|US20110276892A1 (en)
|Resolving information in a multitenant database environment
|US20050160104A1 (en)
|System and method for generating and deploying a software application
|US7222106B2 (en)
|Mechanisms for handling software license agreements on multi-user system
|US7093247B2 (en)
|Installation of a data processing solution
|US20090037875A1 (en)
|Rapidly Assembling and Deploying Selected Software Solutions
|US20080244754A1 (en)
|System and Method for Software License Management for Concurrent License Management and Issuance
|US20050256805A1 (en)
|Real-time license enforcement system and method
Legal Events
Owner name: OPENLOGIC, INC., COLORADO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COPE, ROD;WEIDNER, ERIC;REEL/FRAME:017123/0329
Effective date: 20051014
Owner name: OPENLOGIC, INC.,COLORADO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COPE, ROD;WEIDNER, ERIC;REEL/FRAME:017123/0329
Effective date: 20051014
Owner name: SQUARE 1 BANK, NORTH CAROLINA
Free format text: SECURITY AGREEMENT;ASSIGNOR:OPENLOGIC, INC.;REEL/FRAME:023568/0980
Effective date: 20091119
Owner name: SQUARE 1 BANK,NORTH CAROLINA
Free format text: SECURITY AGREEMENT;ASSIGNOR:OPENLOGIC, INC.;REEL/FRAME:023568/0980
Effective date: 20091119
|Certificate of correction
|Fee payment
Year of fee payment: 4
Owner name: OPENLOGIC, INC., COLORADO
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SQUARE 1 BANK;REEL/FRAME:031098/0165
Effective date: 20130812
Owner name: WELLS FARGO CAPITAL FINANCE, LLC, MASSACHUSETTS
Free format text: SECURITY AGREEMENT;ASSIGNOR:OPENLOGIC, INC.;REEL/FRAME:031098/0836
Effective date: 20130812
Owner name: ROGUE WAVE SOFTWARE, INC., COLORADO
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO CAPITAL FINANCE, INC. (NOW KNOWN AS WELLS FARGO CAPITAL FINANCE, LLC (SUCCESSOR BY MERGER));REEL/FRAME:036663/0695
Effective date: 20150925
Owner name: OPENLOGIC, INC., COLORADO
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO CAPITAL FINANCE, INC. (NOW KNOWN AS WELLS FARGO CAPITAL FINANCE, LLC (SUCCESSOR BY MERGER));REEL/FRAME:036663/0695
Effective date: 20150925
Owner name: RWS, INC., COLORADO
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO CAPITAL FINANCE, INC. (NOW KNOWN AS WELLS FARGO CAPITAL FINANCE, LLC (SUCCESSOR BY MERGER));REEL/FRAME:036663/0695
Effective date: 20150925
Owner name: NEWSTAR FINANCIAL, INC., MASSACHUSETTS
Free format text: SECURITY INTEREST;ASSIGNORS:ROGUE WAVE SOFTWARE, INC.;ROGUE WAVE HOLDINGS, INC.;KLOCWORK INC.;AND OTHERS;REEL/FRAME:036683/0378
Effective date: 20150925
Owner name: ROGUE WAVE SOFTWARE, INC., COLORADO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:OPENLOGIC, INC.;REEL/FRAME:037977/0660
Effective date: 20160302
|Fee payment
Year of fee payment: 8


text: Hey guys, my Mac knowledge is not helping me at the moment. I need your help. My new PB arrived... my 15" was plagued with keyboard issues and this is the replacement machine. Everything seemed fine... maybe I have a curse or something. This is a brand new 17" PB with extra RAM. Please help me diagnose this... My display seems very... grainy. The white doesn't seem completely white. When I look at the screen from different angles, it looks like static, like on TV. It's much more subtle though, of course. It's like this over the whole screen. The hinge is good, except when it gets near the bottom, it really tightens up. This doesn't seem right... it feels like there's a lot of pressure when I hit the hinge button. Did they screw something up with the hinge cables?! I seem to have dead pixels everywhere. I can rub them out but they show up in different places, or just get fainter. It feels like I'm going insane! I downloaded Screen Query and just don't know what to do. The colors don't seem as solid as they should be. I would give you a dead pixel count but I can't seem to decide which are real and which are going away... god, it must be at least 5, sometimes in groups of two. God. The keyboard is nearly perfect... the bottom left hand arrow key makes a louder noise and I can see the keyboard move up and down a little. From where they installed my RAM, there's this very, very small piece of metal mesh it looks like, coming from the seam. I can fix this by opening the RAM area, I think. Should I call Apple immediately? My friend is coming over tomorrow to give a second opinion. I've waited soooooo long for this computer. Help, help, help.

subset: commoncrawl


text:
green onion ginger noodles & sesame garlic cucumbers
by gingeredpear
A quick light asian inspired meal.
Green onion ginger noodles with sesame garlic cucumbers
serves 2
adapted from momofukufor2
Sesame Garlic Cucumbers
1 (english) cucumber
1 tablespoon sesame oil
1 tablespoon light soy sauce
1 tablespoon finely minced garlic
2 teaspoons sugar
1 teaspoon salt
Chop the cucumber into bite size pieces or chop into large pieces and crush with hand. Toss with salt. Wait 20 minutes if you wish to drain the water. Toss with seasame oil, soy sauce, garlic and sugar.
Green Onion Ginger Noodles
1 bunch of green onions sliced
2 tablespoons of vegetable oil
1 tablespoon finely minced ginger
1 tablespoon finely minced shallot
1 tablespoon soy sauce
1 teaspoon sesame oil
salt to taste
rice noodles
Cook the noodles according to the instructions on the package. Heat the vegetable oil until the oil is shimmery but not smoking. Add the green onions, ginger and shallots. The oil with splatter, so be careful. Let it cool and add the soy sauce and sesame oil. Salt to taste if needed. Toss with noodles.


text:
My name is Jaelin Palmer. I was born with a class three underbite and crossbite, which basically means my bottom jaw was too far forward and to the side. At 15 years old and two sets of braces later, I was finally told I had stopped growing. They determine this by doing an x-ray of your hand to see if your bones are fused, which is important so your jaw bones don't move any more after surgery. I was thrilled! I had known this surgery was coming my whole life and I was eager to get it over with.
I met with a local surgeon and everything was set, so on December 24, 2009 I had reconstructive maxilla facial jaw surgery. (Did I mention my birthday is on Christmas? So I spent both Christmas AND my birthday in the hospital) The surgery went as planned (which means my bottom jaw was moved back and my top jaw was moved forward and up). Everything would have been perfect, except at every post-op I went to my pain level never got any lower. My surgeon wasn't concerned; said everyone healed at their own pace. Unfortunately for me, that day never came.
Normally, people go back to school around week two. I had my surgery during winter break, so I thought that would work out perfectly. But when week two came and went and I was still in pain, I had to go on independent study. After a month of basically homeschooling, I was at the date of what should have been full recovery. And my bones were healed, but my nerves weren't. I had awful aching, stabbing, burning pain 24 hours a day in my jaw and sinuses. So when the school district called and said I had used up all of my independent study time, my family and I were worried. However, I was a straight A freshman in high school. I wasn't about to risk what would basically be forced expulsion because of pain. So the next Monday I packed up and went to school. I remember people being really happy to see me, but I couldn't say much back. The pain was excruciating. I only made it to second period before I started sobbing in the middle of class. I was sent to the nurse's office and then went home. I never set foot on that high school campus again.
Now I had a real dilemma. I needed to finish the 9th grade after the semester had already started. My mom and I learned quickly that all of the free online schools required you to sign up before the current semester started. So we went with the only option we had: I finished the last half of the 9th grade at an online private school. My dad is a teacher and we really couldn't afford it, but we had no other option so we put it on a credit card. I didn't like homeschooling though. I had been home schooled on and off my entire childhood and as the math got harder, I needed a real teacher. Luckily, there was a community college 15 minutes from our house. I had always been mature for my age and had never liked the public school system, so my mom and I went about figuring out how to get me graduated from high school. Our answer was found in the CHSPE (California High School Proficiency Exam), which gave me an actual diploma from the state of California, not a GED. I studied for months for that test because it's much more difficult than the CAHSEE. The studying paid off and I passed! I was thrilled to get my high school diploma in the mail. I started community college the next semester where I could take one class at a time, and then go home.
Fast forward five years and I have on a third set of braces, am in a lot worse pain than I was in all those years ago, and have gained about 100 pounds from medication and lack of exercise. At this point I've taken the semester off college and spend all day and night in a reclining chair because it's too much pressure on my face to lay flat on a bed. I grew another half-inch since that first surgery and my bottom jaw took on a rare growth pattern (less than 1% of the population has it) and is now growing down and out. I had seen every doctor under the sun and a pain doctor monthly for an incredible amount of medication that included way too many narcotics for my liking. We finally decided we had no other option but to go in and re-do the surgery, except this time, instead of using metal plates and banding my mouth shut for a week, we'd do it the old-fashioned way. Because of a possible allergic reaction to the metal, we decided to take it all out and wire my teeth shut for 6 weeks to let it heal just like they did back when my mom had the surgery in the '80s. To make sure nothing went wrong, we had the head of the department of Maxilla Facial Surgery at UCLA perform it.
I had that surgery November 5, 2014, and am recovering now. Let me tell you, the wired shut thing sucks. However, I feel better now than I ever have in the past five years. I have already started decreasing my medication, have more energy, and am in less pain. Now all I can do is deal with my annoying closed jaw and pray to whatever God is out there that it's easier from here on out.
2 comments on My Story
I just wanted to say that no matter what you think, you are beautiful. Those eyes have more depth then an Ansel Adams photo. Your beauty is that of Monet's famous painting " The valley of the Nervia."
Just thought I would let you know that you make this guys day.