Deploy an Applet across multiple servers

I have an applet which will need to be deployed over numerous servers and urls.
I was wondering if there was a way for the applet to know which ip/url it was run from, without making a properties file and packaging it in the applets jar file.
As an example,
Let's say I had 3 servers, at the following urls
https://server1.com
https://server2.com
https://server3.com
My applet needs to call a servlet on the server where the applet came from.
Ex.
         URL url = new URL( SERVER +"/ServletToCall" );
         HttpsURLConnection servletConnection = ( HttpsURLConnection ) url.openConnection();
         ...How do I know which url to call without hardcoding it in, or using a properties file?

you'll need to change
URL url = new URL( SERVER +"/ServletToCall" );
//to
URL url = new URL( getCodeBase().getHost() +"/ServletToCall" );// getCodeBase()unless you are planning on signing the applet

Similar Messages

Capture performance metrics across multiple servers

Hello. I'm still very new to Powershell but anyone know of a good Powershell v.3 -4 script that can capture performance metrics across multiple servers with an emphasis on HPC (high performance computing) and gen up a helpful report, perhaps in HTML or Excel
format?
Closest thing I've found and used is this line of powershell:
http://www.microsoftpro.nl/2013/11/21/powershell-performance-monitor-on-multiple-remote-computers/
Maybe figure out a way to present that in better format, such as HTML or Excel.
Also, if someone can suggest some performance metrics to look at with an HPC perspective. For example, if a CPU is running at 100 utilization, figure out if which cores are running high, see how many threads are queued waiting for CPU time, etc...

As far as formatting is concerned,
ConvertTo-HTML is a basic HTML output format, but you can spice it up as much as you like:
http://technet.microsoft.com/en-us/library/ff730936.aspx
Out-Grid is very functional and pretty simple:
http://powertoe.wordpress.com/2011/09/19/out-gridview-now-has-a-passthru-parameter/
Here's an example with Excel:
Excel
Worksheets Example
This might be a good reference for HPC, I don't have access to an HPC environment so I can't offer much advice there.
http://technet.microsoft.com/en-us/library/ff950195.aspx
It might be better to keep unrelated questions separate, so a thread doesn't focus on one question and you lose time getting an answer to another.
I hope this post has helped!

Splitting up a job for 140k+ users across multiple servers

Hello,
I am pretty new to Powershell and want to learn more about scaling stuff and just started working with jobs.
In this particular case I am just doing mass enable or disable at a per user level. The other script I need to do this with grabs and checks values on around 6000 distribution groups and using the current values and type it creates new commands
to add/remove certain users or permissions in bulk with Invoke-Expression. I *think* it would probably be best in my case to run these across servers as well.
Basically what I am looking at is:
Using one large list/array, counting it, splitting it, using the resources it has available with jobs.
One of the problems I have had with this but seems I have mostly figured out is how I combine or 'foreach' several different values that may need to be applied to separate objects on certain servers with certain users and certain attributes.
Last night I ran the first script that could do that but it took me awhile and looks like a wreck I am sure - but it worked!
Now to tackle size.
Thank You

Hi Paul,
looking good so far. Did a little rewrite of what you posted:
Function Disable-Stuff
Param (
[Parameter(Position = 0, Mandatory = $true)]
[string]
$file,
[Parameter(Position = 1)]
[ValidateSet('CAS', 'MBX', 'ALL')]
[string]
$servertype = "CAS"
# Collect server lists
$servers = @()
switch ($servertype)
"CAS" { $servers += Get-ClientAccessServer | Select -ExpandProperty name }
"MBX" { $servers += Get-MailboxServer | select -ExpandProperty name }
"ALL"
$servers += Get-ClientAccessServer | Select -ExpandProperty name
$servers += Get-MailboxServer | select -ExpandProperty name
# Remove duplicate names (just in case)
$servers = $servers | Select -Unique
default { }
# Calculate set of operations per server
$boxes = ($servers).count
$content = Get-Content $file
$split = [Math]::Round(($content.count / $boxes)) + 1
# Create index counter
$int = 0
# Split up task
Get-Content $filepath -ReadCount $split | ForEach {
# Store file content in variable
$List = $_
# Select Server who does the doing
$Server = $servers[$int]
# Increment Index so the next set of objects uses the next Server
$int++
# Do something amazing
# ... <-- Content goes here
Disable-Stuff "c:\job\disable.txt" "CAS"
Notable changes:
Removed the test variables out of the function and added them as parameters
Modified the Parameters a bit:
- $file now is mandatory (the function simply will not run without it)
- The first parameter will be interpreted as the file path
- The second parameter will be interpreted as Servertype
- $Servertype can only be CAS, MBX or ALL. No other values accepted
- $Servertype will be set to CAS unless another servertype is specified
you if/ifelse/else construct has been replaced with a switch (I vastly prefer them but they do the same functionally
I removed the unnecessary temporary storage variables.
Appended a placeholder scriptblock at the end that shows you how to iterate over each set of items and select a new server each time.
I hope this helps you in your quest to conquer Powershell :)
Cheers,
Fred
There's no place like 127.0.0.1

Using JDBC Persistent Manager for Tomcat across multiple Servers

Sorry if I word this question incorrectly, but I hope you can get the gist of it. Basically, I have a web application that will be running on 2 different machines. When too many users are on one machine, they are switched over to another machine (load balancing). If I use JDBC (or file) Persistance Manager to store sessions, what happens when a user is switched between machines? If both machines use the same settings for the Persistance Manager, when a user has just been moved to a new machine, will it be able to load the session from the DB? (since it should have its sessionID). If you can not do this, is there a way to do it?
Thanks!

Sorry if I word this question incorrectly, but I hope
you can get the gist of it. Basically, I have a web
application that will be running on 2 different
machines. When too many users are on one machine,
they are switched over to another machine (load
balancing). If I use JDBC (or file) Persistance
Manager to store sessions, what happens when a user is
switched between machines? If both machines use the
same settings for the Persistance Manager, when a user
has just been moved to a new machine, will it be able
to load the session from the DB? (since it should
have its sessionID). If you can not do this, is
there a way to do it?
Thanks!Session ids are unique and cannot be transferred between different servers... Wise web servers supports load balancing and should be able to transfer/store session without your special code. If you still keen to write transfer code yourself you have to:
1) Store not only session id, but also all content of session (including some virtual (your) session id
2) Transfer (i.e. create a copy) stored session content to another machine
Paul

SFSB Instance Sharing across multiple servers/SFSB failover practices

Hello:
My question is in two parts. I have spent a great deal of time searching the forums without a satisfactory answer, so I thought I'd post my question directly.
1) I have two clients that can potentially talk to two different servers, but they both need to interact with the same instance of a SFSB. For example, the first client calls the SFSB and causes it to save some state in its instance variables. The second client connects to a different server (because of a "network dispatcher" load-balancing architecture), but needs to use the same instance of the SFSB that the first client initialized. The two clients will not always talk to different servers, but the possibility exists that they might.
2) What is the proper design pattern for "fail-over" for a SFSB. For example, a client establishes a session, tickles a SFSB and causes its instance variables to contain state, and then WHAMO the application server crashes or becomes unavailable for some reason. We have in place a mechanism to reroute further client request to a second application server, but currently it is a problem because even though the failover is transparent to the client, the backup server creates a new instance of the SFSB and therefore it has none of the previous state information.
I'm thinking that the answer to one of these questions will be the answer to the other.
A little bit of background: this is not a theoretical application. We are building 250+ cars per day, ramping up quickly to 500-650 cars per day. I'm hoping I can solve this problem from an architectural standpoint, without having to modify each individual bean, because we have on the order of 200-300 SFSBs that would have to be changed--not a pretty thing in a production critical application. We have two AIX servers, but one of them is currenlty just a hot standby because we cannot run both of them at the same time because of problem 1) from above. We'd like to be able to run both servers at the same time for load-balancing purposes. Furthermore, if one box fails then all SFSB data will be lost because of the problem is mentioned problem 2) above.
(As a point of clarification, and only because I don't know if this affects any possible suggestions, but the clients do not use remote references to the EJBs. They simply pass "data containers" via HTTP to the server, and this data is passed to the various EJBs and returned back to the client via HTTP Response and in some cases TCP/IP. In either case, we do not use "remote object" references in the most typical sense. The servlet maintains the references to the EJBs.)
I've read things about "session clustering" but have not pinned down the subject. I have the "Core J2EE Patterns" book on order.
Any suggestions or pointers to reading materials would be greatly, greatly appreciated. I also welcome the "what you should have done" variety suggestions.
Thanks!
Regards,
Doug Wilkerson

Doug,
Here are my thoughts, I hope they help.
I don't think there is a possibility to have two different client (different sessions) talk to one and the same SFSB. A SFSB is specific to a users session and cannot be shared.
The way I would tackle this problem is probably by using SLSB which might access either an entity bean or the DB directly. This way, you might cause DB overhead, but you can share the data between clustered servers and the users will work with the correct data.
About the second question, I don't really now a pattern to provide fail-over for SFSB. To my opinion that is the weakest side of SFSB (beside all the load-balancing that needs to take place).
Hope this helps.

Packaging and deploying jax ws (webservice) in multiple servers

I am a java developer and new to JAX-WS.
i got one requirement to create a web service using jax-ws, packaging using ant build and deploying it in JBOSS and WEBSPHERE server.
The process which i followed to create a web service below:
     1) created a web service class using @webservice annotation
     2) created a client side artifacts using wsimport which is provided by Jdk and created a war and deployed it jboss.
     3) wsdl is getting generated while deploying a war using a URI - (http://localhost:8080/mywebapplication/routing?wsdl)
     4) create client class to call the webservice. everything is working fine for me.
Need your expert input for the following below:
     1) if i write the ant build script to package the client stubs, how i can use wsdl location in wsimport ant task. should i use URI (wsdl="http://localhost:8080/mywebapplication/routing?wsdl") or
(wsdl="d:/route.wsdl")? which is the best practice?
     2) i want to deploy my webservice in JBOSS and WEBSPHERE in different machine and different port no?
     for e.g
*     http://ip1:port1/mywebapplication/route?wdl*
*     http://ip2:port2/mywebapplication/route?wdl*
*     http://ip3:port3/mywebapplication/route?wdl*
     how to mention dynamic ipaddress and port no while running ant build script?
     how to change the wsdl location and port number in generated wsdl and RoutingService client stubs class dynamically? (dont want to change soad address location manually)
*     Do i need to use wsgen to generate server stubs?*
*     Need your inputs in packaging and deploying jax ws in multiple servers.*
Thanks in advance.

how to change the wsdl location and port number in generated wsdl and RoutingService client stubs class dynamically? (dont want to change soad address location manually)
Your client stub should look like that...
<code>
@WebServiceClient(name = "MyClientStub", targetNamespace = "http://www.openuri.org/", wsdlLocation = "http://localhost:8080/MyClientStub/MyClientStubProxy/#%7Bhttp%3A%2F%2Fwww.openuri.org%2F%7DMyClientStub?wsdl")
public class MyClientStub
extends Service
public MyClientStub(URL wsdlLocation, QName serviceName) {
super(wsdlLocation, serviceName);
</code>
You can use the constructor above, like that...
<code>
URL baseUrl = MyClientStub.class.getResource(".");
URL url = new URL(baseUrl, "http://your-server:your-port-no/MyClientStub/MyClientStubProxy/#%7Bhttp%3A%2F%2Fwww.openuri.org%2F%7DMyClientStub?wsdl");
     MyClientStub stub = new MyClientStub(url, new QName("http://www.openuri.org/", "MyClientStub");
</code>

Deploy project to multiple servers

Hi,
Does anyone know if it is possible to deploy a process to multiple servers at once (from one central point)??
In our test environment we only have a few services running, but when we go live, this number would increase. Therefor it would be a time-saving point if we could impress our clients with such a reason.
Kind regards,
RenÃ©

I would implement such a deployment configuration using ant by extending the default build.xml generated by ant. ant has a lot of built-in task that can help with remote deployment. -Edwin

Rollback Multiple Patches on Multiple servers as Jobs

Hello Everyone, This community has helped a lot to me at times when needed , I am glad that I am part of this.Have stuck in a task and requires your helps and suggestions again.Requirement :I have to rollback or uninstall a list of patches or hotfixes across multiple servers.Inputs given to me is a CSV as drafted below:rollback.csvCI,Hotfix
Serv1,KB2968295
Serv1,KB2966827
Serv2,KB2972101
Serv2,KB2972280
I am grouping and splitting the CSV's based on server names in the Powershell script:Serv1.csvServ1,KB2968295
Serv1,KB2966827
Serv2.csvServ2,KB2972101
Serv2,KB2972280Now I have to start remote jobs on serv1 and serv2 to rollback the given hotfixes.Powershellfunction Uninstall-Hotfix {[cmdletbinding()]param($computername = $env:computername,[string] $HotfixID) $hotfixes = Get-WmiObject -ComputerName $computername -Class Win32_QuickFixEngineering...
This topic first appeared in the Spiceworks Community

Hello Everyone, This community has helped a lot to me at times when needed , I am glad that I am part of this.Have stuck in a task and requires your helps and suggestions again.Requirement :I have to rollback or uninstall a list of patches or hotfixes across multiple servers.Inputs given to me is a CSV as drafted below:rollback.csvCI,Hotfix
Serv1,KB2968295
Serv1,KB2966827
Serv2,KB2972101
Serv2,KB2972280
I am grouping and splitting the CSV's based on server names in the Powershell script:Serv1.csvServ1,KB2968295
Serv1,KB2966827
Serv2.csvServ2,KB2972101
Serv2,KB2972280Now I have to start remote jobs on serv1 and serv2 to rollback the given hotfixes.Powershellfunction Uninstall-Hotfix {[cmdletbinding()]param($computername = $env:computername,[string] $HotfixID) $hotfixes = Get-WmiObject -ComputerName $computername -Class Win32_QuickFixEngineering...
This topic first appeared in the Spiceworks Community

User Account Authentication across multiple Solaris servers - Best Practice

Hi,
I am new to Solaris admin and would like to know the best practice/setup for authenticating user accounts across multiple solaris servers.
Currently we have 20 - 30 Solaris 8 & 10 servers which each have their own user accounts setup. I am planning to replace these with a similar number of Solaris 10 servers and would like to centralise the user accounts and their authentication.
I would be grateful for any suggestions on the best setup and any links to tutorials.
Thanks
Jools

i would suggest LDAP + kerberos, LDAP for name lookups and krb5 for auth. provides secure auth + extensable directory for users and other apps if needed. plus, it provides a decent spring board to add other unix plats into the mix since this will support any unix/linux/bsd plat. you could integrate this design with a windows AD env if you want as well.
[http://www.sun.com/bigadmin/features/articles/kerberos_s10.jsp] sol + ldap+ AD
[http://docs.lucidinteractive.ca/index.php/Solaris_LDAP_client_with_OpenLDAP_server] sol + ldap (openldap)
[http://aput.net/~jheiss/krbldap/howto.html] sol + ldap + krb5
now these links are all using some diff means, however they should give you some ideas as to whats out there. sol 10 comes with suns ldap server and you can use the krb5 server which comes with it as well. many many diff ways to do this. many many more links out there as welll. these are just a few.

How to deploy across multiple mid-tier instances

I was hoping someone may be able to point me in the right direction. We have two portal/webcache mid-tier instances on release 10G AS 9.0.4.2. On the ias_admin home page I tried to create a cluster and add the two instances to a cluster but it won't let me do it for a portal type install. If that is the case, how do people handle deploying such things as portlet providers and data sources across multiple mid-tier instances? Here is the concern from our Portal admin:
As discussed, the inability to cluster the mid-tiers will cause issues in production as we try and keep deployed portlet providers with their required configurations and datasources in synch. While deploying and configuring 1-2 mid-tiers for a given portlet manually is do-able, the chance for out of synch components or configuration settings is amplified for each additional mid-tier. If we manually deploy 5 mid-tiers and accidently mistype the datasource for example, we'll have a random error that will occur once requests are attempted to be serviced by that mid-tier. This will make troubleshooting difficult. We really need some way to deploy and configure settings one time and have these items propagated to all the other mid-tiers.
What is the best way to handle this scenario?
Regards and thanks for any info,
Chris Schumacher
Embry-Riddle Aeronautical University

Jar files are not stored on the file system
Temporary files are held in bpel/domain/default/tmp folder, whereas jar files in the dehydration store for clustered deployment.
If you configure BPEL (not AS) cluster - files will be propagated to all nodes.
MJ

How to deploy the same WebService to multiple servers

Hi
I have to deploy the same webservice + its clients to multiple servers. However, the WS URL is hardcoded in its descriptor, as well as in the client, so it means that I have to rebuild everything each time I want to deploy it to a new server.
How can I set the URL dynamically at runtime?
Thanks a lot
Jean-Noel

Hi There,
I think what you can do is once you create your webservice , it has a property called
SOAP RPC URL which you can edit before you create the wsdl and the client.
Hope that helps
Kishore

Need help: Deployment of application on multiple admin servers in a cluster

Forwarding this to the weblogic.developer.interest.clustering group as well:
          Hi,
          I have created two admin servers and one managed server on each of them. Then I have added these two managed servers to both the admin servers.
          So I have two admin servers and a cluster having two managed servers.
          Now, if I deploy through one of the admin servers to the cluster cotaining both managed servers, i can see the deployment happening when I log on to the admin server from which I tried the deployment. IF i log onto the other admin server I do not see the deployment happening.
          Interestingly, if I restart both the managed servers from the second admin server, i can see the deployment from the same one but now, if I loginto the first admin server, I see the deployment missing!
          Is this a normal behaviour? Is there any way in which we can see the deployment from both the admin servers?
          Thanks in advance,
          -Sen

Why do you have two admin servers? How many config.xml files exist? Are both admin servers pointing to the same domain if so how is the domain shared? Are both admin servers on the same box? Are they supposed to be the same domain? I'm just trying to understand why it is configured this way.
          -Jesus

Syncing Forms Across Multiple Application Server Servers?

Hi Guys,
I was hoping someone could point me in the right direction. We recently brought up multiple servers running Application Server 10.1.2.3 for High Availability of our forms and reports. My question is, is there a way to keep the forms files synced? With IIS for example, I have written a batch file that will go check for modifications on a source server and then sync any destination servers that are out of sync. However with Application Server, you cannot simply copy files over because if they are in use they are locked.
Would anyone happen to know of any kind of solution for keeping multiple Application Servers synced?

What we do is use a Load balancer with Multiple App severs. To keep the forms correct we take one out at a time off peak and update and do this round robin until they match.
Best Regards
mseberg

SOA 11g Composite Deployment across multiple Instances: Best Practice

Hi,
We have a requirement where we need to deploy the composite acrocss mutilple instances(DEV,TEST,Production) without JDEV.
We are using SOA11.1.3.3(cluster) and linux OS.
Pls suggest me what is the best practice to deploy the SOA composite.
Thanks,
AB

Why there are different ways to deploy the composite in different environment? Depending upon the environment, it's business importance increases and hence access to developers get more restricted and hence there are many ways for deploying. If you are developing an application, you would not like to export a SAR and then login to EM console to deploy it. For a developer it is always very convenient to use IDE itself for deployment and hence JDev is preferably used for Dev instances for deployment.
Once development finishes, developer will check in the artifacts into version control system and if you want to deploy to a test instance then you have to check out the stable version, compile it and package it and then only you can deploy. Hence for test instances, ANT is the preferable mode for deployment. (Remember that developers may not be able to connect to Test environment directly and hence deployment from JDev is not possible)
Once a configuration gets tested in Test env, it's SAR should be checked in into version control system, so that it would not be required to recompile and repackaging of it. This will also make sure that any artifact which is not tested on Test instance, must not go to higher instances (like UAT/PROD). Now in Pre-Prod/UAT/Prod, you may simply access the EM console and deploy the SAR which is already tested in Test instance. Remember that there will be very limited access to such critical environments and hence using Role based access of EM it would be very easy to deploy the resources. Moreover, it is more secure mode of deployment because only those users which have appropriate priviledge, will be able to deploy, and it would also be easier to track the changes.
What is the proc and cons if we use only one way to deploy the composite across the Instances...As such there is no major pros and cons. You may use EM for all environments but it may be a little discomfort for developers/deployers of test environment. You may also use ANT for all the environments but it is not suggested until and unless you have a very good and secure process in place for deployments.
Regards,
Anuj

Cluster Apex MS's across multiple nodes for load balancing?

Can Cluster Apex MS's across multiple nodes for load balancing? If Yes/No, any supportive doc's will be much appreciated.
Here is what I did ..........
I tried multiple MS's on different nodes for Apex Domain (clustered)
Deployed apex.war, i.war with targets pointing to cluster.
Apex listener techstack is shared filesystem $HOME/apex, where apex-config.xml and bdb are available
Anyone of the MS's whichever started up first is locking up bdb and 500 server shows up when internal workspace is being launched with host specific url, where as it works fine for the host which actually locked up bdb (first MS that was started)
2nd MS shows errors as below in log files ..
Caused By: com.sleepycat.je.EnvironmentLockedException: (JE 4.0.103)$HOME/apex/bdb The environment cannot be locked for single writer access. ENV_LOCKED: The je.lck file could not be locked. Environment is invalid and must be closed.
Its expected behavior until here .....
++++ I tried something to get it working ++++
Whilst both MS's are up and running, delete $HOME/apex/bdb but let apex-config,xml be as it is...now the internal workspace urls for both hosts work fine. I logged into host specific urls and navigated, created/edited users.,etc and it is all looking good but it did not create new bdb directory under $HOME/apex ...!!
Having said its working fine, the same issue repeats after the MS's bounce. So I did put a command line to delete bdb dir once the MS comes up to avoid the issue but really not sure if this is the right way at all?
Geek's ...awaiting your advice!!

Hey there,
I managed to fulfill my requirement..
If its a cluster on same machine or across machines, this should work
1. Login to machine, cd $DOMAIN_HOME
2. mkdir -p Apex_lsn_config/AdminServer Apex_lsn_config/<MS1> Apex_lsn_config/<MS2> # MS1 and MS2 are the Managed Server names as appropriate
#If you are planning for cluster spawning MS's across machines, make sure you create the dir's on step 2 for each machine respectively. (in my case $DOMAIN_HOME is not shared)
3. Copy apex-config.xml from the /tmp/apex or whatever location you have it currently to Apex_lsn_config/<MS1> Apex_lsn_config/<MS2>
4. cd $DOMAIN_HOME/bin; cp -p SetDomainEnv.sh SetDomainEnv.sh.orig #Backup the file
5. Append -Djava.io.tmpdir in SetDomainEnv.sh as below for JAVA_OPTIONS # Do it on both machine if you are not sharing DOMAIN_HOME and planning cluster across machines
-Djava.io.tmpdir=$DOMAIN_HOME/APEX_CONFIG/${SERVER_NAME}
Hint: Search for "iterativeDev" and append the same line with -Djava.jo.tmpdir
6. Modify "java.io.tmpdir" from the web.xml file of apex.war as below and re-deploy the war
<context-param>
<param-name>config.dir</param-name>
<param-value>${java.io.tmpdir}</param-value>
</context-param>
7. Bounce Weblogic Admin and Manged Servers. Make sure to tail the Managed Server log to see apex-config.xml is picked from the new location.
8. Brew a Coffee for yourself :)
- You find the instructions on creating a cluster from weblogic documentation, the steps mentioned above are only to overcome the bdb locking issue whilst creating a cluster.
Did it help?
Edited by: Oratime on Mar 25, 2013 2:44 AM

Deploy an Applet across multiple servers

Similar Messages

Maybe you are looking for