Because some other applications deployed on that server are now not accessible. Other developes always ask our DBA to deploy the applcations to the WebLogic server, but I always want to do that by myself in testing environment, so my boss thinks it is my fault to mess up testing environment. I just wonder how I can argue with my boss to explain that is the testing environment, it should let developers to work on it. it is too much burden to ask DBA to deploy my app during testing process. Any suggestion how to explain to my boss? thanks.
Your testing environment is shared — one messed up and others cannot use. DBA 把门花点时间，troubleshoot 加backout error 花更多的时间，而且别人在这期间不能用。这就是为什么。不懂为什么你犯了错还要argue.
I am the person who setup the testing sever on testing environme
I actually built a new testing server and made 90% applications accessable in less than 2 hours. Only one application I haven't got time to deploy it because DBA changed the password.
Yes, today I setup another WebLogic server but still in the same
I will try to get the ownship to handle the configuation/deployment in testing environment. I can prove DBA has no knowledge to handle this work. He has zero knowledge on application server configuation. Will have group meeting next Tuesday.
我老板以前全让我setup everything on that machine. 那DBA是按照我做好的setting再bui
do the same setting on prod machine.
Also I sent email to DBA first to ask for help. My application was developed on my local mchine which has been tested succesfully againt Tomcat and Glassfish. But our production server is WebLogic. So I deployed to our testing WebLogic server to do final testing. There is issue regarding SSL, but DBA has no idea so he didn't resposne my email which I cc to my manager as well. 2/4/2020 was the deadline and if the issue was not fixed before 2/4/2020, then the current running application will have problem. I have to deploy the new feature into the PROD on 2/4. Since no response from DBA, I login to the sever (which all developers have permission to login), and worked on the issue. Yes, in my last test step, something accidently happened which causes the server not function as expected. After incidence occurred, I have created another new domain and have all the apps running on that new domain.
Yes, I will mention in our next meeting, we need backup on this testing machine. Just in case something is wrong.
It's a testing environment, you fixed it pretty quick, and you are the one who set it up initially. I assume your intention is to move fast and get things done, but not prove DB is useless.
If so, people like you are the 'doers' in the team, I doubt any managers will actually blame you for doing too much. Maybe he just gives you some guidence to how to utilize DBA in the future.
Just acknowlege you made a mistake of bringing down the server, not a big deal. You should work with your manager or team on the next step, how to make this procedure more efficient. Maybe build a container based environment and everyone has its own database, etc.
My boss talked to me today and asked me to write down detailed s
The older version is not compatible with java 8. So no meaning to recover the older server. It only takes me very short time to install WebLogic12c. Then I re-deploy all the applications to the new server. It is not hard at all.
Because some other applications deployed on that server are now not accessible. Other developes always ask our DBA to deploy the applcations to the WebLogic server, but I always want to do that by myself in testing environment, so my boss thinks it is my fault to mess up testing environment. I just wonder how I can argue with my boss to explain that is the testing environment, it should let developers to work on it. it is too much burden to ask DBA to deploy my app during testing process. Any suggestion how to explain to my boss? thanks.
Your testing environment is shared — one messed up and others cannot use. DBA 把门花点时间，troubleshoot 加backout error 花更多的时间，而且别人在这期间不能用。这就是为什么。不懂为什么你犯了错还要argue.
I actually built a new testing server and made 90% applications accessable in less than 2 hours. Only one application I haven't got time to deploy it because DBA changed the password.
each time, I have to give him very detailed instruction. Then he just perform copy/paste function.
I will try to get the ownship to handle the configuation/deployment in testing environment. I can prove DBA has no knowledge to handle this work. He has zero knowledge on application server configuation. Will have group meeting next Tuesday.
testing env. 可以算作一种mock deployment，为production deployment做准备，如果老板同意你可以同样在production这些操作，你确实可以争取，否则以后出现问题需要解决，除了你谁都不懂，你又没有ownership，没法深入调查。
公司项目非常重视team work，每个人遵守相同的规则是起码的要求，你的队友即使是蠢猪，你也只能生气，不能独揽。DBA如果不懂，你写一份非常详细的document，备案并在以后的日子里面不断完善中间的细节，成为这方面的bible，年底写进你的performance review，比你现在的作为要好很多。
星期一与头儿谈，道个把工作耽误了的歉，然后集中精力提出改进方法，详细解释你的计划，你的计划对公司的好处，以及你需要的技术支持。
题外的话：我在职场接触到的人中，可以说中国人是做事最少出错的群体，也是最不肯认错的群体。在升职长薪的评估会上，经常会听到对国人组员的评价：“他这个人做事很好，就是不肯认错”。从前处于好心，经常提醒一下。得到的回答往往是：肯定是XXX说的，我从来不会不认错，那件事根本不是我的错。。。”
其实，认错是职场进取的能力之一。天下没有不出错的人，不出错的人是不做事的人。很多时候：
1，认了错，找出原因，下回再犯同样错误的的机会少好多。
2. 管理也是人，对组员也喜欢报喜不报忧，现在人们不会用: you made a mistake. 连 mistake 一词都不用，用issue/error。遇到一位不认错的组员，真是头都大了三圈。记得从前有位不认错的同事，谁也不愿意和他谈，出了错儿用电邮沟通，最后解聘的时候，电邮都成了证据。
3. 实在不愿意认错，可以用：I'm sorry （something happend）。比如同事出了车祸：I'm sorry you had an accident。
当然，原则性的错误，不在本帖的讨论范围。
我们这儿不管工作方面出错还是不出错，你敢破坏规则而没有上级批准，直接fire都可能，否则这么多员工，每天醒来你都不知道可能发生什么。
她的关键问题不是不肯认错，而是根本不觉得错。
do the same setting on prod machine.
Also I sent email to DBA first to ask for help. My application was developed on my local mchine which has been tested succesfully againt Tomcat and Glassfish. But our production server is WebLogic. So I deployed to our testing WebLogic server to do final testing. There is issue regarding SSL, but DBA has no idea so he didn't resposne my email which I cc to my manager as well. 2/4/2020 was the deadline and if the issue was not fixed before 2/4/2020, then the current running application will have problem. I have to deploy the new feature into the PROD on 2/4. Since no response from DBA, I login to the sever (which all developers have permission to login), and worked on the issue. Yes, in my last test step, something accidently happened which causes the server not function as expected. After incidence occurred, I have created another new domain and have all the apps running on that new domain.
Yes, I will mention in our next meeting, we need backup on this testing machine. Just in case something is wrong.
1. 如我楼上的帖子所说，一般来说，认错的目的是改正错误，防止以后再犯。不是为了惩罚谁。所以认了不过是面子上下不来的错儿，认了比不认好。而且认错，只是一句话，重点是如何将以后的事情做好，出的错反而不重要了。不认错要解释很多，越解释出错的印象越深。
2. 如果错误到了要解聘的地步，认这种错儿要慎重对待。
3. 如果头儿希望组员出成果，不出预期的成果就是错儿。但预期不代表事实，这种错儿认了，接着就要造假了。这是我所说的原则。
It's a testing environment, you fixed it pretty quick, and you are the one who set it up initially. I assume your intention is to move fast and get things done, but not prove DB is useless.
If so, people like you are the 'doers' in the team, I doubt any managers will actually blame you for doing too much. Maybe he just gives you some guidence to how to utilize DBA in the future.
Just acknowlege you made a mistake of bringing down the server, not a big deal. You should work with your manager or team on the next step, how to make this procedure more efficient. Maybe build a container based environment and everyone has its own database, etc.
好的时候，你出的错都可以承认改正，不好的时候，就可能被盯上，像下面ID加州lalin的话，容易躺枪，成为替死鬼挡箭牌之类。我们公司最近大变动，解雇一个员工，他的做法，我们以前忙的时候，几乎都这么做，现在变成违法公司制度的安全问题，不知道他得罪谁了。所以楼主如果老板只同意你，但其他人都不这么做，留心做个证明啥的，以后出错也仅仅限于技术或者交流之类的失误。
认错本身没什么可争的，你说什么我都同意。
The older version is not compatible with java 8. So no meaning to recover the older server. It only takes me very short time to install WebLogic12c. Then I re-deploy all the applications to the new server. It is not hard at all.