weblogic的war的deploy的问题

最新推荐文章于 2022-03-24 08:50:37 发布
原创 最新推荐文章于 2022-03-24 08:50:37 发布 · 1.9k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#weblogic #application #服务器 #浏览器 #web

在WebLogic 8.1+sp3开发模式服务器上，从控制台deploy web application modules显示成功，但浏览器浏览为空；将war文件复制到指定目录则可正常浏览。
1、从http://localhost:7001/console的控制台中deploy一个web application modules时，显示delploy成功，可以进入浏览器浏览时，发现是空的。然而用另外一种方法deploy时，即把war文件copy到D:/bea/user_projects/domains/mydomain/applications 时即可以正常浏览，这里服务器当然是开发模式,服务器的版本是weblogic8.1+sp3。
centos7安装weblogic多域
weixin_54104864的博客
05-25 438
复制 /data/www/wlserver/common/templates/scripts/wlst/basicWLSDomain.py 文件到 example_domain 文件夹下，并重命名为 ExampleDomain.py ，该文件将作为创建当前域的脚本文件。在 /data/app/weblogic/domains 目录下建立空的域文件夹 example_domain ，绝对目录为 /data/app/weblogic/domains/example_domain。
deploy Weblogic application with Ant
黄昏微步，星夜默坐
10-31 150
... <taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" classpath="${wls.home}\server\lib\weblogic.jar"/> <wldeploy action="deploy" name="${appName}" target
weblogic 9.2 deploy 基本过程
walkingmanc的专栏
06-25 1574
使用wl 部署应用的时候，首先是需要将应用打包成war格式，然后上传到domain 里面的admin server所在的那个machine上面去。 接着启动admin server 和managed server ，打开控制台登录到 admin server上，通过install 来安装该war包，注意 默认情况下，managed server 使用的是 stage的install方式，也就是说a
脚本实现weblogic deploy
朝九晚九的csdn版
12-02 2158
http://e-docs.bea.com/wls/docs81/deployment/tools.html这几天在调试程序的被很繁琐的undeploy和deploy工作烦的不行.从上面的文章里找到了解决方法, 以下是我脚本的一部分java -cp c:/bea/weblogic81/server/lib/weblogic.jar weblogic.Deployer -adminurl http:
weblogic.Deployer命令使用(初稿)
wengjixi的专栏
05-27 2235
一、weblogic.Deployer所需的环境1、在本机上安装WebLogic Server 软件；2、添加WebLogic Server类到 CLASSPATH 环境变量中，并设置JDK的二进制执行目录到path环境变量中。我们可以使用 setWLSEnv.sh 或者setWLSEnv.cmd 脚本帮助我们设置环境变量如下：然后手动把上面的CLASSPATH变量和path变量的值设置到系统环境...
部署应用到weblogic
xiejx618的专栏
08-19 2554
主要参考资料:http://docs.oracle.com/middleware/1213/wls/wls-developdeploy.htm 假设开发的web应用是myweb.war 自动部署: 1.进入到域(我新建的域在:D:\oraclehome\user_projects\domains\base_domain),双击打开startWebLogic.cmd来启动web
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
最新发布
10-24
</think>### WebLogic应用数据更新失败问题解决方案 (`weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload`) 根据您描述的方法调用位置（`AppDataUpdate.java:43`），该问题通常发生...
Weblogic部署
03-30
5. **监控和调试**：利用WebLogic提供的监控工具（如JMX、JConsole等）检查应用性能和日志，进行问题排查。 在【源码】和【工具】标签的提示下，我们可以知道这篇博客可能涉及了如何将源代码构建为可部署的应用程序...
weblogic 部署war包
12-27
### 部署 WAR 包到 WebLogic 服务器 为了在 WebLogic 服务器上成功部署 WAR 文件，可以采用命令行工具 `weblogic.Deployer` 或者通过管理控制台图形界面完成操作。 #### 使用命令行工具部署 WAR 包 利用命令行方式...
weblogic.Deployer invoked with options: -debug -remote -verbose -noexit -name crm -targets AdminServer -adminurl t3://10.190.252.34:80 -user weblogic -undeploy [WebLogicDeploymentManagerImpl.<init>():112] : Constructing DeploymentManager for Java EE version V1_4 deployments [WebLogicDeploymentManagerImpl.getNewConnection():155] : Connecting to admin server at 10.190.252.34:80, as user weblogic [ServerConnectionImpl.getEnvironment():317] : setting environment [ServerConnectionImpl.getEnvironment():320] : getting context using t3://10.190.252.34:80 [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.domainruntime [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.runtime [DomainManager.resetDomain():36] : Getting new domain [DomainManager.resetDomain():39] : Using pending domain: false [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [ServerConnectionImpl.initialize():193] : Connected to WLS domain: smecs [ServerConnectionImpl.init():183] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@3ed242a4 [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.deriveAppName():143] : appname established as: crm <Jul 17, 2025 8:25:55 AM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating undeploy operation for application, crm [archive: null], to AdminServer .> [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.loadGeneralOptions():718] : Delete Files:false Timeout :3600000 Targets: AdminServer ModuleTargets={} SubModuleTargets={} } Files: null Deployment Plan: null App root: null App config: null Partition: null ResourceGroup: null Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=crm,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false,specifiedTargetsOnly=false,partition=null,resourceGroup=null,resourceGroupTemplate=null,uploadPath=null,specifiedModules=[],removePlanOverride=false,} [BasicOperation.execute():517] : Initiating undeploy operation for app, crm, on targets: [BasicOperation.execute():519] : AdminServer weblogic.management.ManagementException: [Deployer:149001]No application named "crm" exists for operation "undeploy". at weblogic.deploy.internal.adminserver.operations.OperationHelper.assertAppIsNonNull(OperationHelper.java:968) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.updateConfiguration(RemoveOperation.java:191) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.updateConfigurationAndInitializeDeployment(AbstractOperation.java:478) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.execute(AbstractOperation.java:301) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.execute(RemoveOperation.java:84) at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run(DeployerRuntimeImpl.java:1034) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:137) at weblogic.management.deploy.internal.DeployerRuntimeImpl.performDeployerActions(DeployerRuntimeImpl.java:1028) at weblogic.management.deploy.internal.DeployerRuntimeImpl.undeploy(DeployerRuntimeImpl.java:513) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:532) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method)这是建构的什么报错，和application.xml有关系吗
07-18
java weblogic.Deployer -adminurl t3://10.190.252.34:80 -user weblogic -password <pass> -deploy -name crm -targets AdminServer myapp.ear ``` 如果没指定 `-name`，默认会使用 `.ear` 或 `.war` 文件名作为...
weblogic.management.ManagementException: [Deployer:149001]No application named "crm" exists for operation "undeploy". at weblogic.deploy.internal.adminserver.operations.OperationHelper.assertAppIsNonNull(OperationHelper.java:968) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.updateConfiguration(RemoveOperation.java:191) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.updateConfigurationAndInitializeDeployment(AbstractOperation.java:478) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.execute(AbstractOperation.java:301) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.execute(RemoveOperation.java:84) at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run(DeployerRuntimeImpl.java:1034) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:137) at weblogic.management.deploy.internal.DeployerRuntimeImpl.performDeployerActions(DeployerRuntimeImpl.java:1028) at weblogic.management.deploy.internal.DeployerRuntimeImpl.undeploy(DeployerRuntimeImpl.java:513) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:532) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:249) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:439) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.MBeanCICInterceptor.invoke(MBeanCICInterceptor.java:304) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.PartitionJMXInterceptor.invoke(PartitionJMXInterceptor.java:435) at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:355) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.CallerPartitionContextInterceptor.invoke(CallerPartitionContextInterceptor.java:217) at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:327) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:655) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:653) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:646) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:645) at weblogic.rmi.internal.BasicServerRef$2.run(BasicServerRef.java:534) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:531) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:138) at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352) at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337) at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57) at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41) at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420) at weblogic.work.ExecuteThread.run(ExecuteThread.java:360) Unexpected Error Initializing Deployer: weblogic.management.ManagementException: [Deployer:149001]No application named "crm" exists for operation "undeploy". ------------------------------------ ARTIFACT DEPLOYMENT ------------------------------------------------ weblogic.Deployer invoked with options: -debug -stage -remote -verbose -upload -name crm -source /root/.jenkins/workspace/TEST_FN_CRM/dist/crm.war -targets AdminServer -adminurl t3://10.190.252.34:80 -user weblogic -deploy [WebLogicDeploymentManagerImpl.<init>():112] : Constructing DeploymentManager for Java EE version V1_4 deployments [WebLogicDeploymentManagerImpl.getNewConnection():155] : Connecting to admin server at 10.190.252.34:80, as user weblogic [ServerConnectionImpl.getEnvironment():317] : setting environment [ServerConnectionImpl.getEnvironment():320] : getting context using t3://10.190.252.34:80 [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.domainruntime [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.runtime [DomainManager.resetDomain():36] : Getting new domain [DomainManager.resetDomain():39] : Using pending domain: false [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [ServerConnectionImpl.initialize():193] : Connected to WLS domain: smecs [ServerConnectionImpl.setRemote():514] : Running in remote mode [ServerConnectionImpl.init():183] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@3ed242a4 [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.deriveAppName():143] : appname established as: crm <Jul 17, 2025 8:25:59 AM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, crm [archive: /root/.jenkins/workspace/TEST_FN_CRM/dist/crm.war], to AdminServer .> [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.loadGeneralOptions():718] : Delete Files:false Timeout :3600000 Targets: AdminServer ModuleTargets={} SubModuleTargets={} } Files: null Deployment Plan: null App root: /tmp/root/./config/deployments/crm App config: /tmp/root/./config/deployments/crm/plan Partition: null ResourceGroup: null Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=crm,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false,specifiedTargetsOnly=false,partition=null,resourceGroup=null,resourceGroupTemplate=null,uploadPath=null,specifiedModules=[],removePlanOverride=false,} 这个啥错？
07-18
- **`-deploy` 参数的行为**：默认情况下，`weblogic.Deployer -deploy` 会尝试先卸载同名应用，如果不存在就会报 `[Deployer:149001]` 错误。 - **WebLogic 的部署机制**：WebLogic 在部署前会尝试清理旧版本应用，...
weblogic启动失败的常规检查(个人总结)
04-18
自己工作中整理的；weblogic不如tomcat简单好用；动不动就容易启动失败； 文档中有常见启动失败的检查方法；
Weblogic部署项目三种方式
山山来驰的博客
08-28 526
地址：http://www.cnblogs.com/telwanggs/p/7137125.html
在配置HDFS环境时遇到的一些坑
Trony的博客
11-11 522
启动datanode、namenode时未启动 使用jps命令查看，未启动datanode，切换到logs目录下，使用tail命令打开刚刚生成的日志查看错误 一定要查看配置文件，看看有没有单词拼写错误！！！！ 克隆的虚拟机的uuid需要重新生成，不然在hadoop的浏览器端会默认只有一个datanode 在格式化HDFS的时候，关闭datanode，namenode等，不然会导致clusterID不同，找到datanode中的VERSION，更改其中的clusterID与namenode保持一
weblogic部署项目
Because of You！
06-26 790
1.weblogic控制台启动 2.项目打包(打成war包)3.部署项目并测试
Tomcat启动时卡在“INFO: Deploying web application directory ......”的解决方法
热门推荐
Stone的专栏
06-25 10万+
第一次遇到Tomcat在Linux服务器启动卡住的情况，情况很简单，tomcat启动以后卡在INFO: Deploying web application directory ......这句话，具体会卡多久就没测试了。google、baidu都没找到解决方法。 幸亏UCloud的技术支持人员给出了解决方案。 找到jdk1.x.x_xx/jre/lib/security/java.securi
Weblogic应用程序部署指南
死牛崇拜的专栏
08-13 7984
<br />       1.1    部署JAVA EE应用程序<br />将编译好的Web应用程序复制到WebLogic的服务器目录下。例如路径D:/bea10/user_projects/domains/base_domain/autodeploy；<br />这样，当启动WebLogic时候，WebLogic会自动发布该项目。在 WebLogic有个BUG，有时候不能自动发布项目，这时候我们手动修改config.xml配置文件,，配置如下：<br /><app-deployment><br />  
weblogic 9.0.1集群配置
msdnweixiaomsdn的专栏
04-26 1635
WebLogic91 Cluster Configuration  建立集群（ehucluster）在左侧单击“Domain Structure”——“base_domain”——“Environments”——“Servers”先单击左上方的“Lock & Edit”按钮；右侧显示区域中单击“New”按钮，转入（Create a New Cluster）页
【IDEA中Tomcat9部署maven项目打包的war包运行】
可乐的博客
03-24 2080
因为war包需要在Tomca服务器下面运行，所以我们要将项目的war包部署到Tomcat下 1. 首先打包项目，在IDEA的右侧栏上选择maven，先clean一遍项目在install打包 这样IDEA就会生成target文件夹，项目的war包也会在其中 2. 点击调试编辑下拉框，选择编辑配置Edit Configurations… 3. 如果Deployment下面有war包，则先点击➖号删除war包，然后点击＋号 选择Artifact… 4. 先选择自己项目打包的war包，点击ok，这
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值