Idan Adar :
Just like you can deploy multiple instances of Worklight (v6 and above) projects - multiple .war files to the same WAS application server, there should not be issues to deploy it to an application server running other services.\n\nThat said, possible issues to consider:\n\n\nWhen deploying a Worklight project, you will want to enable \"application security\"\n(in the WAS admin console, Security > Global Security). If there are some other web\napplications for which application security is undesired, you need a different WAS server\ninstance.\n\n\nSetting up, enabling and migrating security\n\nThe list of users that can use the web applications are configured through LDAP or\n\"federated repositories\", or similar. If, for Worklight, you need to use a completely\ndifferent set of user logins than for the other web applications, then you need to use\nmultiple \"security domains\".\n\n\nConfiguring multiple security domains\n\nThe machine hosting the application server will probably need memory upgrades...\n\n\nDeploying the Enterprise Archive (EAR) Using the WebSphere Admin Console\n\nProbably also need to make clear seperation where required:\n\n\nIBM WebSphere Developer Technical Journal: Co-hosting multiple versions of J2EE applications\n\n",
2013-12-04T16:09:41