How to deploy config files to managed servers

We have several configuration files that are used by our EJB application at
startup. Is there a way to automatically deploy these configuration files
to the managed servers. Right now, we are forced to FTP to files over to
the managed servers as part of the deployment process. It would be nice if
there were an easier way.
Randy Ott

why cant you include them inside your ejbjar as resource files ?
prasen
Nitin Shenoy wrote:
>
Guess no one replied!!
"Randy Ott" <[email protected]> wrote in message
news:3b67022e$[email protected]..
We have several configuration files that are used by our EJB applicationat
startup. Is there a way to automatically deploy these configuration files
to the managed servers. Right now, we are forced to FTP to files over to
the managed servers as part of the deployment process. It would be niceif
there were an easier way.
Randy Ott

Similar Messages

How to Deploy sca files in CE

I have downloaded an sca file for 7.1 sp3 but how do you deploy it, the SDM has been removed from this version and I am struggling to find documentation on how to deploy sca files.

Hi ,
i do this way
1. login os ( host of CE installed system)
2. cmd
3. telnet
4. o localhost 50008 note: "00" is the instance
5. user -> administer user
6. password>****
7. deploy d:\<path><SCName.ear on_deploy_error=stop
ex: deploy d:\Temp\new\XYZABC.sca on_deploy_error=stop
Regards
Shridhar Gowda
p.s: pls close the therad if it solved.

How to deploye .war files in SOA_Server1 ?

Hi,
I was created Auto Generated Task form for Human Task in 11G.After that how to deploye .WAR files manually in
"Infra -Soa(Soa_srerver1)" .Plz help me now

When you auto-generated the UI it would have defaulted to creating a web app project in your application. When you deploy the BPMN process, there are three steps in the wizard:
1. Deploy Configuration
2. Task flow deployment
3. Select Server
In step 2 you can select some of all of the UI projects in the app and deploy them as part of deploying the composite. The build/deploy process will automatically create the war(s) and ear file. Once they're deployed, you can leave them un-selected to avoid redeploying them each time you just change the process definition. If you make changes to the UI, you can just select them again during deployment and select the option to overrwrite the EAR.

How to deploy sca files and navigate to web services?

Hello All,
Installed SAP MDM 7.1 and also got sapmmc on my desktop.. Wondering how can I deploy sca files and how can I get web service navigator page to see web services? Any light on this?
Thanks
Rajeev

Hi,
Please find details below:
1. How to deploy SCA files:---> You need to deploy these .SCA files through JSPM on any JAVA AS server (7.0 or 7.1 depending upon .sca files version you have). make sure your MDM version should be minimum 7.1.02.51.
2. How to get webservice Page:--> To Access web service page using the following link
http://<Netweaver Java AS Machine>:<NetWeaver Java AS HTTP port>/webdynpro/dispatcher/sap.com/tcmdmwsgeneratorui/WSGenerator
For more details please check [this|http://help.sap.com/saphelp_nwmdm71/helpdata/en/45/018c03166a0486e10000000a155369/frameset.htm] link.
Regards,
Shiv

Wlw-runtime-config.xml & two managed servers

I have a problem with WSDL generation and WebLogic workshop in a
cluster.
I'm using a wlw-runtime-config.xml file to ensure that my web service
generates the correct url for it's endpoint.
The problem I have is that I have two managed servers on one physical
box, one listening on port 7010, the other on port 7030.
The wlw-runtime-config.xml file is placed in the domain root, and I
only seem to be able to specify a single port/dns name in the config
file.
My web service request will come in through the IIS plugin, hit one of
the servers, generate the WSDL containing the port information, which
may or may not be correct for the WLS instance that it has actually
been proxied to.
If that is correct, how do I handle the fact that the web service is
deployed across all cluster members, two of which are hosted on one
single machine.
Am I missing something?
Pete

Hi Pete,
I'm assuming you have seen the "how do i" on this topic [3], plus the
information on how to setup a cluster [1].
Your missing link may be the way your DNS entry is configured for the
cluster. See the docs [2] on this topic, but you will need to specify
the multiple nodes something like this:
DNSName1:port1,DNSName1:port2,DNSName1:port3
Note the folks in our super support group will be best suited to assist
your efforts.
Regards,
Bruce
[1]
http://e-docs.bea.com/wls/docs81/cluster/setup.html#684345
[2]
http://e-docs.bea.com/wls/docs81/cluster/setup.html#714310
[3]
http://edocs.bea.com/workshop/docs81/doc/en/workshop/guide/deployment/howClusterDeployment.html
Pete wrote:
>
I have a problem with WSDL generation and WebLogic workshop in a
cluster.
I'm using a wlw-runtime-config.xml file to ensure that my web service
generates the correct url for it's endpoint.
The problem I have is that I have two managed servers on one physical
box, one listening on port 7010, the other on port 7030.
The wlw-runtime-config.xml file is placed in the domain root, and I
only seem to be able to specify a single port/dns name in the config
file.
My web service request will come in through the IIS plugin, hit one of
the servers, generate the WSDL containing the port information, which
may or may not be correct for the WLS instance that it has actually
been proxied to.
If that is correct, how do I handle the fact that the web service is
deployed across all cluster members, two of which are hosted on one
single machine.
Am I missing something?
Pete

How to deploy EAR file in Tomcat?

Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.

Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
     Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
     Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation

WAR files on managed servers

I have a question about placing new war files in production. First, why
does WebLogic recommend AGAINST using auto-deploy in production? Is it
for security or stability and what are those arguements?
Second, do I need to move the actual war file to the managed servers
(seperate hardware from the domain admin)? Does it always read the war
file from the domain admin, or will it also read it from it's local
disk? If it does also read locally, which one would take priority? I am
looking for the most reliable way to move new war files into production,
but I do not want to be manually moving files around to the managed
servers if they are never being used.

Another option, although not near as good as a stand-alone tool, I think you could put in the WSDL address for a particular managed server in the Admin Consoles test client. For example, on my machine with the example's server, that is bound to http://localhost:7001/wls_utc/
The one issue might be if you front-end address that gets put in your WSDL doesn't match the managed server that you want to test, then you might need to edit it first, which is probably a pain.
The test client used to be a stand alone deployment (at least I think it was in the 9.2 days), but it appears to be part of an internal application now from the docs:
http://edocs.bea.com/wls/docs103/deployment/managing.html#wp1021614

Replicating files across managed servers

          Hi there,
          I have a clustered environment with say 3 managed servers. One of the managed
          server (e.g. A) will try to download some files from a remote location periodically
          (for caching purposes).
          So, when a client tries to connect to the cluster (any of the managed server depending
          on the load balancer), I am supposed to serve the files to the client. My question
          is, say for e.g. server A downloaded the files to save in its local directory,
          how do I make these files replicated to other server as well. Or, how do I automatically
          direct the client to server A only when fetching the document is required?
          Suggestions? Many thanks in advance....


          Hi Oscar,
          Many thanks for your feedback and solution, I could give it a try... :)
          "Oscar Cristobal" <[email protected]> wrote:
          >
          >Hi.
          >I had pretty the same problem.
          >In my application, users can upload images.
          >If these images are in server 1, and one user tries to access these images
          >from
          >server 2, we get the same problem.
          >So we solved the situation like follows:
          >1.- When a user uploads an image, this image is saved in database.
          >2.- There is a daemon, running in every server, that checks (every 30secs)
          >if
          >there is any image in the database that is not at the server. If not,
          >it downloads
          >the image from the database. After all, it registers at the database
          >that server
          >X got the image.
          >3.- When all servers downloaded the image, daemon deletes it from the
          >database.
          >
          >That is my solution. I dont know if it can be used by you, because maybe
          >this
          >solution is only ok for low number of file updates.
          >I would like to know if somebody can provide some better solution.
          >
          >Thanks in advance
          >Oscar Cristobal
          >
          >
          >"Stephen S." <[email protected]> wrote:
          >>
          >>Hi there,
          >>
          >>I have a clustered environment with say 3 managed servers. One of the
          >>managed
          >>server (e.g. A) will try to download some files from a remote location
          >>periodically
          >>(for caching purposes).
          >>
          >>So, when a client tries to connect to the cluster (any of the managed
          >>server depending
          >>on the load balancer), I am supposed to serve the files to the client.
          >>My question
          >>is, say for e.g. server A downloaded the files to save in its local
          >directory,
          >>how do I make these files replicated to other server as well. Or, how
          >>do I automatically
          >>direct the client to server A only when fetching the document is required?
          >>
          >>Suggestions? Many thanks in advance....
          >

How TO DEPLOY JAR FILES INTO XI Server using SDM

Hi XI Gurus,
   im working on adapter development. we have created jar file in NWDS.
   now going ahead to deploy into XI server through SDM.
   can we deploy jar files directly into xiserver through SDM. or it needs to convert to any other formate like EAR, SDA. then how would i convert to SDA.
i any have clear idea on this... pls throw the ways how to convert........
           JAR File to EAR format
           JAR file to SDA format
           EAR file to SDA format
   can any one explain the procedure step by step how to convert jar file into deployment archive file in order to succesfully into XI server.
          thanks i advance. points will be rewarded.
Regards
Rajesh

Hi Rajesh,
JAR file in itself in not deployable.
So v need to envelop this jar file into an EAR file and then v deploy this EAR file on SDM.
Creating Jar
Inside NWDS --> Windows --> Open perspective --> J2EE Development --> right click on ur proj --> Build EJB Archive
Converting .EAR file to .SDA
Converting .EAR file to .SDA
Regards,
Prateek

How to Deploy HTML file in embedded OC4J Server

Hi,
I have a problem with deploying the HTML file.
How to deploy a HTML file in embedded oc4j server.
I'm running this in a Standalone and JDeveloper9i version.
I don't know where to deploy and how to deploy ?
Thanks
James

Hi Deepak,
I tryed that but i was NOT successful.
I'm getting 404 error page could not find in the Server.
Any other idea ?

How to deploy WAR file in tomcat.?

Can anybody please provide step by step information of deploying war file to Jakarta tomcat without IDE.
I am working on Windows XP with jakarta tomcat 4.1.30.
Thanks in advance.
Regards,
Aman Aggarwal

See if tomcat runs as a service in your operating system. If you can locate it, you can set the start type to automatic. A very crud way is to run the tomcat startup file from autoexe.bat.
I don't know how to do this in Linux. Here is a link for tomcat 6. Maybe it is the same in tomcat 4
[http://tomcat.apache.org/tomcat-6.0-doc/setup.html]
Edited by: nirvan on Dec 29, 2008 9:15 AM

How to deploy osb projects into managed server in weblogic

i am new to osb
i have a doubt
i created a managed server in weblogic admin console, it was running fine ,but i need to know how to deploy my osb projects in that new manged server.As of now it is deployed in http://localhost:7001/sbconsole

I think you need to extend the domain instead of creating the managed instance manually through Admin console. By default when you create a domain using OSB domain template, it deploys all of the applications needed automatically to all the instances. If you are trying to do it manually, then you need to follow the documentation to see which applications need to be deployed to use OSB services.
http://docs.oracle.com/cd/E23943_01/doc.1111/e15017/configure_osb.htm#BGBFGBFF
To deploy a project, Login to SB console http://<admin>:<port>/sbconsole > System Administration > Export/Import Resources.

How import/deploy .ept files in Portals

Hi All,
I am trying to integrate RedDot CMS with SAP Portals. Customer has provided two types of files. One with .epa and other one with .ept extension. I could import .epa file using System Admin, however I am not able to deploy/import .ept files. I tried renaming a copy of com.reddot.pct.liveserver.par.ept to com.reddot.pct.liveserver.par and deployed the .par file, I didn't find this deployed .par in the list of creat iview from PAR list. Please someone let me know how to deploy these .ept files.
Satish

Hi,
Did you try to deploy .ept files as .ear files. I believe same procedure shuould work
check the below wiki
https://www.sdn.sap.com/irj/scn/wiki?path=/display/ep/archiving%252bof%252bportal%252bobjects
Koti Reddy

How to install Window service for Managed Servers of a Cluster

Dear All,
          I am preparing a production setup consist of three machines A,B and C. Machines A is the Admin Server which hosts a cluster consist of two managed nodes. I intend to schedule both these nodes, targeted to two different machines (machines B node-b and machine C host node-c), as startup task on daily basis. I have no Node Manager running on machine A, but on machine B and machine C.
          I am only interested to schedule started task for node-b and node-c only. I need to know how to install the Windows services for the node-b and node-c since there are targeted on remote machines. Starting managed server as Win sevice works in the case of standalone managed servers but not sure when it comes to cluster setup.I appreciate if you can throw some light on this question.
          Thanks
          Kris

Krish,
          >Let say I gracefully shutdown both managed servers while >Admin is running. Do you think both these nodes while be >brought up ? I dont think they will come up.
          If you require an automatic restart when the managed server did not enter a failed state you can use the weblogic.Admin utility to ping the servers and kick off a server startup in the normal way with nodemanger see:
          http://e-docs.bea.com/wls/docs81/admin_ref/cli.html
          http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html
          If your servers entered a failed state you can use weblogics self health monitoring.
          >Can we use JMX MBean to start managed servers ?
          Yes.
          As long as the nodemanagers are running you can start the managed servers using scripted commands using the weblogic.Admin class or your own java app using JMX.
          I think you may also be able to use WLST
          http://dev.bea.com/codelibrary/code/wlst.jsp
          hope this helps
          cheers
          Please see the
          Hussein Badakhchani
          www.orbism.com

How to deploy reports to anothe managed Server (Weblogic)

Hi everyone
I would like to know how could i deploy reports to another managed server in weblogic.
When i first installed forms and reports it asked me to where i want to deploy and everything works fine.
But i have created another managed server afterwards and i would like this server to be configured with reports, but it won´t work.
I don´t know if i have to run the installer again selecting this new server or is there another better way to do this.
Thanks for your help
Greetings
Mateo.

I think you need to extend the domain instead of creating the managed instance manually through Admin console. By default when you create a domain using OSB domain template, it deploys all of the applications needed automatically to all the instances. If you are trying to do it manually, then you need to follow the documentation to see which applications need to be deployed to use OSB services.
http://docs.oracle.com/cd/E23943_01/doc.1111/e15017/configure_osb.htm#BGBFGBFF
To deploy a project, Login to SB console http://<admin>:<port>/sbconsole > System Administration > Export/Import Resources.

How to deploy config files to managed servers

Similar Messages

Maybe you are looking for