• -jts starts a Container-resident, lightweight, one-phase-capable JTS service. Turning on the Transaction Service in the Borland AppServer's daemon starts a full two-phase transaction manager.
• -jns starts a CosNaming service in the Container process that does not persist its data and uses all default configuration parameters of the VisiBroker for Java 4.x Naming Service. Using the IAS counterpart, you can configure it more flexibly but functionally it is equivalent in the sense that they are both exactly the same service.
• -jss is the Container’s state repository for stateful session beans. There is no conterpart of this under IAS.
• -jdb starts an in-process RDBMS. The JDataStore service in the IAS daemon is functionally equivalent.

Bottomline: The Container's built-in services are developer-friendly incarnations of services that are functionally complete and equivalent. The difference is in configuration and lifecycle control.