Hello @Nimisha Joseph 
As per you're SQL implementation. It's actually straightforward and you took and store "Forename" and "Surname" in to context.  haven't taken any SQL resultset object to loop. You can execute only embedded sql in the <sql> BPL element.

So, If you want to execute the query you can assign the SQL object by using <assign> or you can use code block to write executable codes. I have added some sample code below for reference.

• Assign the SQL result set object to context variable
• while the result set
  • process and result and do your implementation

/// BPL Definition
XData BPL [ XMLNamespace = "http://www.intersystems.com/bpl" ]
{
<process language='objectscript' request='Ens.Request' response='Ens.Response' height='2000' width='2000' >
<context>
<property name='Forename' type='%String' instantiate='0' >
<parameters>
<parameter name='MAXLEN'  value='50' />
</parameters>
</property>
<property name='Surname' type='%String' instantiate='0' >
<parameters>
<parameter name='MAXLEN'  value='50' />
</parameters>
</property>
<property name='ReportDiscipline' type='%String' instantiate='0' >
<parameters>
<parameter name='MAXLEN'  value='50' />
</parameters>
</property>
<property name='tResult' type='%SQL.StatementResult' instantiate='0' />
</context>
<sequence xend='200' yend='950' >
<trace name='TEMP trace element' value='"In business process "_request.StringValue' xpos='200' ypos='250' />
<assign property="context.ReportDiscipline" value="request.StringValue" action="set" xpos='200' ypos='350' />
<trace value='"ReportDiscipline value: "_context.ReportDiscipline' xpos='200' ypos='450' />
<assign property="context.tResult" value="##Class(%SQL.Statement).%ExecDirect(,&quot;select * from table&quot;)" action="set" xpos='200' ypos='550' />
<while condition='context.tResult.%Next()' xpos='200' ypos='650' xend='200' yend='450' >
<assign property="context.surname" value="context.tResult.%Get(&quot;surname&quot;)" action="set" xpos='200' ypos='250' />
</while>
<trace value='"SQLCODE: "_SQLCODE' xpos='200' ypos='750' />
<trace value='"returned value: "_context.Forename' xpos='200' ypos='850' />
</sequence>
</process>
}

HTH.

Have you verified? Did you get all the values whether the hl7 message is properly imported to the object after executing XMLImportSDAString for all the properties.

do reqObj.XMLImportSDAString(xml.Read())

I believe the simulator/JWT.io uses Base64UrlEncode instead of Base64Encode
The problem with Base64Encode is that it contains the characters + , / , and = ,. So Base64UrlEncode solves this by replacing + with - and / with _ .

The lock is belongs from different process(9908) and you're trying to terminate  via different process(10376) not is not possible. You can verify and terminate the 9908 in process  (System Operation>Process) if no longer required for prevent multiple locks set again and click remove all locks for process and remove it.

• Use $test  special variable in your code to check the for success/failure lock. If lock is success it return 1 otherwise return 0 based on this result you can continue your logic flow.
• Always use incremental lock with timeout (ex: lock +^test:0) 

LEARNING>w $test
0
LEARNING>lock +^test:0
 
LEARNING>w $test
1
LEARNING>

Basically. The tcommiit will commit the current open transaction. Lock -^global (decremental lock ) is used to release the incremental lock( lock +^global) so everytime if you do incremental lock then you should decrement the lock) by using lock -^gbl syntax

Argumentless lock is release all the locks in the process. So this is not highly recommend in code. And incremental locks are highly recommend for use.

I see you're locking the global  +^IudexNqlInByte not unlocking. can you check the below

tstart
	if staten["IUDX" {
		lock +^IudexNqlInByte(1):0
		if $test{ 
			set IudexNqlInByte(1,inc)=obj.%Id()
			lock -^IudexNqlInByte(1)
		}
	}
	else {
		lock +^ToshibaNQLIn(1):0
		if $test {
			set ^ToshibaNQLIn(1,inc)=obj.%Id()
			lock -^ToshibaNQLIn(1)
		}
	}
tcommit

Thank you for the samples. Now it works fine and I get JWT. I have seen this parameters in some other post in community. What is the exact use of these parameters dispatcher class.

 Parameter TokenLoginEndpoint = "login"; Parameter TokenLogoutEndpoint = "logout"; Parameter TokenRevokeEndpoint = "revoke"; Parameter TokenRefreshEndpoint = "refresh";

Yes. my web application is /api and invoked this http://localhost:52774/api/login