The best practice is to have a unique name for each port. In general, the port name is based on the name of the web service. You'll see that a lot in the out of the box web services. There are also a couple that have arbitrary names like "Port"
The name has to be unique to the WSDL, not the environment, so you can get away with re-using a port name across multiple remedy web services. Spend some time considering the naming convention that you will follow. You may want to include a version indicator, a reference to the functional purpose of the service, or a reference to any number of other things. Once you publish, changing the name could pose a problem for consumers of the service. -- Steve On Mon, Feb 18, 2013 at 4:00 AM, Ramy S. Ayoub <[email protected]> wrote: > ** All > > When creating new Web Service which port should be considered , do we need > to change the port for each WSDL we are creating or we should use default > > Version 7.6.04 > > > > -- > > *Ramy Ayoub* > Products and Service Delivery > > Business Process Automation > > Vodafone – Egypt > > Phone: +20100441441 > Email: [email protected] > > Smart Village, > > Vodafone-Egypt C2 Building > Cairo/Alex – Desert Road > > KM28, Smart Village > > > > > > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
