Modular Software System for Use in an Integration Software Technology and Method of Use

A method of utilizing a modular software system within an integration software technology by executing computer-executable instructions stored on a non-transitory computer-readable medium, comprises the steps of:

• providing a plurality of modules, wherein the plurality of modules comprise a log miner module, a searchable information database module, an integration scheduler module, a fault handler module, and an integration incident manager module;
• providing an integration software technology, wherein the integration technology is a collection of software and hardware applications implemented as middleware in order to manage or coalesce a plurality of hardware and software subsystems;
• providing an integrated system, wherein the integrated system is a system comprised of hardware and software subsystem managed or coalesced by the integration software technology;
• providing a displayable data table;
• providing an agent installed on network accessible drives of the plurality of hardware subsystems;
• providing an inbound directory, a database, and a processor installed on a main network accessible drive;
• providing the SOP library comprising a technology selection SOP, a Technology Training SOP, a Technology Product Evaluation SOP, a proof of concept (POC) Environment SOP (Platform and Key Interfaces Plan, Design, Build), a proof of concept (POC) Environment Evaluation SOP, a Project Planning SOP, an Infrastructure Platform Design SOP, an Application Design SOP, an Interface Consolidation and Design SOP, an Applications per Platform Consolidation SOP, an Interfaces per Platform Consolidation SOP, an Infrastructure build SOP, an Interfaces development SOP, a Backup and Recovery SOP, a Change Management Process SOP, a Deployment Automation SOP, a Production Support Process SOP, a Production Release SOP, a Support Process 5 Automation SOP, and a Training SOP;
• providing the interface library comprising an Integration Interface to Email integration errors, an Interface to integrate queue, an Interface to integrate file transfer, an Interface to integrate databases, an Interfaces to Integrate EDI, an Interface to integrate B2B clients, an Interface to integrate ERP Applications, an Interface to integrate Legacy Applications, an Interface to ping remote hosts, an Interface to lookup configuration values, and an Interface to purge files and data;
• providing the documentation library comprising Articles on Integration Technologies, Documents on Integration Products, Documents on Best Practices, Documents on Development Techniques, Audio and Video files on Subject Matters, Installation Guides, List of Tools and Software, Sample Code, Sample Architecture Designs, Sample Project Plans, and Templates;
• providing a quick access page comprising links to the SOP library, the interface library, and the documentation library;
• providing a plurality of user defined application faults each comprising event identifiers;
• providing a production related incident ticket comprising a production specific integration incident and an incident resolution;
• providing a plurality of user defined scheduled process each comprising an event condition and a scheduled process;
• installing the plurality of modules on the integrated system;
• activating the log miner module;
• receiving a plurality of log files in the inbound directory, wherein the plurality of log files are transmitted by the agent on the hardware subsystems;
• reading each log file received in the inbound directory, wherein the processor reads each log file for identifiers;
• comparing the identifiers of a log file received in the inbound directory to known identifiers associated with log file types in the database;
• extracting a plurality of raw data values from the log file,
• creating a data table entry in the displayable data table, wherein the processor creates the data table entry based on a data table entry format associated with the known log file type,
• converting the plurality of raw data values using a known conversion process, wherein the processor uses the known conversion process associated with the known log file type,
• allocating converted data values to the data table entry,
• if the processor detects known identifiers in the log file associated with a log file type in the database;
• extracting a plurality of raw data values from the log file,
• analyzing the plurality of raw data values extracted from the log file, wherein the processor compares raw data values extracted from the log file to raw data value types associated with a known log file type,
• determining a closet matching log file type,
• creating a new data table entry based on the closest matching log file type,
• implementing the conversion process of the closest matching log file type,
• allocating converted data values to the data table entry,
• prompting a verification of a new data table entry format on the displayable data table,
• creating a new log file type in the database containing a new conversion process, a new data table entry format, and a new identifier or means of identification,
• if the processor does not detect identifiers or detects identifiers in the log file not associated with a known log file type in the database;
• activating the searchable information database module;
• displaying the quick access page;
• receiving an input on the quick access page;
• initiating a SOP selection process,
• if the searchable information database module receives a search query that relates to the selection of an SOP;
• redirecting to the sop library,
• if the searchable information database module receives a link selection for the SOP library or a query for a specific SOP;
• redirecting to the interface library,
• if the searchable information database module receives a link selection for the interface library or a query for a specific interface;
• redirecting to the documentation library,
• if the searchable information database module receives a link selection for the documentation library or a query for a particular piece of documentation;
• initiating the fault handler module;
• monitoring integration technology interactions;
• detecting an event identifier in an integration technology interaction;
• notifying a user of an application fault;
• initiating the integration scheduler module;
• monitoring for the even condition;
• detecting the event condition;
• initiating the scheduled process;
• initiating the incident manager module;
• monitoring the production related incident ticket;
• monitoring a plurality of production related incident tickets with matching production specific integration incidents;
• detecting an incident resolution;
• and
• redirecting to resolution information on a searchable information database.

A method of utilizing a modular software system within an integration software technology by executing computer-executable instructions stored on a non-transitory computer-readable medium, comprises the steps of:

• providing a plurality of modules, wherein the plurality of modules comprise a log miner module, a searchable information database module, an integration scheduler module, a fault handler module, and an integration incident manager module;
• providing an integration software technology, wherein the integration technology is a collection of software and hardware applications implemented as middleware in order to manage or coalesce a plurality of hardware and software subsystems;
• providing an integrated system, wherein the integrated system is a system comprised of hardware and software subsystem managed or coalesced by the integration software technology;
• providing a displayable data table;
• providing an agent installed on network accessible drives of the plurality of hardware subsystems;
• providing an inbound directory, a database, and a processor installed on a main network accessible drive;
• providing the SOP library comprising a technology selection SOP, a Technology Training SOP, a Technology Product Evaluation SOP, a proof of concept (POC) Environment SOP (Platform and Key Interfaces Plan, Design, Build), a proof of concept (POC) Environment Evaluation SOP, a Project Planning SOP, an Infrastructure Platform Design SOP, an Application Design SOP, an Interface Consolidation and Design SOP, an Applications per Platform Consolidation SOP, an Interfaces per Platform Consolidation SOP, an Infrastructure build SOP, an Interfaces development SOP, a Backup and Recovery SOP, a Change Management Process SOP, a Deployment Automation SOP, a Production Support Process SOP, a Production Release SOP, a Support Process 5 Automation SOP, and a Training SOP;
• providing the interface library comprising an Integration Interface to Email integration errors, an Interface to integrate queue, an Interface to integrate file transfer, an Interface to integrate databases, an Interfaces to Integrate EDI, an Interface to integrate B2B clients, an Interface to integrate ERP Applications, an Interface to integrate Legacy Applications, an Interface to ping remote hosts, an Interface to lookup configuration values, and an Interface to purge files and data;
• providing the documentation library comprising Articles on Integration Technologies, Documents on Integration Products, Documents on Best Practices, Documents on Development Techniques, Audio and Video files on Subject Matters, Installation Guides, List of Tools and Software, Sample Code, Sample Architecture Designs, Sample Project Plans, and Templates;
• providing a quick access page comprising links to the SOP library, the interface library, and the documentation library;
• providing a plurality of user defined application faults each comprising event identifiers;
• providing a production related incident ticket comprising a production specific integration incident and an incident resolution;
• providing the plurality of user defined application faults each comprising an event identifier and an email alert protocol;
• providing a plurality of user defined scheduled process each comprising an event condition and a scheduled process;
• providing a production related incident ticket comprising a production specific integration incident and an incident resolution;
• installing the plurality of modules on the integrated system;
• activating the log miner module;
• receiving a plurality of log files in the inbound directory, wherein the plurality of log files are transmitted by the agent on the hardware subsystems;
• reading each log file received in the inbound directory, wherein the processor reads each log file for identifiers;
• comparing the identifiers of a log file received in the inbound directory to known identifiers associated with log file types in the database;
• extracting a plurality of raw data values from the log file,
• creating a data table entry in the displayable data table, wherein the processor creates the data table entry based on a data table entry format associated with the known log file type,
• allocating converted data values to the data table entry,
• converting the plurality of raw data values using a known conversion process, wherein the processor uses the known conversion process associated with the known log file type,
• if the processor detects known identifiers in the log file associated with a log file type in the database;
• extracting a plurality of raw data values from the log file,
• analyzing the plurality of raw data values extracted from the log file, wherein the processor compares raw data values extracted from the log file to raw data value types associated with a known log file type;
• determining a closet matching log file type;
• creating a new data table entry based on the closest matching log file type,
• implementing the conversion process of the closest matching log file type,
• allocating converted data values to the data table entry,
• prompting a verification of a new data table entry format on the displayable data table,
• creating a new log file type in the database containing a new conversion process, a new data table entry format, and a new identifier or means of identification,
• if the processor does not detect identifiers or detects identifiers in the log file not associated with a known log file type in the database,
• activating the searchable information database module,
• displaying the quick access page,
• receiving an input on the quick access page,
• prompting user to identify a type of integration implementation project,
• initiating the technology selection SOP,
• initiating the technology training SOP,
• initiating the technology product evaluation SOP,
• initiating the POC environment SOP,
• if the type of integration implementation project is selected as a new implementation, or as a technology upgrade,
• initiating the POC environment SOP,
• if the type of integration implementation project is not selected as a new implementation or as a technology upgrade,
• prompting the user to evaluate the success of an implemented proof of concept POC integration environment,
• initiating an environment SOP, where the environment SOPs are the Project Planning SOP, the Infrastructure Platform Design SOP, the Application Design SOP, the Interface Consolidation and Design SOP, the Applications per Platform Consolidation SOP, the Interfaces per Platform Consolidation SOP, the Infrastructure build SOP, the Interfaces development SOP, and the Backup and Recovery SOP,
• initiating the production release SOPs, where the production release SOPs are the Change Management Process SOP, the Deployment Automation SOP, and the Production Support Process SOP,
• initiating a support SOP,
• initiating a training SOP,
• if the implemented integration technology is evaluated as being successful in the POC integration environment,
• initiating the technology selection SOP,
• initiating the technology training SOP,
• initiating the technology product evaluation SOP,
• initiating the POC environment SOP,
• if the implemented integration technology is evaluated as being unsuccessful in the POC integration environment,
• if the searchable information database module receives a search query that relates to the selection of an SOP;
• redirecting to the sop library,
• if the searchable information database module receives a link selection for the SOP library or a query for a specific SOP;
• redirecting to the interface library,
• if the searchable information database module receives a link selection for the interface library or a query for a specific interface;
• redirecting to the documentation library,
• if the searchable information database module receives a link selection for the documentation library or a query for a particular piece of documentation;
• initiating the fault handler module;
• monitoring integration technology interactions;
• detecting an event identifier in an integration technology interaction;
• notifying a user of an application fault through an email alert according to the email alert protocol;
• initiating the integration scheduler module;
• monitoring for the even condition;
• detecting the event condition;
• initiating the scheduled process;
• initiating the incident manager module;
• monitoring the production related incident ticket;
• monitoring a plurality of production related incident tickets with matching production specific integration incidents;
• detecting an incident resolution;
• and
• redirecting to resolution information on a searchable information database.