<div>
<div class="content wysiwyg-content">
This is a question for someone with a lot of experience bringing application servers online or for a network engineer who worked intimately to support someone who did.<br />
<br />
If I were going to roll out a new suite of applications (JD Edwards EnterpriseOne , for example) , what considerations would I have to make with regard to network architecture and connectivity? <br />
<br />
For example, creating a dual-homed server architecture for NIC/switch-port redundancy. Or creating a management vlan, separate from the data vlan, and using a separate NIC for that. Or perhaps placing an application server that has to constantly sieze information from an SQL database server on the same vlan/subnet to avoid layer 3 switching (routing) between hosts on different vlans. Or maybe placing the production servers and dev servers in separate vlans, etc.<br />
<br />
The reason I am asking is that I am going to have to help an applications support group make network architecture decisions when they roll out the new suite of applications and associated servers.<br />

</div>
</div>


This is a question for someone with a lot of experience bringing application servers online or for a network engineer who worked intimately to support someone who did.

If I were going to roll out a new suite of applications (JD Edwards EnterpriseOne , for example) , what considerations would I have to make with regard to network architecture and connectivity? 

For example, creating a dual-homed server architecture for NIC/switch-port redundancy. Or creating a management vlan, separate from the data vlan, and using a separate NIC for that. Or perhaps placing an application server that has to constantly sieze information from an SQL database server on the same vlan/subnet to avoid layer 3 switching (routing) between hosts on different vlans. Or maybe placing the production servers and dev servers in separate vlans, etc.

The reason I am asking is that I am going to have to help an applications support group make network architecture decisions when they roll out the new suite of applications and associated servers.


Application Servers

An application server is a software framework that provides both facilities to create applications and a server environment to run them. Most application server frameworks contain a comprehensive service layer model, acting as a set of components accessible to the software developer through an API defined by the platform itself. For Web applications, these components are usually performed in the same running environment as their web server(s), and their main job is to support the construction of dynamic pages. However, many application servers target much more than just Web page generation: they implement services like clustering, fail-over, and load-balancing.

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

Microsoft applications include a variety of software programs, including development and digital authoring programs (Expression and Media Center), educational programs, Internet software, including Essentials, Skype and the Live family, anti-virus, productivity applications and suites like Office, Excel, Word, Outlook, Access and PowerPoint, video games and server applications such as Exchange, SharePoint, IIS and Virtual Server.