Image Feature #3237
New AMI for WAS ND v9
|Image:||WebSphere AS - ND 9.0||Your Marketplace Account ID:||0000-0000-0000|
|Operating System:||Linux||Marketplace:||Amazon Web Services|
|JRE:||v1.8 JRE/JDK 64-Bit||Customer State:||KENT|
|Instance Type:||All||Customer Country:||UK|
We need to update our WAS ND listings with the newest versions published by IBM: https://www-01.ibm.com/support/docview.wss?uid=swg27004980#ver90
- Assignee changed from Mariusz to IBM Support
There is a problem with creating default profiles when there is no public dns on an instance but only numeric public IP.
DMGR can be created but it cannot start because of some UDP related errors.
I did some investigation but couldn't find the solution so I created a PMR with IBM.
- Status changed from In Progress to In Development
Along with IBM team we finally were able to make WebSphere profiles work when they are created with numeric public ip.
It was necessary to change the network configuration:
[root@ip-172-30-0-134 midvision]# nmcli con mod "System eth0" ipv4.addresses 188.8.131.52 [root@ip-172-30-0-134 midvision]# nmcli con mod "System eth0" +ipv4.dns 184.108.40.206 [root@ip-172-30-0-134 midvision]# nmcli con up "System eth0"
I will add this to Troubleshooting section in our documentation for WASND products on AWS.
- Status changed from Create Documentation to Image Testing - General
- Assignee changed from IBM Support to Mariusz
New WASND versions are ready to be tested:
ami-07314a46bca2e9253 - AwsMarketPublished_WebSphere Application Server Network Deployment Edition v 220.127.116.11 RD 5.0.10 R.1.0
ami-099deeab76c17ad74 - AwsMarketPublished_WebSphere Application Server Network Deployment Edition v 18.104.22.168 RD 5.0.10 by MidVisionCloud R-1.0
- Status changed from Submitted to Closed
- % Done changed from 0 to 100
These versions are now publicly available :