If you have any documents, ppt which you want to share, you are most welcome. Also, please let me know the quality of the stuffs, that you see in this site. (This site is in an infant state, need your help for improvements)
My idea is to provide a single point, where you will get most of the questions answered.
Changes are done. And, as you said, i don't think there should be detailed DOC for removing the scheduled jobs. Normally this kind of requests will be carried out by someone who has fair knolodge in SD,Excel and SQL. So, i think we can avoid that.
Do you have anything to add to Speed Up the SD ? I am planning to add few more things at the client side (like reduce the number of fields and tabs etc..
Actually I had wrote in some posts the practice I follow to speed up client, but the search is quite problematic so i'll post it here again.
1. Avoid having too many fields of entity reference and entity reference set type in the most used forms.
Examples of entity reference set: Service Calls, Changes, Incidents, Problems, Workorders on Configuration Items, Child Organizations in ORGS etc.
Entity reference fields are Codes (custom or built-in), persons, workgroups etc.
2. For items with very large volume of entries, besides setting query limits through Presentation/Search, fields most commonly used as criteria in search/view filters should be indexed at the db level. Multiple indexes may be needed.
For example, We have about 2500000 configuration items and 600000 persons. An advanced find using a non indexed field as filter may take as long as several minutes to be completed. Indexing together fields that are used in filters reduce search/time to present a view to seconds.
3. For items with large volume of entries, avoid presenting too many entity reference fields in the views. Not only the views on client but the views that are "embedded" in forms for entity set relations (example CI users, Used services etc).
4. For items with large volume of entries do not use custom fields as primary keys for Data Exchange tasks. Use "searchcode", "source-id" or even id if possible.
5. In heavy views avoid having calculated fields (like remaining duration).
Hi, This tip may be known to old timers but for someone new to service desk I hope it is useful. ********************************************* Usually all service departments conduct a customer satisfaction survey or feedback for the services they are offering to their end users or customers. Unfortunately this feature is not there by default in service desk. But Service desk can be customized to enable this. The procedure would involve following steps: 1. Enable some custom fields to define the feedback questions and also to capture customer's inputs. (Ex: using Code or Text fields). 2. Customize service pages to include a new jsp which acts like a feedback form. This form would contain all the custom fields defined above and also method to save these. 3. Customize ViewEditServiceCall.jsp to call the new form on certain condition (ex: When the status of service call is changed to Resolved.) 4. In the resolution emails request users to login to service pages and confirm the solution and provide their feedback. When user logs in he/she will see a link to provide feedback (this will open the Feedback form). 5. Modify / create views in database to report on the feedback collected. 6. Create reports to display customer feedback received on a weekly/monthly basis. ********************************************
I've had a look at your site, it looks good the quality of the stuff there is quite high. I'll be visiting again and reading more when I get time!
I replied to a post a while ago regarding Service Manager 7. I offered a PowerPoint Presentation of slides etc from the HP Seminar on SM7.
The zipped file is 14Mb. I have been swamped with requests to email the file and I've tried to send it to them all. Lots of the emails fail because of the file size.
Would you be able to host the file on your website?
If so please email me at firstname.lastname@example.org and I'll send you the file.
Also what else are you looking for, I have some documents which I have created which explain how to do stuff, such as getting data from an Excel sheet and importing into HPOV 4.5. I know its in the manual but this is hopefully easier to understand?
Would that sort of thing be of interest?
Lastly, on the HPOV page on your site, there are titles such as "How to check the DB of your Service Desk", but they are just text. They are not hyperlinks. Is this in development or is there some kind of error somewhere?
Well, about The HP Slides : I thought of putting it up, in fact i was thinking of sending u a mail for the same. But,whne i looked at the slides, it say it is "HP Confidential". Can we publish it ? Any legel issues ?
About the other stuffs : Please rush them to me.....i am sure there are a lot of people who can use it....
Regarding "Checking DB" etc.. ::- I am yet to write in those topics. Thanks for reminding me and waking me up!!!!
great idea with the site, thought you might want to add some info about finding deserialised rules, see the attached executeable plus the instructions. This needs to be run directly on the app server using the system account as the default account
here is a tip on setting the java memory instead of using the defaults
-XX:MaxNewSize=64M -XX:NewSize=64M â Xms200M -Xmx1000M
- make sure that the sum of Xms (initial heap size) for all application servers running on a single physical machine remains clearly below the available memory (preferrably below 50 % of the memory) - to assure that there will never be a shortage of memory, make sure the sum of Xmx (maximum heap size) for all application servers running on a single physical machine does not exceed the available memory - make sure that NewSize is smaller than Xms, and MaxNewSize is smaller than Xmx - setting NewSize to the same value as MaxNewSize assures the JVM does not resize its youngest generation, and should therefore result in a better performance.
- make sure that the sum of Xms (initial heap size) for all application servers running on a single physical machine remains clearly below the available memory (preferrably below 50 % of the memory)
- to assure that there will never be a shortage of memory, make sure the sum of Xmx (maximum heap size) for all application servers running on a single physical machine does not exceed the available memory
- make sure that NewSize is smaller than Xms, and MaxNewSize is smaller than Xmx
- setting NewSize to the same value as MaxNewSize assures the JVM does not resize its youngest generation, and should therefore result in a better performance.
Peter :: Points are taken careâ ¦. ï Thank you Mark
Michel :: I have seen the PPT, and it says â HP Confidentialâ so, I am afraid to publish it, unless I get am able to get in touch with a HP person and get permission to publish the sameâ ¦
Thank you ALL!!! I am working on making the site more good looking, all the new tips will be published on the new site, sorry for the delay!! Please let me know, if you would like to see any changesâ ¦I will try my level best to add/remove them!!