COMPUTER INTERFACE MIDDLEWARE SOFTWARE

Brand	Owner (click to sort)	Address	Description
SEAD ENGINE	KABUSHIKI KAISHA SQUARE ENIX HOLDINGS (ALSO TRADING AS SQUARE ENIX HOLDINGS CO., LTD.)	6-27-30 Shinjuku, Shinjuku-ku Tokyo Japan	Computer interface and middleware software for applications integration and cross-platform interoperability of disparate software applications and computer systems; program-development environment software;ENGINE;
VOLUTE	Volute Holdings Corporation	166 Valley Street, Suite 219 Providence RI 02909	COMPUTER INTERFACE AND MIDDLEWARE SOFTWARE FOR APPLICATION INTEROPERABILITY OF DISPARATE SOFTWARE APPLICATIONS AND COMPUTER SYSTEMS AND THAT ADAPTS TO THE NEEDS, CAPABILITIES AND DESIRES OF THE PERSON USING THE COMPUTER SOFTWARE;
WHITE ENGINE	KABUSHIKI KAISHA SQUARE ENIX HOLDINGS (ALSO TRADING AS SQUARE ENIX HOLDINGS CO., LTD.)	6-27-30 Shinjuku, Shinjuku-ku Tokyo Japan	Computer interface and middleware software for applications integration and cross-platform interoperability of disparate software applications and computer systems; program-development environment software; computer software for use in the development of computer games and/or video games; computer software to ease the development of computer games and/or video games comprising multiple middleware programs featuring graphics engine, physics system, motion control, cinematics, sound, special effect rendering, artificial intelligence, and networking;ENGINE;
	Where the owner name is not linked, that owner no longer owns the brand

Technical Examples

Methods and systems are disclosed for a user to access an intranet from within a systems interface to back-end legacy systems. A user logs a computer into a systems interface which permits access to back-end legacy systems. The computer accesses the systems interface over a wireline or a wireless communications network. Preferably, the systems interface is located on at least a first network address. Preferably, the systems interface includes a first server with middleware for managing the protocol interface, the first server being located at the first network address. Preferably, the systems interface includes a second server for receiving requests and generating legacy transactions. When the user is logged on, a client application for the systems interface is running on the computer. Next, the user launches a shared network software application, preferably a browser. The user may or may not minimize the client application, but the user remains logged-on. As the browser launches and seeks out an intranet site at a separate network address, the systems interface receives a message from the computer or otherwise detects that the computer is seeking access to the intranet. In response to detecting that the computer seeks access to the internet, the systems interface determines whether intranet access is to be granted. If access is granted, the systems interface routes communications from the computer to the separate network address. Preferably, the first server routes communications from the computer from the first network address to the separate network address.