J2ee application configuration

We have application consisting of servlets and ejbs. Unfortunately our configuration
is hierarchical and recurring. So it is difficult to specify it in deployment
descriptor file.
Have anyone tried any other approached like xml file or JNDI. Which one is better?
Have any one tried using xml configuration file. Is there any utilities available??.
How do you handle a situation where you have to change the configuration after
deployment?. Does it require repacking and redeployment.
In case of JNDI is it better to use LDAP??. What if I want use it from a stand
alone app?
Thanks in advance

Thanks for the reply.
Basically, I just want to able to read the j2EE Engine configuration, i.e. how many instances, what are they called, how they are configured, how many dispatchers, servers etc.... The config.xml file that could be generated from the configtool of the 6.20 J2ee engine contained all the information that I needed, but this xml file is now no longer available with 6.40.
Best regards,
Eoin

Similar Messages

How to configure rules in J2EE application

Please tell me how to configure rules in J2EE application. Configure rules in the sense before a page gets loaded a set of rules has to be fired automatically. A general idea how you would have been configured set of rules using java classes.
If any one would have worked on rules. Please post the code snippets as well to get the idea on how to configure rules. Thnx a lot in advance.

user13490100 wrote:
ya I know wht am I doing..jt asking for suggestions on using hibernate and configuration files...rules generally on load of the page for example the update address page..the user is elibigible to edit this page only on certain conditions depends on the policy..is there any other ways of doing these?
suggestion from side not necessary to take if u dont understand the question dont pass on the comments or type wht ever you want..You are not going to get an answer unless you clearly explain in standard English what your problem is.
Things you might want to cover:
--What these rules are (i.e. are they business rules, for example to check if a trade is fraudulent, or to decide if a plane has radar coverage in a particular location)
--Where these rules are currently stored, if anywhere
--What you're trying to do with these rules.

SSO to J2EE application from SAP Portal

Hi
I am trying to do SSO from SAP Portal to a J2EE engine which runs on SAP Web AS.
Here are my queries
1. When I deploy a J2EE application on Web AS , I dont get any login screen. How can I make sure that if a user wants to access this J2EE application he should get a login screen and provide his login credentials first, only then would he be able to access the J2EE application.
2.When I am done with Part 1. If a user tries to access this J2EE application from the Portal (asuming the user Id's in Portal and J2EE application are same and both are in the same domain) , I should not get any login screen and should be able to view the J2EE application.
3.I want to use SAP Logon tickets generated by the Portal to enable SSO.
I have done all the necessary configurations in the J2EE server.
1. Imported the Portal's verify.der certificate.
2. Adjusted the login modules stack for the application accordingly.
Can anyone please help me out with this or throw some light.
Please help.
Thanks in advance,
Vivek
PS - Points will be definitely rewarded

Hi Vivek,
Let me give you the solution for both questions differently.
Ques 1. When I deploy a J2EE application on Web AS , I dont get any login screen. How can I make sure that if a user wants to access this J2EE application he should get a login screen and provide his login credentials first, only then would he be able to access the J2EE application.
Ans: For doing this in the code of your J2EE application you have to write a if statement which will check if the user ID is coming from the backend or not. If yes then you display that logon page else you just pass that username which is coming from backend and displ;ay the page accordingly.
Ques 2.When I am done with Part 1. If a user tries to access this J2EE application from the Portal (asuming the user Id's in Portal and J2EE application are same and both are in the same domain) , I should not get any login screen and should be able to view the J2EE application.
Ans: Yes, this is what I am explaining you. Even I had also made same kind of J2EE application in which if the user is coming from the backend then he/she will look the J2EE screen else if the username is not coming then he will se the Login screen. Exactly same as what are looking for.
3.I want to use SAP Logon tickets generated by the Portal to enable SSO.
Ans: I have used User Mapping instead of SAP Logon ticket. Well that is also the option for SSO but personally I think User Mapping is easy and better way for implementing SSO.
I dont know whether this will help you or not. Please let me know. I can definately help if you want to implement SSO using User Maping.
Regards
Pravesh
PS: Please dont forget to reward points.

Unable to connect to the OracleForms application through a J2EE application

Hi there,
I have deployed a custom J2EE application in Middleware instance of my Oracle 10g AS 10.1.2
The application is sso enabled . Once a user logs in the application he is able to see a jsp in which i display hyperlinks for him to access.
One of these hyperlinks is pointing to the forms application.
the url is http://psc-pc0592:7778/forms/frmservlet?config=abs_deploy[b]
Once i click on the URL the forms applet begins to load but as the applet opens up i get the database logon screen.This should not happen
I am already logged and have been verified by sso.
Also the forms configuration is associated with a datasource.
I am not able to get as to why i get that screen when it shoud directly connect to the forms application.
Any help on this is appreciated.
Thanks & Regards,
Madhur Pant

when you go through your carrier provider, there is an additional step in the SSL tunnel. Not sure how this transcribes, but it is possible that your carrier does not use the same port as the one you want it to use.
The search box on top-right of this page is your true friend, and the public Knowledge Base too:

Is anyone doing disaster recovery for a J2EE application?

We generally use database log shipping to maintain a standby database for our ABAP instances. We can successfully fail over our production application to our disaster recovery site with no real issues. With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them? Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
Regards,
David Hull
The Walt Disney Company

I haven't done this personally, but I do have some experience with these issues in different HA environments.
To your first point: You can change the hostname, note 757692 tells you exactly how to do it. However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP." When it says "supported by SAP" I think it means SAP the company, not SAP's software. So I would contact SAP to see if this configuration would be covered under your service agreement. Then you have to think about whether you want to do something that isn't "officially supported" by SAP. Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
To your second point: As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same. I don't think they are hostname or fqdn dependant. For BSPs I would think they would still work as long as they use relative paths rather than absolute paths. And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
Again, I haven't done what you're describing myself. This is just based on my HA experiences.
Hope this helps a little,
Glenn

Simple J2EE application fails under activation

Hi,
I have a simple J2EE application which contains one Servlet.
I have two DCs: SSORedirector (Enterprise application project) and SSORedirectWebModuleWebModule (Web Module)
(there is a third DC which is a child DC to SSORedirector, but I don't think it causes any problems)
The web module has by default public part called war (an I haven't touched this).
The Enterprise application project I have addeed the required references to the web module in the application.xml(this automatically set a Used DC reference).
When right-clicking the enterprise application and selecting build, it builds a correct ear file, and if I deploy it to my local workplace installation, the J2EE application works as expected.
However, when I try to check in and activate the activity the SDM deployment fails with the message: Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
I've retrieved the .sda file on the file system (shouldn't it be an .ear file) and it contains the application.xml under the folder meta-inf. The complete contents of the sda file is
./d1c66970ddbec7e6ffcc4d01c4705600.HASH
./META-INF/application-j2ee-engine.xml
./META-INF/application.xml
./META-INF/MANIFEST.MF
./META-INF/SAP_MANIFEST.MF
./META-INF/sda-dd.xml
./src/java/src.zip
./bouvet.com~SSORedirectorServlets.war
What could possibly be wrong?
Below are some logs.
Deployment log
SAP Change Management Service
System sapJDI.st.bouvet.no
Build space JDI_ZEPSSO_D
Request 8554
Step Deployment
Log /sapmnt/JDI/global/TCS/LOG/JDI_ZEPSSO_D2006021618420025.log
Info:deploy every archive associated to the buildspace: JDI_ZEPSSO_D
Info:getting DC SSORedirector from CBS for buildspace: JDI_ZEPSSO_D
Info:archive /sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda for DC SSORedirector was transfered
Info:Start deployment:
Info:The following archives will be deployed (on http://sapED2.st.bouvet.no:50018)
Info:/sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
Info:SDM log:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:Feb 16, 2006 7:39:58 PM Info: -
Starting deployment -
Info:Feb 16, 2006 7:40:01 PM Info: Loading selected archives...
Info:Feb 16, 2006 7:40:01 PM Info: Loading archive '/usr/sap/ED2/JC00/SDM/program/temp/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda'
Info:Feb 16, 2006 7:40:11 PM Info: Selected archives successfully loaded.
Info:Feb 16, 2006 7:40:11 PM Info: Actions per selected component:
Info:Feb 16, 2006 7:40:11 PM Info: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
Info:Feb 16, 2006 7:40:14 PM Info: The deployment prerequisites finished withtout any errors.
Info:Feb 16, 2006 7:40:14 PM Info: Saved current Engine state.
Info:Feb 16, 2006 7:40:15 PM Info: Error handling strategy: OnErrorSkipDepending
Info:Feb 16, 2006 7:40:15 PM Info: Update strategy: UpdateAllVersions
Info:Feb 16, 2006 7:40:15 PM Info: Starting: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
Info:Feb 16, 2006 7:40:15 PM Info: SDA to be deployed: /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
Info:Feb 16, 2006 7:40:15 PM Info: Software type of SDA: J2EE
Info:Feb 16, 2006 7:40:15 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Feb 16, 2006 7:40:15 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Feb 16, 2006 7:40:15 PM Error: Aborted: development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596':
Info:Caught exception during access of archive "/usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda":
Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
Info: (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Info:Feb 16, 2006 7:40:26 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Info:Feb 16, 2006 7:40:27 PM Error: -
At least one of the Deployments failed -
Info:end of log received from SDM
Info:End deployment:
Info:deploy finished for SSORedirector (8554) with rc=12
Info:deployment finished for buildspace: JDI_ZEPSSO_D
CBS log
CBS Request Log - [ 8554/JDI_ZEPSSO_D ]
sapjdi.st.bouvet.no SAP Component Build Server
Build number assigned: 8596
Change request state from QUEUED to PROCESSING
ACTIVATION request in Build Space "JDI_ZEPSSO_D" at Node ID: 37,956,050
 [id: 8,554; parentID: 0; type: 4]
 [options: NO OPTIONS]
REQUEST PROCESSING started at 2006-02-16 18:41:35.949 GMT
===== Pre-Processing =====
List of activities to be activated:
 1 activity in compartment "bouvet.com_PASSTHROUGH_SSO_1"
 C049689.6 - Passthrough SSO
 [seq. no 17][created by 433937 at 2006-02-16 19:41:49.0][ID 44ed44bc9f1911daae5b0012799e50b6]
Analyse activities... started at 2006-02-16 18:41:35.967 GMT
 Synchronizing component "bouvet.com/SSORedirector" from repository... finished at 2006-02-16 18:41:37.129 GMT and took 1 s 10 ms
 Component "bouvet.com/SSORedirector" is to be CHANGED by this activation.
 Synchronizing component "bouvet.com/SSORedirectWebModule" from repository... finished at 2006-02-16 18:41:37.933 GMT and took 802 ms
 Component "bouvet.com/SSORedirectWebModule" is to be CHANGED by this activation.
 Synchronizing component "bouvet.com/SSORedirectorServlets" from repository... finished at 2006-02-16 18:41:39.144 GMT and took 1 s 211 ms
 3 components to be build in compartment "bouvet.com_PASSTHROUGH_SSO_1"
Analyse activities... finished at 2006-02-16 18:41:39.202 GMT and took 3 s 235 ms
Calculate all combinations of components and variants to be built...
 "bouvet.com/SSORedirector" variant "default"
 "bouvet.com/SSORedirectorServlets" variant "default"
 "bouvet.com/SSORedirectWebModule" variant "default"
Prepare build environment in the file system... started at 2006-02-16 18:41:39.410 GMT
 Synchronize development configuration... finished at 2006-02-16 18:41:39.430 GMT and took 20 ms
 Synchronize component definitions... finished at 2006-02-16 18:41:39.469 GMT and took 38 ms
 Synchronize sources...
 Synchronize sources... finished at 2006-02-16 18:41:40.891 GMT and took 1 s 422 ms
 Synchronize used libraries...
 public part "war" of component "bouvet.com/SSORedirectWebModule" ... OK
 [PP "war" of DC 381 variant "default"][SC 142][last successfull build: 0]
 public part "default" of component "sap.com/ejb20" ... OK
 [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
 public part "default" of component "sap.com/jdbc20" ... OK
 [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
 public part "default" of component "sap.com/jms" ... OK
 [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
 public part "default" of component "sap.com/servlet" ... OK
 [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
 public part "default" of component "sap.com/ejb20" ... OK
 [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
 public part "default" of component "sap.com/jdbc20" ... OK
 [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
 public part "default" of component "sap.com/jms" ... OK
 [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
 public part "default" of component "sap.com/servlet" ... OK
 [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
 Synchronize used libraries... finished at 2006-02-16 18:41:43.712 GMT and took 2 s 820 ms
Prepare build environment in the file system... finished at 2006-02-16 18:41:43.712 GMT and took 4 s 302 ms
===== Pre-Processing ===== finished at 2006-02-16 18:41:43.713 GMT and took 7 s 755 ms
===== Processing =====
BUILD DCs
 "bouvet.com/SSORedirectorServlets" in variant "default"
 Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
 The build was SUCCESSFUL. Archives have been created.
 "bouvet.com/SSORedirectWebModule" in variant "default"
 Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
 The build was SUCCESSFUL. Archives have been created.
 "bouvet.com/SSORedirector" in variant "default"
 The build was SUCCESSFUL. Archives have been created.
===== Processing ===== finished at 2006-02-16 18:41:56.154 GMT and took 12 s 436 ms
===== Post-Processing =====
Check whether build was successful for all required variants...
 "bouvet.com/SSORedirectorServlets" in variant "default" OK
 "bouvet.com/SSORedirectWebModule" in variant "default" OK
 "bouvet.com/SSORedirector" in variant "default" OK
Update component metadata...
 "bouvet.com/SSORedirector" has been CHANGED
 "bouvet.com/SSORedirectWebModule" has been ACTIVATED
STORE build results...
 "bouvet.com/SSORedirectorServlets": store meta-data
 "bouvet.com/SSORedirectorServlets" in "default" variant is PROCESSED
 "bouvet.com/SSORedirectWebModule": store meta-data
 "bouvet.com/SSORedirectWebModule" in "default" variant is PROCESSED
 "bouvet.com/SSORedirector": store meta-data
 "bouvet.com/SSORedirector" in "default" variant is PROCESSED
Change request state from PROCESSING to SUCCEEDED
Analyse effect of applied changes to buildspace state... started at 2006-02-16 18:41:56.364 GMT
Handle Cycles...
 No cycles detected.
Determine components that have become DIRTY due to the results of this request...
 No such components have been found.
Integrate activities into active workspace(s)...
 Integration of activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" started at 2006-02-16 18:41:56.785 GMT
 "C049689.6 - Passthrough SSO" OK
 Integration of 1 activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" finished at 2006-02-16 18:42:16.614 GMT and took 19 s 829 ms
Analyse effect of applied changes to buildspace state... finished at 2006-02-16 18:42:16.615 GMT and took 20 s 251 ms
Request SUCCEEDED
===== Post-Processing ===== finished at 2006-02-16 18:42:16.617 GMT and took 20 s 451 ms
REQUEST PROCESSING finished at 2006-02-16 18:42:16.618 GMT and took 40 s 669 ms

Managed to solve it in a obscure way.
I had earlier deployed the .ear file directly from NWDS to our dev system (hadn't installed dev workplace then). By removing the application from the deploy service in visual admin, the import suddenly worked.
Dagfinn

How to make J2EE application in OC4J use windows credentials

Hi,
I have a J2EE application which is deployed in Oracle10AS. When a user tries to access this application, the application should use windows login information and authenticate the user and allow access to the user.
Can someone guide me on how to achieve this, any links or documents to achieve this would be greatly appreciated.
Thanks

The configurations in mod_osso.conf were not made properly hence getRemoteUser() was failing. Once mod_osso.conf was configured properly everything went well.

How to get deployment time of an J2EE application

Hi All,
I am developing J2EE applications on NetWeaver 7.0 and 7.1. In my application, I need to get deployment time of a J2EE application installed in the J2EE engine.
For NetWeaver 7.1, I found SAP's Java APIs to do that:
com.sap.engine.services.deploy.server.cache.dpl_info.Applications.get("appName").getMonitorData().getDateOfLastRedeployment();
But for NetWeaver 7.0, I haven't found any similar stuffs.
Could you give me any helps for the case of NetWeaver 7.0?
Thank you very much.
Viet

I'm not 100% sure but you may be able to turn on tracing for the Java stack "Deploy" service.
In Visual Administrator, go to "Global Conf [Server] -> services -> Deploy" change additional_debug_info.
Then in "Cluster [server x] -> services -> log configurator [locations] -> com -> sap -> engine -> services -> deploy" change the debug level to "Info" or something.
This should put some additional tracing out to the trace files which can be viewed in the Log Viewer.
Don't forget to reset the trace level when you're done.

Building J2EE Applications using JBOSS and ECLIPSE 3.0

Hi all
i am trying to deploy a J2EE application using JBOSS3.2.5 and Eclipse 3.0.
I have written the EJB bean, home, remote and a test JSP page. Can someone tell me the exact procedure...step by step ways to deploy the JBOSS server and run my application.
My package structure is
MyProject
ejb
client
Servlet.java
server
Bean.java
shared
home.java
remote.java
please tell the various jar files that i must include. Kindly give information about the directory structure, the xml file details and the WAR file generation
Thankz in advance
Arun :)

That is a lot of stuff! At a basic level, you can create an EAR file and put it in the JBoss auto-deployment directory. In the EAR file you should have a WAR file for the web component and a JAR file for the EJB component. And inside each archive there should be a valid deployment descriptor that contains configuration data for the component. When you start up JBoss, the application will be deployed and accessible via web browser, or there will be error messages written to the server log.

Porting j2ee application from Weblogic to Oracle 10g AS

What are the common guidelines/consideration when we port a J2EE application on Oracle Application server 10g. from WebLogic 8.1. If you have some inputs on pin points/guidelines/Architecture decisions that we might need to consider when we port a J2EE application on different J2EE application server
I got the link for app server migration but it is broken :
http://www.oracle.com/consulting/technology/appserver_migration_ds.pdf
Our application uses the following J2EE components
1. JDBC 2.0
2. JNDI
3. DAO
4. EJB
5. JMS
6. JAAS
7. JAVA Mails.
8. Servlets, JSP’s
I can think following point that needs to take care while porting
1. Its deployment configuration vis-a-vis the apps on top
2. The APIs it exposes (actually the information it allows the apps to pass in to the framework
3. The data it encapsulates (in order to be app-server agnostic; does it need to be now exposed to apps?)
Some J2EE specific areas
1. JNDI usage and exposure to apps 2. Properties files/XML files
2. Location specification 3. Resource bundle location specification
4. EJB deployment descriptors
5. Class/jar references between wars and ears
6. Jar sharing model across ears
7. Class loader differences across app-servers
8. JMS settings (queues, topics, factories, durability etc)
9. UI tags 10. Startup services
11. Managed services (JMX)
12. Security context passing
13. Clustered configurations if any and how they port across app-servers
Thanks
Santosh Maskar

This document is very old.
Take a look at the recent migration guide in the Oracle AS 10.1.3.1 documentation
http://download-uk.oracle.com/docs/cd/B31017_01/migrate.1013/b31269/toc.htm

Unit test for J2EE application

I am writting a Unit test for One J2EE application. The Application is built in such a way that makes unit testing extremely difficult.
There are 2 things that contribute to the mess.
1. Sping integration means all the config files are specified in web.xml independently, even though their beans rely on each other across files. End result is in a unit, I cannot try to load a bean because some of its dependencies are missing (ie. they are in a config file that the first file does not include). For this I tried to use AbstractDependencyInjectionSpringContextTests class to set the Spring Application Context when you are not in the flow but didn't success ed.If any one has use this please post the example.
2. The application is using Errors interface of package org.springframework.validation. To write a test for any validator class you have to pass the object of Error in the validate method with the command object. Now my question is how you can set this Error object when you are not in the flow. For this I tried to use Mock object e.g Errors error;
Mockery context = new Mockery();
final Errors errorMock =context.mock(Errors.class);
//call the validate object with mock object
classObject.doValidate(cmdObject, errorMock)
This thing doesn't work. It gives me below error message.
unexpected invocation: errors.pushNestedPath("")
no expectations specified: did you...
- forget to start an expectation with a cardinality clause?
- call a mocked method to specify the parameter of an expectation?
Is there any way to get around these hiccups programmatically in unit tests?
thanks...

If you are doing unit testing, try to use straight JUnit4 without involving the Spring framework. Given that you do unit testing, you might not need Spring configuration in your unit test at all. You can programmatically instantiate the instance of the class under testing and either programmatically instantiate collaborating objects, or create mock objects for that purpose. If you are doing functional testing, you might need a Spring context after all. Understand that your tests are running in the different context than the complete application, so you would have to create separate application context for your test(s). You might have to go through the existing Spring configuration modules that you created for your application and re-jiggle them a bit so that they can be included both in your application context and your unit test context.
Hope this helps.

File- XI- J2EE application(HTTP adapter as Receiver)

Hi all!
My question is What else to be given in ID i.e., in my outbound communication channel: I have given the following:
Adapter Type: HTTP
Receiver
Transport Protocol: HTTP1.0
Message Protocol:XI payload in HTTP body
Adapter Engine:Integration server
Addressing Type: URL Address
Targer Host: localhost(My J2EE application resides here)
Service number:7001
Path:/InvokeJ2EE/SendName
Authentication Type:
Username:xiappluser
password:xxxxx
Lonon language: EN
Content type: text/xml
XML code: UTF-8
I have tried many blogs, but i didn't get get correct response!

HI
GOOD
GO THROUGH THIS LINKS
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping%3Fpage%3Dlast%26x-maxdepth%3D0
http://www.sun.com/third-party/global/sap/collateral/SunSAPWP_final.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm
THANKS
MRUTYUN

6.40 J2EE Engine Configuration Data

How can 6.40 J2EE Engine Configuration be accessed externally by 3rd party software?
The 6.20 J2EE engine allowed all configuration data, cluster setup, servers, dispatchers etc. to be exported as an XML file. With the 6.40 J2EE Engine all data is stored in the database. In the configtool, there is an option to export unsaved changes to XML, but this only appears to export Secure Store Data. Can this secure store data be used to connect directly to the database from external application in order to read configuration setup.
Many thanks.

Thanks for the reply.
Basically, I just want to able to read the j2EE Engine configuration, i.e. how many instances, what are they called, how they are configured, how many dispatchers, servers etc.... The config.xml file that could be generated from the configtool of the 6.20 J2ee engine contained all the information that I needed, but this xml file is now no longer available with 6.40.
Best regards,
Eoin

Double submission problem in J2EE application under Weblogic 8.1 SP2 server

Hi,
We are facing double submission problem in our J2EE application which is running under Weblogic 8.1 SP2 and for the same we already implemented or added the below preventive solutions.
1. We disable the SUBMIT button once the user clicks it.
2. We preventated pressing 'F5' button and clicking 'Refresh' button in the browser.
3. Also we tried to prevent by declaring the idempotent is 'true' under weblogic-ejb-jar.xml as below.
<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempotent>
So please somebody help us on this issue like how to prevent in some other way.
Regards,
Dinesh.

I have no idea why you would think changing your EJB configuration would have anything to do with preventing double submission at your servlet layer.
One technique I've seen for preventing double submission was first used in the Struts framework several years ago. When a page is "prepared" for display, a token value is created and stored in the session. The page is displayed with a hidden field containing that value. When the page is submitted, the value of the hidden field is compared with the value stored in the session. If they're not equal, the submission is ignored.

Integrating WebSphere/J2EE applications in portal

Greetings!
I need to integrate Websphere/J2EE applications in NW04s Portal. How can we acheive this.
I have heard about AppIntegrator iViews can be used for this purpose, but can anyone help me on how to configure one on NW04s? Are there any good documents that can help?
Thanks for your help!
Regards
KV

Hi KV,
Here is the documentation for the AppIntegrator iview:
http://help.sap.com/bp_epv260/EP_JA/documentation/How-to_Guides/25_HowToUseAppIntegrator_en.pdf
And two blogs covering this topic:
Step-By-Step Guide to implement Application Integrator
Integrating your Web Front-ends into the SAP Enterprise Portal using the Application Integrator
Regards,
Johan

J2ee application configuration

Similar Messages

Maybe you are looking for