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.

Our company would like to setup open source OT management system that allows us to do following:

1. When employ wants to do OT, Start time must be submitted first and then it will only be reflected to system once administrator approved.
2. Later when employee finish job, he or she can set the end time, and there should be something that allows emplyee to upload service report that contains start and end time signed by our customers.
3. After setting end time, it should show total OT - hours and we should be able to generate monthly OT for each employee.

Plz advise something that is opensource or even if need to pay, it should be something not very expensive.

Indeed there is no such file, whereas there is a file /Users/barrygbrunning/eclipse/java-oxygen/Eclipse.app/Contents/Info.plist. At the install log errors referenced path /Users/barrygbrunning/eclipse/java-oxygen/Eclipse.app/Contents/Eclipse/ are located folders: configuration, droppins, features, jre, plugins, readme and the eclipse.ini file, but no info.plist.

The implied "Deferring..." action seems to have not happened. Any suggestions as to what I might do to recover the situation? What should have happened to an info.plist somewhere? How might I get the CFB perspective to manifest in Eclipse?

I am in the process of getting an outdated server upgraded to a supported OS. Running VMWare 5.5 and we get getting a system off a Virtual Server 2003 x86, and upgrading it to the only available system possible a virtual Server 2008 x86. The original server is an application and file server. It has 3 IP addresses assigned to a single nick and the DNS has 2 of those IP's assigned to static FQDN's.
Here is where things get unusual...

When the original server is the one bound to the domain I can ping it from all of my systems. When the new computer is bound to the domain it will not respond to ping from only certain subdomains (inbound ICMP v4 & v6 are enabled for file and print sharing.. so it isn't the firewall).

The 2nd and 3rd IP's do not respond to any type of ping even though they show they are connected to the network. I have even tried changing the configuration by removing the 2nd and 3rd IP's from the one nic and giving them their own individual nic cards to see if they might respond from there. Again no such luck.

I am going crazy trying to get this to work properly but I can't seem to find a way to get the nic's to talk correctly, nor can I get them to respond to all of the subdomains that the original server had no issues responding to.

I am hoping that someone may have seen something like this before. I realize that an in place upgrade doesn't always resolve all issues but I've never seen something like this in any previous attempts.
Thank you in …

we have direct printing with two application servers running IIS connecting to SQL DB . we have upgraded two application servers 3 months back and one application is not responding for direct printing .
our application vendor is asking us to check with the network team to resolve the issue . but it seems to be nothing wrong with the network level .

Q1 - How can I confirm the network level issue is clear - Eg by ping the client to server or ?
Q2 - Patch level , there are some changes in the patch level , but our vendor has confirm before the patch upgrade ,there is nor issue with the latest patch update .

Our Printing is configured as below
Client end - connecting the receipt printer to client PC - Host name - C1
Application server side - Direct printer is mapping billingPrinterC1 and billingPrinter is the prefix for the printer profile name for billing Dep.

billingPrinterC1 IPaddress

how can I rectify the direct printing issue on the not responding server . Direct printing still using for big applications ? we are having so much of issues with this architecture . please comment on this
I will share some testing result later

Cloud based application having issues with ldaps bind to our Domain Controller in DMZ.
The application vendor is seeing the follwoing log entries on their side:
[7:Public User][1024:application notice][R] (:) - Unable to bind to the LDAP server.

They are saying that the reason packet analyser highlights the [RST, ACT] packets in red is because after the connection closure by Cloud Application server (source) [FIN, ACK] , server is expecting a final [FIN, ACK] from Domain Controller (destination) but [RST, ACK] arrives instead. And thus they believe that it could be a issue with the Domain Controller.

We are looking to replace our current SAP systems with a new one. We were thinking of pointing using a friendly URL to point to the database such as prodcutionSQLDB.ACME.com and productionOracleDB.ACME.com instead of using DB Server name.

This way our application servers just get this FQDN to point to the database. THis would simplify our DR planning and future migrations.

The question is, does SAP require certificates or something similar where the application servers would not be able to communicate with the DB (SQL or Oracle). My understanding is SQL and Oracle use username\pass to authenticate, or does SAP rely on certificates to communicate with the DB servers?

I am trying to Import Car file created on WAS 6.1 into WAS 8.5.Ware getting below error.

*sys-package-mgr*: processing new jar, 'C:\Program Files (x86)\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime\ejbdeploy.jar'
*sys-package-mgr*: processing new jar, 'C:\Program Files (x86)\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime\ejbmapvalidate.jar'
com.ibm.wsspi.management.bla.op.OpExecutionException: Exception create contexts for asset:java.util.NoSuchElementException
at com.ibm.ws.management.bla.model.BLAOutImpl.findContext(BLAOutImpl.java:201)
at com.ibm.ws.management.bla.model.BLAOutFactoryImpl.getBLAOut(BLAOutFactoryImpl.java:41)
at com.ibm.ws.management.bla.steps.StepSaveBLA.getBLAOut(StepSaveBLA.java:263)
at com.ibm.ws.management.bla.steps.StepSaveBLA.execute(StepSaveBLA.java:215)
at com.ibm.wsspi.management.bla.op.compound.Phase.execute(Phase.java:151)
at com.ibm.wsspi.management.bla.op.compound.CompoundOperation._doPhaseExecute(CompoundOperation.java:102)
at com.ibm.wsspi.management.bla.op.compound.CompoundOperation.doExecute(CompoundOperation.java:85)
at com.ibm.wsspi.management.bla.op.Operation.execute(Operation.java:158)
at com.ibm.wsspi.management.bla.op.compound.CompoundOperation.execute(CompoundOperation.java:68)
at com.ibm.ws.management.bla.j2ee.ext.tasks.ConfigBLATask._runBLAOp(ConfigBLATask.java:303)
at …

The above issue I fixed by replacing the jar - jsf-impl-2.2.13.SP1.jar that comes with wildfly-10.1.Final modules with jsf-impl-2.2.8-jbossorg-1.jar that comes with wildfly8.2 modules and got the application deployed successfully.

We're running a XA 6.5 environment, and I've just built a series of new VMs and added them to the existing farm.

I am able to see the new servers within the farm and have verified that the application servers are all same version (6.5), same OS Win2k8R2, same Hotfix XA650W2K8R2X64R03. However the XML brokers (we have 3) are R04. My first guess would be to verify that all the Hotfix packs were the same, however, when I try and launch applications from the old farm (R03), everything works normally with the XML brokers (R04). I don't want to convert the XML brokers (R04) to a different hotfix pack (R03) and break the old production environment. So why can't the new servers work with the XML brokers?

I have verified that the new application servers have R03 just the same as the old farm, however I am unable to publish applications from any of the new servers.

When I attempt to launch an application from one of the new servers, I see the following error messages in the WI:

1. An error occurred while attempting to read information from the Citrix servers: An existing connection was forcibly closed by the remote host. This message was reported from the XML Service at address http://SERVER1.domain:8080/scripts/wpnbr.dll [com.citrix.xml.NFuseProtocol.RequestAddress]. The specified Citrix XML Service could not be contacted and has been temporarily removed from the list of active services. [Unique Log ID: 1b1f909e]

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.