Skip to main content

Docker Commands for Maximo Consultants

Containers are becoming popular day by day and provide great flexibility of running the instance locally and play around for developers. For Maximo developers, it is even more relevant as there is no need to coordinate with others while enabling admin mode, or restarting the server, etc for any developmental need.

Docker for Maximo can be used by Developers to run their isolated local instance. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime system tools, system libraries, and settings.


While working with docker, the following are some of the frequently used commands which every Maximo consultant should know.

Happy Dockerizing!

CommandsPurpose
docker --versionVersion of Docker installed on your machine
docker infoDetails of Docker installed on your machine
docker imagesList of images on your machine
docker images -aList of images with creation time, size and all other details
docker pull <image name>Pull image from Docker Registry
docker run -it -d <image name>Run the image as docker container
docker ps -aList all containers and details of port, container id, image & status
docker exec -it <Container ID> bashAccess a Running container by its Container ID
exitExit from Container
docker stop <Container ID>Stop running container
docker commit <Source container ID> <docker hub registry>/<name of image>Create new image on local system from existing source image
docker push <docker hub registry>/<name of image>Push docker image created from local system to Docker Hub
docker rm <container id>Remove Container via Container ID
docker rmi <image id>Remove Image
docker rmi -f <image id>Remove Image Forcefully
docker-compose up -dRun container from the image
docker exec -ti --user root <Container ID> /bin/bashRun Docker Container as Root
docker exec -ti --user ctginst1 <Container ID> /bin/bashRun Docker as specific user (eg- ctginst1)
docker container ls –aqList IDs of all docker containers
docker container pruneRemove all stopped containers
docker images ls -qf dangling=truRemove all dangling images
docker images pruneRemove all unused images
docker volume lsList all volumes
docker volume ls -qf dangling=trueList all volumes which are Dangling
docker volume rm $(docker volume ls -q -f dangling=true)Remove all dangling
docker run -it -d <image name>Run Image as Container
docker loginLogin into Docker Hub
docker commit <Container-ID> <RepositoryUserName>/<Repository_Name>:tagCreate image from Container
docker push <ImageName>:<TagName>Push image to Docker Hub

Comments

Popular posts from this blog

Maximo OSLC Integration with External System- Get data in JSON format

Greetings! If you have noticed recent version of Maximo, couple new application in Integration module has been added which are OSLC Resources and OSLC Provider.These modules gives us ability to integrate with external system in JSON. OSLC is an open community that creates specifications for the integration of products and/or tools.  IBM is a leading contributor to this community and many software products within the IBM Software Group are implementing OSLC in order to enable cross-product integrations. An OSLC integration requires 2 players-  1. OSLC Consumer application 2. OSLC Provider application.   An OSLC provider application makes containers of associated resources(data) available for integration through service providers. Consumer applications then use these service providers to query resources and to create, update, and delete resource data.  The consumer application sends a query to the service provider for resource data. The service provider provides a link

Power of Maximo Formulas - Build logic w/o Custom Java code or Automation Script

Greetings! Maximo 7.6 has lot of additional capabilities added in Tivoli Automation Engine as compared to older versions of Maximo which aim to allow users to make change in applications for small requirements without actually going to customization route. Automation scripts is one of such tool given for users and technical developers to change the behavior of Maximo in case where functionalities can't be changed only via use of configuration. If we have a requirement to populate some field on basis of other fields , we can easily do that with automation script but in order to do that you still need to have knowledge of Jython or Javascript to write the logic. Maximo formula is one the tool given by IBM which can be used for such business requirements and user can make changes to Maximo logic via configuration without getting into difficulties of coding. Formulas are available from Maximo version 7603. With release of Maximo version 7606, there has been addition of new capabil

Call publish channel w/o enabling Event Listener in Maximo

Greetings! Generally if we have to send data to external system via MIF, we create Publish Channel and enable Event Listener on publish channel. Once event listener is enabled, Maximo listens for event and send data to end point via publish channel for each Save of related MBO . But t here are many scenarios where we need to send data to external system using publish channel on specific event and not for every save. In order  to send to external system on specific event, for example - sent data to Ariba when PO status in Maximo is changed to APPR, we can use automation script or java code to call publish channel on the go. Below code can be used in automation script - server = MXServer.getMXServer() userInfo = mbo.getUserInfo() whereClause = <CONDITION> server.lookup("MIC").exportData("<Publish Channel Name>", "<External System Name>", whereClause, userInfo, 1000) Via Java class - MXServer server = MXServer.getMXServer();