h2. PART
II
In
the first part
We
said that (How-To Create Dynamic & Configurable Web Services Easily With Netweaver Development Components (Part...) we can create dynamic
web services with Netweaver Developer
Studio, and without code modification
we will change the configurations
on the fly. For doing this we
should first create web service
configurations.
+To
do this;+
Open
the ejb project, double click
on the web service configurations,
create to configuration by clicking
the add button.
First
one was standard, named Config1,
and it was added when we first
create the web service.
The
second will be used for reaching
the web service via basic authentication
with username and password. Create
the new configuration by clicking
web service configurations, click
the web service name and click
the add button. After creating
the configuration choose security;
select HTTP Authentication for
Authentication mechanism and Basic +Use
SAP Logon Ticket +from
below. Choose operations(your
ejb methods) for web service and
save. Save it and your configurations
look like the below one :
After
this, add the ejb project to ear
project and deploy the ear project
to server.
If
we want to see how it looks like
from the server side, go to the
visual administrator on your j2ee
server, choose +server > services >
web
services container+;
in the endpoints&wsdl tab
you see your web service, and
2 config ports, with different
addresses. Now we will point to
these two ports declaratively
without coding after making a
few adjustments.
Its
time to generate the parts in
our proxy project and call them
from our servlet in the web project.
We
created the server proxy project
and generated a logical port.
Here target address is our destination
and logical port name is our reference
for reaching the service. Your
project is like the one below
:
Adding
public parts
In
order for other DCs to call our
proxy we should add the parts
to our public parts both as *API
and SDA*.
To do this go to Proxy Project,
select your proxy, right click
on it and create a new public
part by selecting add proxy to
public part and choose type API.
Do the steps again and add an
SDA public part. Build and deploy
the project. Then we will use
these references in our web project
Then
we start to fill our web project.
First we create a servlet by right
clicking on the web project and
choose new servlet. Remove the
doPost method therefore our servlet
is only callable from URL. Then
add the following code to our
doGet method. Dont panic, at first
it cannot find the Test2WS and
some other class .
Our
code is like the one below :
protected
void doGet(HttpServletRequest
request, HttpServletResponse response)
throws
ServletException,IOException {
try
{
InitialContext ic = new InitialContext();
Test2WS
testWS = (Test2WS) ic.lookup( "java:comp/env/DepProxy1" );
Test2WSViDocument vi = testWS.getLogicalPort();
String s = vi.getDateAndTime( "baris" );
response.getWriter().write(s);
} catch (Exception e) {
response.getWriter().write(e.toString());
}
}
After
that we should add our proxy reference
from used DCs. To do this we go
to DC metadata, choose DC definitions,
right click on used DC and add
our previously generated public
parts to project like the below
image. Choose build time and runtime
and choose strong for dependency
type.
We
should also add web services from
the SAP_JTECHS SD
under used +DCs > Local
Development+ and
webservices_lib from SAP-JEE for
using the web service related
libraries.
Adjustments
We
then have to map our servlet to
a URL from web.xml. Look below,
its as easy as seen in the picture.
Double click web.xml, choose mapping
tab, click ServletMappings, add
a servlet and create mapping with
a URL pattern by starting with
a slash(/WSClientServlet).
Save and you can use it.To
determine the application root,
enter application.xml;
go to modules tab, select the
web project, and change the context
root for your preference by clicking
get context root... By this way
your servlet is callable via URL
: http:// <yourserver>:<yourport>/<yourcontextroot>/<yourservletmappingpath>
Lastly
we have to add the proxy reference
to application-j2ee-engine.xml for
using in runtime. In the general
tab choose references, create
new and add the related information.
See the image below for this :
Testing
After
deploying our project, our servlet(therefore
our web service) is callable from
URL : /bb/WSClientServlet.
Bingo!! And here is the response
:
Now
the switching without the code
part :
We
said that we can switch configurations
without any coding effort. To
do this we will use our logical
ports from the proxy project.
We will switch to our second config
port, which makes authentication
therefore our web module calls
the authenticated web service
proxy without any code change.
If
we want to change the address
in our project just change the
target address in the logical
port and point to other port.
See the image below :
Therefore
we call the authenticated web
service and get an unauthorized
exception.
Revert
back your changes in the proxy
project.
Now
comes the magical part ..
Without
deployment just go to the visual
administrator, go to web service
security > web
service clients and find the application.
At first it look like the one
below :
Just
change the URL and point your
proxy target and bingo again!!
You can call the application (call
the service without authentication)
again, and no exception. Upps,
no, just apply the basic rule
: Restart first(just the application)
Go
to deploy service, choose application,
choose your proxy, stop and start
it, now you can call the service.
Again
you have changed the destination
to basic authentication web service,
but this time without changing
your project code.
5 Comments
