System Management Best Practice Questions

I help out with IT at a small fire department, town is around 3,000 people. They have about 10 PCs. The only time I really do anything is when someone has a question, or points out a problem. Everything is in place, and works well. However, is there anything
I should be regularly checking on? We have the usual in place: Anti-virus on all PCs, Windows Updates are automatic, all PCs have passwords, Wi-Fi has a password, etc.

AS i know addUser(User user){ ... } is much more useful for several reasons:
1.Its object oriented
2.its easy to write , because if Object has many parameters its very painful to write method with comma seperated parameters

Similar Messages

Best Practices Question: How to send error message to SSHR web page.

Best Practices Question: How to send error message to SSHR web page from custom PL\SQL procedure called by SSHR workflow.
For the Manager Self-Service application we’ve copied various workflows which were modified to meet business needs. Part of this exercise was creating custom PL\SQL Package Procedures that would gather details on the WF using them on custom notification sent by the WF.
What I’m looking for is if/when the PL\SQL procedure errors, how does one send an failure message back and display it on the SS Page?
Writing information into a log or table at the database level works for trouble-shooting, but we’re looking for something that will provide the end-user with an intelligent message that the workflow has failed.
Thanks ahead of time for your responses.
Rich

We have implemented the same kind of requirement long back.
We have defined our PL/SQL procedures with two OUT parameters
1) Result Type (S:Success, E:Error)
2) Result Message
In the PL/SQL procedure we always use below construct when we want to raise any message
hr_utility.set_message(APPL_NO, 'FND_MESSAGE_NAME');
hr_utility.raise_error;
In Exception block we write below( in successful case we just set the p_result_flag := 'S';)
EXCEPTION
WHEN APP_EXCEPTION.APPLICATION_EXCEPTION THEN
p_result_flag := 'E';
p_result_message := hr_utility.get_message;
WHEN OTHERS THEN
p_result_flag := 'E';
p_result_message := hr_utility.get_message;
fnd_message.set_name('PER','FFU10_GENERAL_ORACLE_ERROR');
fnd_message.set_token('2',substr(sqlerrm,1,200));
fnd_msg_pub.add;
p_result_message := fnd_msg_pub.get_detail;
After executing the PL/SQL in java
We have written some thing similar to
orclStmt.execute();
OAExceptionUtils.checkErrors (txn);
String resultFlag = orclStmt.getString(provide the resultflag bind no);
if ("E".equalsIgnoreCase(resultFlag)){
String resultMessage = orclStmt.getString(provide the resultMessage bind no);
orclStmt.close();
throw new OAException(resultMessage, OAException.ERROR);
It safely shows the message to the user with all the data in the page.
We have been using this construct for a long time for all our projects. They are all working as expected.
Regards,
Peddi.

Best practice question -- copy container, assemble it, build execution plan

So, this is a design / best practice question:
I usually copy containers as instructed by docs
I then set the source system parameters
I then generate needed parameters / assemble the copied container for ALL subject areas present in the container
I then build an execution plan JUST FOR THE 4 SUBJECT AREAS and build the execution plan and set whatever is needed before running it.
QUESTION - When i copy the container, should i delete all not needed subject areas out of it or is it best to do this when building the execution plan? I am basically trying to simplify the container for my own sake and have the container just have few subject areas rather than wait till i build the execution plan and then focus on few subject areas.
Your thoughts / clarifications are appreciated.
Regards,

Hi,
I would suggest that you leave the subject areas and then just don't include them in the execution plan. Otherwise you have the possibility of running into the situation where you need to include another subject area in the future and you will have to go through the hassle of recreating it in your SSC.
Regards,
Matt

SAP Adapter Best Practice Question for Deployment to Clustered Environment

I have a best practices question on the iway Adapters around deployment into a clustered environment.
According to the documentation, you are supposed to run the installer on both nodes in the cluster but configure on just the first node. See below:
Install Oracle Application Adapters 11g Release 1 (11.1.1.3.0) on both machines.
Configure a J2CA configuration as a database repository on the first machine.
Perform the required changes to the ra.xml and weblogic-ra.xml files before deployment.
This makes sense to me because once you deploy the adapter rar in the next step it the appropriate rar will get staged and deployed on both nodes in the cluster.
What is the best practice for the 3rdParty adapter directory on the second node? The installer lays it down with the adapter rar and all. Since we only configure the adapter on node 1, the directory on node 2 will remain with the default installation files/values not the configured ones. Is it best practice to copy node 1's 3rdParty directory to node 2 once configured? If we leave node 2 with the default files/values, I suspect this will lead to confusion to someone later on who is troubleshooting because it will appear it was never configured correctly.
What do folks typically do in this situation? Obviously everything works to leave it as is, but it seems strange to have the two nodes differ.

What is the version of operating system. If you are any OS version lower than Windows 2012 then you need to add one more voter for quorum.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

SAP Adapter Best Practice Question for Migration of Channels

I have a best practice question on the SAP adapter when migrating an OSB project from one environment (DEV) to another (QA).
If my project includes an adapter channel that (e.g., Inbound SAP Proxy listening on a channel), how do I migrate that project to another environment if the channel in the target environment is different.
I tried using the search and replace mechanism in the sbconsole, but it doesn't find the channel name in the jca and wsdl files.
What is the recommended way to migrate from one environment to the other when the channel name changes?

I have a best practice question on the SAP adapter when migrating an OSB project from one environment (DEV) to another (QA).
If my project includes an adapter channel that (e.g., Inbound SAP Proxy listening on a channel), how do I migrate that project to another environment if the channel in the target environment is different.
I tried using the search and replace mechanism in the sbconsole, but it doesn't find the channel name in the jca and wsdl files.
What is the recommended way to migrate from one environment to the other when the channel name changes?

Operating system image build and management best practices?

how do we create gold images for servers/desktops,
Best practices image management,
How do we control changes?
How do we prevent unauthorized changes (installation of software)?
What tools we can use for above.

I use MDT 2013 Lite Touch to create my images
http://www.gerryhampsoncm.blogspot.ie/2014/03/create-customised-reference-image-with.html
You should use in-built ConfigMgr Role Based Access Control to manage images afterwards (look at the Operating System Deployment Manager role).
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Solution Manager best practices about environments

Hello,
we intend to use Solution Manager 4.0.
My question : I wonder whether we need to have a single instance a SM (production) or whether we need to have multiple instances (one development SM where developments and customizing will be performed and one production SM populated with transport requests coming from the development SM) ?
What are the best practices ?
Thank you.
Regards,
Fabrice

Dear Fabrice,
In principle you donot need to have 2 instances of Solution Manager. 1 Instance is sufficient enough for monitoring all the Satellite Systems.
However if you intending to have Customized ABAP on Solution Manager then it might be a good idea to do so in an different client in the same instance keeping the client as an development client.
Most of the customizing in Solution Manager is non transportable hence it should be directly done in the productive client.
Hope this answers your queries.
Regards
Amit

Site System Roles - Best Practices

Hi all -
I was wondering if there wwere any best practice recommendations for how to configure Site System Roles? We had a vendor come onsite and setup our environment and without going into a lot of detail on why, I wasn't able to work with the vendor. I am trying
to understand why they did certain things after the fact.
For scoping purposes we have about 12,000 clients, and this how our environment was setup:
SERVERA - Site Server, Management Point
SERVERB - Management Point, Software Update Point
SERVERC - Asset Intelligence Synchronization Point, Application Catalog Web Service Point, Application Catalog Website Point, Fallback Status Point, Software Update Point
SERVERD - Distribution Point (we will add more DPs later)
SERVERE - Distribution Point (we will add more DPs later)
SERVERF - Reporting Services Point
The rest is dedicated to our SQL cluster.
I was wondering if this seems like a good setup, and had a few specific questions:
Our Site Server is also a Management Point. We have a second Management Point as well, but I was curious if that was best practice?
Should our Fallback Status Point be a Distribution Point?
I really appreciate any help on this.

The FSP role has nothing to do with the 'Allow
fallback source location for content' on the DP.
http://technet.microsoft.com/en-us/library/gg681976.aspx
http://blogs.technet.com/b/cmpfekevin/archive/2013/03/05/what-is-fallback-and-what-does-it-mean.aspx
Benoit Lecours | Blog: System Center Dudes

SRM EBP User management - best practice followed for your customer.

Hello All,
What are the best practices followed on SRM User manageemnt followed for your customers.
(1)When employee/ buyer leave the organisation ? what actions you do ? do you lock the users?
(2) If any thing interested share your experiences.
(3) What exactly customer expects from SRM systems on SRM user management?
(4) SAP audit/ customer audit practice on USER management ?
Any piece of information on your experiece/ best practice is appreciated.
regards
Muthu

Thanks Peter .
it is happening only in SRM right.
Is any work around for this issue.
In future SRM any planing to take care of this.
in ECC i can delete the user whenever the user moves .
All SRM customers will be very happy if SRM gives some workaround for this issue.
Every customer wants to reduce cost .
How can I find what are the opening documents for this user in one shot ?
thanks for answering this question.
I have seen our Eden Kelly report helps for shopping cart and other BO.
You are doing good job on our SRM WIKI innovative topics and discussons. I appreciate.
why i am raising this concern is that one user left the organisation and again we want to edit the data whch entered by the left user . system will not allow us to do after deleting the user.
so we are approaching SAP for ths help.
It is very difficult to convice the customers on this issues.
br
muthu

Working with version management and promotion management best practices BO 4.1

Hi Experts
I wondered if anybody knows if there is a document or something about best practices to work with the version management and promotion management in BO 4.1?
Our Environment includes two servers. The first one is our development and test server. The second server is our prod system.
Now on the dev server we have basically two folders called dev and test. We control access to them with a right system based on the folder structure.
My question now is how you would work in this scenario (third server is not an option). Main target is to have as few reports as possible. Therefore we try to work with the version management system and only have one version of each report in the dev folder of the cms. But this is where problems start. Sometimes the newest version is not the version we want to publish to the test folder or even prod server.
How would you publish the report to the other folder? Make a copy of the concerned report (transport to the same system via promotion management is not possible). Also how would you use the version management in regards to the folder structure? Only use version management in dev folder and export reports to test folder (out of vms control) or also use vms in test folder and how would that work?
Further more I’d be interested in learning best practices with promotion management. I found out that the promotion of a report that doesn’t exist in prod doesn’t make any problems. But as soon as an older version already exists there is only partial success and the prod folder gets renamed to “test”.
Any suggestions on how to handle these problems?
Thank you and regards
Lars

Thank you for your answer.
So you are basically proposing to work with the vms in the dev folder and publish the desired version to the test folder. And the test folder is out of version control in this scenario if I understood you correctly (like simple data storage)?
And how would you suggest promoting reports to the prod system? Simply by promoting the
desired version from dev folder directly to prod? This would probably lead to inconsistence because we would need to promote from dev system to test and dev to prod instead of promoting a straight line from dev over test to prod. Furthermore it would not solve the problem of the promoting result itself (A new folder called dev will be generated in prod but the report gets promoted to the prod folder if there was no report before).
Thank you for the link. I came across this page just a few days ago and found also lots
of other tutorials and papers describing the basic promoting process. The promoting process in general is clear to me but I wondered if it is possible to change some parameters to prevent folder renaming for example.
Regards
Lars

Best Practice Question

I have 3 Areas for my DWH
The first area is Staging then validation and core
Staging is just do load date from the source systems
validation is to validate data (every city has to have a countrie ....)
core is my DWH shema.
The First step in ETL is to load the data from core to validation, let's say my GEO_DIM Dimension goes to Countries, Cities and Regions in core. Additionaly I build a CRC SUM when I downlaod from Core to Validation and store the CRC Checksum in a Staging table.
The second step is to load target from the source systems to staging, but only those date that are non equal to the previous downloadet CRC schecksum, so only changed or new data going to staging.
The third step is do load that new/changed data from staging to core and proof some dependences. It's just validation.
My Question is, what is the best practic to bring three tables (Countries, cities and region) to one Dimension
thanks and regards
Andreas

Andreas,
I guess the correct is depends... Without kidding, are you planning to use a flat star table for this dimension? If that is the case you would be joining the sources together and loading this into the table.
Now this sounds way to simple, so I guess there is something more to the question...
Jean-Pierre

Best Practices question re Windows XP & Parallels 4.0 installation

To Apple Gurus here:
I am a new convert from Windows to Mac. Just bought a Macbook Pro (4G/320G, 2.4Gz) and a copy of Parallels 4.0. I have an OEM copy of Windows XP Pro & Photoshop CS4 for Windows. The question before me is what sequence should I go about installing Windows & Parallels. Logically, I think I should install:
1) Windows XP using Boot Camp first,
2) then install PhotoShop CS3 for Windows in the Windows partition
3) then install MS Office
4) and finally install Parallels 4.0.
Is this the right sequence or indeed a "Best Practices" scenario?
Any tips for a 'Best Practice' installation will be highly appreciated.
Also, is anyone here using the SAP GUI for Mac OS-X & Citrix Presentation Server Client for Mac OS 10.0 (now renamed XenApp)?

First, my creds. I don't consider myself an Apple guru. I have been running a MB since last December and at that time, I installed Parallels 3.0. If I remember correctly, after installing Parallels, I installed Windows Vista, and then Office and while I was impressed to be able to run MS Office on a MB, it took what I considered to be TOO long to load and then the performance was not that great. So, mostly I've stayed on the Mac side of the operation and only loaded Parallels if I had to run some MS program.
About a week ago I got an offer from Parallels to buy 4.0 at an upgrade price of $40. I went with the box version since it was the same price as the download version. Tonight I got my courage up to do the upgrade. I was leery because I thought I might have to reinstall all my MS stuff (Office Pro, etc.) When I put the disk in to install the program, I receive a message saying there was a later edition available with the option to download it or install the box edition. After a few minutes of thought, I decided to do the download version. I would still recommend getting the box version since you get a manual with it although the download version comes with a PDF manual.
When I finished, I then clicked on upgrade/install and the installation proceeded without much input from me. Lo and behold, the installation finished and it booted up to my previous Vista installation with all my programs intact.
So far, I must stay I'm VERY impressed with this upgrade Parallels edition. It seems to load much faster, the programs are more responsive, Vista so far seems very stable and the ability to switch back and forth from Windows to OS X is totally better. From what I've seen so far, I would highly recommend anyone using Parallels 3.0 get this upgrade. While I've only been using it a few hours, it seems like the best upgrade for ANY program/system (Windows 95-->Vista) that I've ever done.
A few months ago I saw a piece on an upgraded version of Fusion which stated that it moved Fusion ahead of Parallels. If that were so, I think the ball must be back in Parallels court with 4.0.

Development System Backup - Best Practice / Policy for offsite backups

Hi, I have not found any recommendations from SAP on best practices/recommendations on backing up Development systems offsite and so would appreciate some input on what policies other companies have for backing up Development systems. We continuously make enhancements to our SAP systems and perform daily backups; however, we do not send any Development system backups offsite which I feel is a risk (losing development work, losing transport & change logs...).
Does anyone know whether SAP have any recommendations on backuping up Development systems offsite? What policies does your company have?
Thanks,
Thomas

Thomas,
Your question does not mention consideration of both sides of the equation - you have mentioned the risk only. What about the incremental cost of frequent backups stored offsite? Shouldn't the question be how the 'frequent backup' cost matches up with the risk cost?
I have never worked on an SAP system where the developers had so much unique work in progress that they could not reproduce their efforts in an acceptable amount of time, at a acceptable cost. There is typically nothing in dev that is so valuable as to be irreplaceable (unlike production, where the loss of 'yesterday's' data is extremely costly). Given the frequency that an offsite dev backup is actually required for a restore (seldom), and given that the value of the daily backed-up data is already so low, the actual risk cost is virtually zero.
I have never seen SAP publish a 'best practice' in this area. Every business is different; and I don't see how SAP could possibly make a meaningful recommendation that would fit yours. In your business, the risk (the pro-rata cost of infrequently needing to use offsite storage to replace or rebuild 'lost' low cost development work) may in fact outweigh the ongoing incremental costs of creating and maintaining offsite daily recovery media. Your company will have to perform that calculation to make the business decision. I personally have never seen a situation where daily offsite backup storage of dev was even close to making any kind of economic sense.
Best Regards,
DB49

Hotfix Management | Best Practices | WCS | J2EE environment

Hi All,
Trying to exploit some best practices around hotfix management in a J2EE environment. After some struggle, we managed to handle the tracking of individual hotfixes using one of our home-grown tools. However, the issue remains on how to manage the 'automated' build of these hotfixes, rather than doing the same manually, as we are currently doing.
Suppose we need to hotfix a particular jar file on a production environment, I would need to understand how to build 'just' that particular jar. I understand we can label the related code (which in this case could be just a few java files). Suppose this jar contains 10 files out of which 2 files need to be hotfixed. The challenge is to come up with a build script which builds -
- ONLY this jar
- the jar with 8 old files and 2 new files.
- the jar using whatever dependent jars are required.
- the hotfix build script needs to be generic enough to handle the hotfix build of any jar in the system.
Pointers, more in line with a WCS environment would be very much appreciated!
Regards,
Mrinal Mukherjee

Moderator Action:
This post has been moved from the SysAdmin Build & Release Engineering forum
To the Java EE SDK forum, hopefully for closer topic alignment.
@)O.P.
I don't think device driver build/release engineering is what you were intending.
Additionally, your partial post that was accidentally created as a duplicate to this one
has been removed before it confuses anyone.

IVR (Inter-VSAN Routing) - Best practices questions

Hi there,
We have a situation where we will have multiple customers hosted on a 9513 and sharing a single storage array.
We want to keep the logically seperated in their own VSANs, but of course the storage array will need to be zoned to all the customers hosts.
Now IVR should be the thing to use, but I'm getting resistance from the local team (screams of "Nooooo!!! They're EVILLLLL!!!") ... so I want to find out if there are some best practices around IVR use ?
Should they be used only for light duty stuff ? (though at present we use them with tape backup, which isn't exactly "light")
Do they impact performance to a measurable degree ?
Are they stable ?
What can go wrong with them ? And does it happen often ?
Thanks!

IVR does not impact application I/O performance because all the vsan rewrite and fcid rewrite actions are done in hardware asics. The IVR process on supervisor is responsible for managing the configuration and ensuring the rewrite tables are programmed in the linecards. The process is stable.
Most of the issues I have seen are in environments with multiple IVR enabled MDS switches ISL'd together or an MDS IVR enabled switch connected to a McData/Brocade in an interop mode.
Like any feature there have been bugs and it pays to check the SAN-OS release notes when planning installs. For example, a config change on one switch does not get properly pushed to another IVR switch or a forwarding table for an ISL interface does not get correctly programmed. There have also been a fair share of user misconfigurations which could have been avoided if Cisco Fabric Services (CFS) was enabled for IVR. This is done with the 'ivr distribute' command. Without this it is very difficult in large topologies of multiple IVR switches to ensure they have a consistent IVR config. In other cases there have been problems from a mix of IVR enabled switches running different releases of SAN-OS, e.g. mixing 3.0 with 3.2.
Best practice is to have dual physical fabrics, upgrade one fabric at a time ensuring all IVR switches in a fabric run same SAN-OS release.
A single IVR switch is much easier to implement. The MDS Configuration Guide has a list of best practices for IVR and one of those is to use the NAT option. Personally I would avoid NAT option where you can as NAT makes any troubleshooting harder trying to figure out the domain ID translations. You would also minimize risk of hitting some NAT related bugs, but you could also avoid most of these by checking the workarounds documented in the Release Notes. And with NAT you need to also configure persistent virtual domains and fcids to cater for AIX and HP-UX systems that cannot handle the FCID of the target changing whenever the exported virtual domain ID changes. To give NAT credit, each vsan is represented by a single virtual domain. In regular non-NAT mode, each switch in a vsan is represented by a virtual domain, meaning you eat up more virtual domain IDs. So in large topologies with many domain IDs there are scalability advantages to using NAT and the IVR updates between switches are more efficient with fewer virtual domain IDs to advertize. Of course, NAT must be used if merging physical fabrics with same domain ID and you cannot afford the downtime to change one of the switch domain IDs.
However if it is just a single IVR switch I would avoid NAT. To do this all your domain IDs should be statically defined and there must be no overlapping domain IDs between IVR'd vsans. If it is a brand new install you can easily achieve this by specifying unique allowed domain ID ranges per vsan.
For example, each customer can have their own vsan with say 10 domain IDs and the storage can be in vsan 2. You will only use one domain ID per vsan on day 1. Allowing 10 domain ids per vsan means you can add up to 9 other switches per vsan should you need to in the future. There is a maximum 239 domains per vsan so you could have up to 23 customers on your 9513 working with a range of 10 domain IDs per vsan.
fcdomain domain 2 static vsan 2
fcdomain domain 10 static vsan 10
fcdomain domain 20 static vsan 20
fcdomain domain 30 static vsan 30
..and so on..
fcdomain domain 230 static vsan 230
fcdomain allowed 01-09 vsan 2
fcdomain allowed 10-19 vsan 10
fcdomain allowed 20-29 vsan 20
fcdomain allowed 30-39 vsan 30
..and so on..
fcdomain allowed 230-239 vsan 230
With or without IVR you should still run dual fabrics (e.g. 95xx in each fabric) and host based multipathing for redundancy.
And don't forget IVR will require an Enterprise license. I have even seen a large outage because the customer forgot to install the license before the 120 day grace period expired.

System Management Best Practice Questions

Similar Messages

Maybe you are looking for