EASERVER 6.3.1 : location of web application properties(terminalregister.properties) file.

I have a web application migrated on Easerver 6.3.1 from 5.5 and Powerbuilder 10.5 to 12.5.2 which takes the request through the SOAP UI tool and receives the response back. For older version(5.5) the project has the property file placed at the bin folder and the SOAP request use to pick the server details from that location by default to read server login details and logging information. In Easerver 6.3.1  it's not picking the properties file content from default i.e bin folder of Easerver6. The code is JAVA code in eclipse and methods are written to read the property file contents.            As of now to run my application I have to hard code the complete path location of my property file( as of now in easerver6\bin) where ever kept and it reads the file content correctly. Let me know if anyone has idea that how and where we can place the application property file having server details to read the contents without hard coding the path location. I have been struggling to resolve this from past one week but seems to have no luck on it. Thanks for response in advance.

Here is the code example where I have hard coded the path to read the property file. Hope it may help you to understand in better way.

public class TerminalRegisterSOAPBindingImpl implements terminalregister.services.registerterminal.TerminalRegisterPortType{

    private static final String CLASS_NAME = "TerminalRegisterSOAPBindingImpl";
    private static final String PROP_FILE_NAME = "C:\\prg\\Sybase\\EAServer6\\bin\\terminalregister.properties";

    static no.bbs.baxbis.util.JMSLogger termregLogger;

    private String authenticateUser( no.bbs.baxbis.util.JMSLogger termregLogger ) throws java.rmi.RemoteException {

        return no.bbs.baxbis.util.AuthenticateWebserviceAccess.authenticateUser( PROP_FILE_NAME, termregLogger );

    }

    public void merchants(terminalregister.services.registerterminal.Merchant[] merchant) throws java.rmi.RemoteException {
        final String OPERATION = "merchants";


        termregLogger = new no.bbs.baxbis.util.JMSLogger( "termreg", PROP_FILE_NAME );
        //Test     
        //System.out.println( "TerminalRegisterSOAPBindingImpl called" );

        termregLogger.of_trace(1, CLASS_NAME, OPERATION, "Start, props = " + PROP_FILE_NAME);

Regards,

Kunal