Abstract: A classification mechanism within the source code management system for customizing malicious code searches. This classification mechanism is used to limit the number of searches that are performed on incoming source code, as some malicious code searches may only need to be performed on particular modules, classes, components, etc. of the software product. When a library system is being set up to receive new source code, security classifications are created for the source code. Upon receiving the source code from a software developer, each component in the source code is associated to a security classification. A virus check is then performed on the components in the source code based on the associated security classifications. In this manner, only certain components may need to be checked for certain virus patterns, and other components may be checked for other virus patterns.

Abstract: A method, computer program product, and data processing system for installing and registering software components as part of a unified solution, rather than simply as individual software components, are disclosed. According to a preferred embodiment, an installer supplies specific registration information as part of its overall installation process. This registration information overrides that used by the native component install technology to register the solution/component, as appropriate. In a preferred embodiment, the standard registration information provided by each software component's individual installer program is removed by an installation wrapper script and replaced by registration information that pertains to the installed solution as a whole. This registration scheme may just be characterized as a form of “late binding” of registration information.

Abstract: A system and method for enhancing source code management by using existing virus detection methods in a library management system to detect potentially malicious code. With the mechanism of the present invention, malicious code that is introduced into a software product may be detected before the code is able to damage stored data and other software by preventing a product build with the destructive code. When source code is received at a code management library system from a set of software developers in a collaborative development environment, the source code is moved into a staging area. A determination is then made as to whether malicious code exists in the source code. If malicious code exists, the library system removes the source code from the software product build and notifies the system administrator of the presence of malicious code.

Abstract: A repair mechanism within a code management library system for repairing build code that is infected with malicious code. When a virus pattern is detected in a component of a source code, other components in the source code containing dependencies upon the first component are identified. This identification may be based on rules defined from relationships between the infected component and the other components in the source code. The component and the other components that are identified as having dependencies upon the infected component are retracted from the software product build. The infected component and the other identified components are then replaced with a previous archive of the code build. The software product build of the source code may then be performed.

Abstract: A system and method for user role based product license generation is presented. An installer uses a license generator to analyze role keys that it receives from the installer and associates a user role to the role key, such as “developer” or “production.” The license generator identifies the user role and retrieves a corresponding license template, such as a “developer” template. The installer provides user information to the license generator, and the license generator customizes the license template using the user information. In addition, the license generator may inhibit particular software features based upon the identified user role.

Abstract: A system and method for customized bundled license generation is presented. A license generator uses license sections as building blocks in order to dynamically generate a customized bundled license agreement for use with a bundled software package offering. Each license section has attributes, which are used to select the license sections to include in a customized bundled license. The license generator receives installation parameters from an installer, and matches the installation parameters with the section attributes. Once the license generator matches one or more of the section parameters with one or more section attributes, the license generator retrieves corresponding license sections and generates a customized bundled license. In addition, the license generator may receive user information, such as a user name and department number, which the license generator includes in the customized bundled license.

Abstract: A computer system and associated method to distribute an electronic communication object. The electronic communication object comprises a main communication and a first sub-communication object. The first sub-communication object is embedded within a main communication object. The main communication object comprises a first set of attributes and a first addressee. The first sub-communication object comprises a second set of attributes and a second addressee. A hierarchal relationship exists between the main communication object and the first sub-communication object such that the first sub-communication object inherits one or more of the first set of attributes from the main communication object if said one or more of the second set of attributes is not specified in the first sub-communication object. The main communication object and a first outline of the first sub-communication object is sent to the first addressee. The first sub-communication object is sent to the second addressee.

Abstract: Techniques are disclosed for enabling a validating parser to interpret a schema, where that schema may have been extended to multiple levels, and to perform the validation of a structured document according to the extended schema while still allowing a consumer application to request objects or events that are cast at some different level of the schema (including the base schema). Validating the source document according to an extended (i.e., more specific) schema enables improved detection of syntax errors. At the same time, casting objects and events from the parsed document to a level requested by the consumer application allows the consumer to receive only those objects or events for which it is adapted, without requiring the consumer application to include extra code to deal with objects or events it does not recognize in the parser's output. Preferably, the parser simply discards those objects or events which this consumer is not interested in receiving.