Downloaded 64 times
![WSAdmin – sending commands
▪ Start in the BIN directory of the deployment manager
– C:IBMWebSphereAppServerprofilesDmgr01bin
!
▪ Call wsadmin by typing
wsadmin(.sh) –lang jython –username [name] –password [password]
▪ Choose which application you want to work with
execfile(“profilesAdmin.py”)
▪ Any changes you make here will be pushed out to all the nodes
– Wsadmin commands are case sensitive regardless of your platform](https://image.slidesharecdn.com/connections-140526144640-phpapp02/85/Becoming-A-Connections-Administrator-38-320.jpg)
Uploaded byGabriella Davis
Becoming A Connections Administrator
This document provides information about becoming an IBM Connections administrator. It discusses the wide range of skills and technologies required, including CSS, Java, LDAP, databases, IBM HTTP Server configuration, and WebSphere administration. It emphasizes planning resources, verifying configurations, backing up data, monitoring logs, and following documentation to install, customize, and maintain Connections successfully.
More Related Content
Similar to Becoming A Connections Administrator
Becoming A Connections Administrator
- 1. Become a Connections Administrator GabriellaDavis, The Turtle Partnership
- 2. ! Gab Davis -Technical Director The Turtle Partnership gabriella@turtlepartnership.com ▪Administrator, Problem Solver, Stubborn Fixer of Things ▪Working with IBM technologies and all the things surrounding and integrating with those ▪Based in London, about half the time 2
- 3. CONNECTIONS IN ALLITS GUISES
- 4. 4 • A ConnectionsAdministrator is knowledgeable about many different products and tools that have a wider application than just IBM Connections • A Connections developer can use development tools from CSS to OpenSocial gadgets to Java and more, all have a much wider application than just IBM Connections
- 5. WHAT WE HAVELEARNT ABOUT PLANNING
- 6. Fight For TheResources You Need 6
- 7. Are You SureAbout That WebSphere Architecture? 7
- 8. It’s All AboutThe People Locations Teams You’re only as good as your LDAP Meaningful context is everything - who ARE these people?
- 9. I wish Ihad connections to plan installing connections…. Drag everyone into a room…..
- 10.
- 11.
- 12.
- 14. KNOWING WHERE ALLTHE DATA IS
- 15. CONFIG LOCAL DATA SHARED DATA FILEATTACHMENTS DATABASES
- 16.
- 17.
- 18. SHARED DATA Customisation Strings ProfileTypes Language Translations File Attachments Custom JSPs
- 19.
- 20.
- 21. DANGER! ! ..deleting a Communityis irreversible & can be done by any Community Owner
- 22.
- 23.
- 24. 2 4 LDAP DIRECTORY TDISERVER TDI SCRIPTS / ASSEMBLYLINE PEOPLEDB DATABASE CONNECTIONS PROFILES CREATING PROFILES 31 5
- 25. Population Wizard Simple: Manual 1LDAP Source > Profile XML Files From TDISOL 1 LDAP Source > Profile Some data manipulation Assemblyline Advanced: Realtime Multiple Data Sources Full data manipulation
- 26.
- 27.
- 28. HTTPD.CONF In HTTPServerbin Can bemodified in WebSphere PLUGIN-CFG.XML Generated by WebSphere Mappings for every application Distributed to HTTPServer
- 29. DANGER! ! The httpd.conf filecan be easily broken as it’s not validated on save ! A faulty httpd.conf will prevent IHS from starting
- 30.
- 31. Searching Files & FolderMetadata Document Types Tagging ✤ People / Unstructured ✤ Process / Structured Finding Things
- 32.
- 33. Cognos BI Cognos Transformer Cognos & Metrics DB Cognos& Metrics J2EE Apps Connections Reporting
- 34. Forms Experience Builder Polls& Surveys Installs on WebSphere Server(s) Requires DB2 Installs on every server in the chosen cluster
- 35.
- 36. Websphere Administration ▪ Applicationsecurity - the rights users have to applications • Not granular “one size fits all” • New roles that change behaviour aren’t something you can add ! • Wsadmin • command line administration tool • also used to make changes to application configuration settings
- 37.
- 38. WSAdmin – sendingcommands ▪ Start in the BIN directory of the deployment manager – C:IBMWebSphereAppServerprofilesDmgr01bin ! ▪ Call wsadmin by typing wsadmin(.sh) –lang jython –username [name] –password [password] ▪ Choose which application you want to work with execfile(“profilesAdmin.py”) ▪ Any changes you make here will be pushed out to all the nodes – Wsadmin commands are case sensitive regardless of your platform
- 39. JAASAUTHENTICATION ! – Global Security– JAAS – J2C authentication data
- 40. DatabaseReorg Look for reorg.sqlscripts in the connections.sql directory of the installer
- 41. backup & restorefrom Dmgr profile “bin” directory backupconfig d:backupsdmgr040114.zip -nostop
- 42. SystemOut.log LOG_ROOT variable = logfile location Each WAS server has its own logs Location and retention configurable by server
- 43. Do’s & donots ▪ Backup your configuration using backupconfig before making changes to the configuration – Never manually edit an XML configuration file, always use wsadmin which verifies the XML structure as it’s checked back in – Schedule the database reorg maintenance scripts to run regularly, – Set up specific credentials for developers to use to access the Connections data, don’t re- use administration credentials – Ensure you have a test / staging server to test customisations, enhancements and developments on – Never skip post installation steps , or any steps, follow the documentation ! – Never let your developer have ISC access or wsadmin access to a production environment!
- 44. HOWTO FIND ME Twitter,blogs, Instagram, Facebook and more gabriella@turtlepartnership.com GabriellaDavis (skype) http://turtleblog.info gabturtle on twitter and elsewhere