Saritha,
I read the thread pointed to, by RMG, his suggestion is useful… for the sake of alternatives, you can also use an XML to store your config. I usually prefer this! In order to read this config file, you may create a flow service (eg readConfig) comprising of pub.flow:getFile-> pub.xml:xmlStringToXMLNode-> pub.xml:xmlNodeToDocument, to read the contents of the config file into an IS Document (you will need to create an IS Doc corresponding to the config xml).
If the config parameters are read often, it will be a good idea to define readConfig as a startup service and add a step in that service to store the config IS Doc into a Data Store or create a static IData Object. Then create a wrapper java service around this that checks whether the config IS Doc is present in the memory (as a static object or in the Data Store), if yes, return the requested parameter from that memory object or else do a physical read and store the config as a memory object before returning the value of requested parameter.
HTH, Roh
#Integration-Server-and-ESB#webMethods#edi