Starting managed servers using nodemanger from admin console

Change property in the nodemanager properties file

When you are planning to start a managed server from admin console (<host>:<port>/console).
Change the following property from false to true in nodemanger properties file.

StartScriptEnabled=true

The node manager properties file can be found at 

<fmw-home>\wlserver_10.3\common\nodemanager\nodemanager.properties

Where fmw-home is the weblogic installation directory or fusion middleware home.

Common Issues encountered

After this if you face port already in use error to start a managed server this is due to the debug property set to the same port . Try adding this lines to setDomain.sh / .bat  depending upon the environment you are using
<fmw-home>\user_projects\domains\soa_domain\bin\setDomainEnv.cmd
Rename the soa_server1 to your corresponding server name by default it is soa_server1

if "%SERVER_NAME%" == "soa_server1" (
   set DEBUG_PORT="8454"
)
at

if "%SERVER_NAME%"=="" (
    set SERVER_NAME=AdminServer
)

oraext:index-within-string throws internal xpath extension error

Using oraext:index-within-string is not pretty simple as it looks so . If you are using

oraext:index-within-string(($inputVariable.payload/client:DocId),'.')

Unlike builtin xpath functions which have internal type conversion this throws an error. Try using 

oraext:index-within-string(string($inputVariable.payload/client:DocId),'.')

Instead which works . Please note the conversion of string here .

This is applicable to oracle bpel assign activity .